"ar-SA - Invalid request" when uploading metadata to Play Store with a locale it does not support #21905
Comments
|
Facing the same issue. |
|
It seems you’ve encountered an issue with the fastlane tool when uploading metadata to the Google Play Store for a locale that is not supported. The error message you received indicates that the language code ar-SA (Arabic - Saudi Arabia) is not currently supported by Google Play. To resolve this issue, you can adjust your Crowdin configuration to ensure that only supported locales are used. Google Play supports a variety of locales, but not all possible combinations of language and region codes are accepted. It’s important to use only the locales that are recognized by Google Play to avoid such errors during the deployment process. As you’ve discovered, setting skip_upload_metadata and skip_upload_changelogs to true can bypass the error, but this is more of a workaround than a solution. The proper fix would be to ensure that your metadata locales match the supported locales on Google Play. For future reference, it’s always a good idea to check the supported locations for distribution and the supported languages/locales on Android to prevent similar issues. If you need to update your fastlane configuration or scripts, make sure to include only the supported locales to streamline your deployment process. |
|
Yes, I know why this happens, I just want this to not be a fatal error. Just skip the unsupported language and continue. Maybe not by default, but it would be nice to have an option to do so, not the current all-or-nothing approach. |
New Issue Checklist
Issue Description
When any of textual metadata upload is enabled, but there are locales in
fastlane/metadatathat aren't supported by Google Play, you get this cryptic error.I used a mitm proxy to see the actual error returned by the server and the request that caused it. (there might be better ways to do it but I'm very unfamiliar with Ruby and its ecosystem)
Request URL:
https://androidpublisher.googleapis.com/androidpublisher/v3/applications/:packageID/edits/:someOtherID/listings/:localeError:
{ "error": { "code": 400, "message": "The requested language is not currently supported: ar-SA.", "status": "INVALID_ARGUMENT" } }I assume these GET requests to retrieve existing metadata are done to only update those pieces of metadata that have actually changed.
If I set both
skip_upload_metadataandskip_upload_changelogstotrue, this goes away and the deployment succeeds.Now that I've seen the real error, I know I should change my Crowdin configuration to only add the country code to locales where it's strictly necessary (e.g.
pt-BRvspt-PT). Still, the error messages returned by APIs should always be included in the output.Command executed
fastlane deploy
Complete output when running fastlane, including the stack trace and command used
Environment
(doesn't seem to matter, does the same thing in a Github Action)
✅ fastlane environment ✅
Stack
System Locale
fastlane files:
`./fastlane/Fastfile`
`./fastlane/Appfile`
fastlane gems
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
generated on: 2024-03-01
The text was updated successfully, but these errors were encountered: