-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sf package version create - Language code not valid Winter '24 #2518
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Hello @marsh-mellow 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
CLI Version: Architecture: Node Version: Plugin Version: OS and Version: Shell: Root Path: |
Updated 3 plugins
using npm install --global @salesforce/plugin-packaging Same ErrorError (1): Can’t create package version. en_CA isn’t a valid language code. Review the language codes listed on this Salesforce Help page: https://help.salesforce.com/s/articleView?id=sf.faq_getstart_what_languages_does.htm&type=5. Then update the language code, and tryVersion create.... done |
Confirmed scratches are still working |
|
@marsh-mellow FYI you can update that plugin to latest by saying
not I doubt it'll solve your problem because this looks like a server/release issue. |
I agree with Shane. This does not look like a CLI issue. Can you try uninstalling these plugins with And installing them with the CLI itself: Do you have any other languages in your project? |
Just the en_CA, fr_Ca and of course the default en_US |
Tried the uninstall in npm and install with SF. Same error. I also have a ticket open with salesforce. |
FYI Here is the new version output after plugin install
|
Interesting, I am assuming you are not having any issues with |
I have experienced the same with 'hu'. "Can’t create package version. hu isn’t a valid language code." |
Still waiting on Case with Salesforce. Will update here once I know more. |
Does anyone have any updates on this? We've also logged a case with Salesforce but not making any progress so far. |
We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on. |
What's the case number? I'll check on it. |
Thanks @shetzel our case number is 45520085 I also reached out to the packaging PM |
That case number doesn't match something related to this issue. Possibly a different number? |
Our case number is #45474747 |
@shetzel sorry I'm confused, case 45520085 is exactly about this issue! |
@paulhxcd - sorry, I checked with the wrong system (which referenced a different case). Dileep appears to be helping to move the case along. |
Response from Salesforce today about issue ============================= I would like to provide an update regarding the issue pertaining to the new package version creation. After our investigation, our product team has identified a critical bug. This bug arises when a user attempts to create a package version, and we identify their locale (in this case, en_CA) to create a package version. Currently, our validation method for supported languages is stringent, allowing only "Fully Supported Languages." We are working to expand this to accommodate all types of languages supported by the organization. Our team is actively working to resolve this high-priority bug. In the meantime, if this issue is hindering your package version creation, there is a temporary workaround available. You can specify a fully supported language code, such as en_US, via the CLI command (using --language=en_US), which should enable you to create versions successfully. |
I confirmed the workaround does work with the language switch. |
Closing. |
Summary
This issue appears to have started when Salesforce version was updated. Error message says this language isn't available when everything was packaging before the upgrade.
sf package version create -w 100 -x -c -v -p 0Hxxx
» Warning: Plugin @salesforce/plugin-packaging (1.16.2) differs from the version specified by sf (1.26.1)
Version create.... -
Error (1): Can’t create package version. en_CA isn’t a valid language code. Review the language codes listed on this Salesforce Help page: https://help.salesforce.com/s/articleView?id=sf.faq_getstart_what_languages_does.htm&type=5. Then update the language code, and try creating the package
Steps To Reproduce
Expected result
Package was built without error
Actual result
Error (1): Can’t create package version. en_CA isn’t a valid language code. Review the language codes listed on this Salesforce Help page: https://help.salesforce.com/s/articleView?id=sf.faq_getstart_what_languages_does.htm&type=5. Then update the language code, and try creating the package
System Information
Windows Bash MINGW64
The text was updated successfully, but these errors were encountered: