-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[expo-localization] Exception: Unsupported ISO 3166 country: es_419 #21414
Comments
@andresribeiro - that isn't a valid reproducible example, you should share a link to a repository that we can clone and run and see this issue. it'd be helpful if you can add that to this issue. that said, it seems that there may be an additional case that we need to handle with |
yeah, should be enough. |
Thank you for filing this issue! |
@brentvatne I recognize that it's not a valid reproducible example, but there is no way to provide one since it is just calling getLocales() on a device where the language does not have a country code (according to the react-native-localize issues) |
Have same issue on Expo 47:
|
@MortensenC Still having this error? I'm also using Expo V48 and just send my build to Play Store, but in my case the locale was |
@aleqsio @MortensenC Same here, we just got the error with |
Getting these errors as well. With expo 49. Causes crashes for android devices reported in google play. Error: Call to function 'ExpoLocalization.getLocales' has been rejected. → Caused by: java.lang.IllegalArgumentException: Unsupported ISO 3166 country: en |
@aleqsio can you reopen this issue, please? |
Will Play Store deny my production deploy while I'm having this issue? |
No, it will not deny your app because of that
El mié, 27 sept 2023 a la(s) 16:07, Alan Graton Lourenço de Brito (
***@***.***) escribió:
… Will Play Store deny my production deploy while I'm having this issue?
—
Reply to this email directly, view it on GitHub
<#21414 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADKK5PBL5PWRQBTXGL2OELX4R2QXANCNFSM6AAAAAAVIYQAPI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Create your own email signature
<https://www.wisestamp.com/create-own-email-signature/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=>
|
no. |
We are having this problem as well. These are the observations I've made so far about the issue:
Perhaps a similar check is needed here? |
Same problem: Unsupported ISO 3166 country: en |
Same problem: Unsupported ISO 3166 country: ar |
Still no solution for this? |
We were using expo-localization 14.0.0 and seeing this error. A fix to catch exceptions has been added for v14.2.0 If you're still seeing this problem, perhaps try upgrading to expo-localization v14.2.0 or higher and see if that solves it? |
@cgordon-d2l We are facing with this error on 14.5.0. I checked 14.0.0-14.2.0 diff and 14.2.0-14.5.0 diff and didn't find any solid changes. So for me it's a mystery why it's working for you and not working for us. Our firebase crashlytics shows that there is no difference between lib versions, os versions or device models |
It's hard to provide a reproducible example, but I decided to run an emulator, which let me change the locale through Using an emulator let me change this in terminal. So I decided to test it on an old Android version (11) by running these commands adb root
adb shell "setprop persist.sys.locale es-419; setprop ctl.restart zygote" Navigating to the language setting, I can finally see that option, which wasn't available before, and that my phone is using Latin American Spanish Now I did 2 different Sad because it's even included in documentation examples expo/packages/expo-localization/build/Localization.types.d.ts Lines 67 to 73 in 76fad0f
|
@newfylox i'll try to follow those steps and see if I can reproduce – seems to be a fairly good repro, thank you! |
Minimal reproducible example
https://gist.github.com/andresribeiro/569e4d70afe1778e8f2541e301433017
Summary
The following error appears on Play Console pre-launch report:
It might be related to these 2 issues from
react-native-localize
:zoontek/react-native-localize#31
zoontek/react-native-localize#36
Environment
System:
OS: Linux 5.4 Linux Mint 20.3 (Una)
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 19.7.0 - /usr/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 9.5.0 - /usr/bin/npm
Watchman: 2022060.192726.0 - /usr/local/bin/watchman
npmPackages:
expo: ~48.0.4 => 48.0.4
react: 18.2.0 => 18.2.0
react-native: 0.71.3 => 0.71.3
npmGlobalPackages:
eas-cli: 3.7.2
expo-cli: 6.3.2
Expo Workflow: managed
The text was updated successfully, but these errors were encountered: