expo: [expo-localization] Exception: Unsupported ISO 3166 country: es_419

It’s hard to provide a reproducible example, but I decided to run an emulator, which let me change the locale through adb commands. The faulty locale is named Latin American Spanish but I was not able to see this option through the settings UI. I guess some phones are shipped with this option enabled or added on custom Android OS phones.

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 console.log, one with the deprecated locale constant and one with the new getLocales() method. The deprecated one is correctly showing the locale but not the new one, showing an empty array. And so my code was using getLocales() method in both example after these 2 different logs, hence crashing my application

Sad because it’s even included in documentation examples https://github.com/expo/expo/blob/76fad0fe281f3517cb3a5375c9854541ff66b781/packages/expo-localization/build/Localization.types.d.ts#L67-L73

We are having this problem as well. These are the observations I’ve made so far about the issue:

• It seems that the country code is missing or not an ISO country code for the exceptions we’re getting. Example: es_IC, en, pl_SP, es_419, nl, ar_XB
• The country code is supposed to be optional, but it looks like Java throws an exception if it’s missing or incorrect
• There was a similar error for react-native-localize Issue 31, and the fix was to add a check to validate the country code

Perhaps a similar check is needed here?

@newfylox i’ll try to follow those steps and see if I can reproduce – seems to be a fairly good repro, thank you!

Same issue here for ar EXPO 48:

Exception com.facebook.react.common.JavascriptException: Error: Call to function ‘ExpoLocalization.getLocales’ has been rejected. → Caused by: java.lang.IllegalArgumentException: Unsupported ISO 3166 country: ar, js engine: hermes, stack: _construct@1:126614 Wrapper@1:126259 _createSuperInternal@1:668274 CodedError@1:668559 _handleAppStateChange@1:2231905 anonymous@1:645128 emit@1:115114 __callFunction@1:120571 anonymous@1:119079 __guard@1:120018 callFunctionReturnFlushedQueue@1:119037 at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72) at java.lang.reflect.Method.invoke at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372) at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188) at com.facebook.jni.NativeRunnable.run at android.os.Handler.handleCallback (Handler.java:942) at android.os.Handler.dispatchMessage (Handler.java:99) at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27) at android.os.Looper.loopOnce (Looper.java:201) at android.os.Looper.loop (Looper.java:288) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228) at java.lang.Thread.run (Thread.java:1012)

@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 getLocales(). @aleqsio - is there enough information here for you to go off of?