Exception in HostObject::get: <unknown>

[donovanhiland]

Describe your environment

• react-native-localize 1.0.3
• react-native 0.59.3
• Target platform: Android
• Device:
  • Manufacturer: Tecno, OS: 7.0
  • Manufacturer: Infinix, OS: 7.0 or 8.1.0
  • Manufacturer: OnePlus, OS: 9.0
  • Manufacturer: Pixel, OS: 9.0
• OS: 7, 8, 8.1 ,9
• DevTools: N/A
• buildToolsVersion: 28.0.3

How to repeat issue and example

import { findBestAvailableLanguage } from 'react-native-localize'

expected it not to crash but it crashes on the above devices with:

Exception in HostObject::get: <unknown>

Some context around this error: This does not happen very often. Probably something like 1% of the time but it does result in an unrecoverable crash we think. We're seeing this reported through bugsnag and we don't have a device to reproduce this on. Thought it would be worth a report anyway. Maybe you all have some context on this error.

[zoontek]

@donovanhiland Do you have a more complete Stacktrace?

[DimitryDushkin]

Might be related facebook/react-native#24607

[zoontek]

@DimitryDushkin So it seems that getting a constant on this devices results sometimes in a crash. We have to find which one.

[DimitryDushkin]

Yeah, in our case some of constants turned out to return nil instead of NSString.

[gbalduzzi]

Are there some workaround for this issue? I'm still experiencing it and I honestly don't know how to fix it

[zoontek]

@gbalduzzi Please provides some details (OS version, RN version, simulator / phone), etc. As I don't even know how to reproduce the error, it's very hard to find the cause 😞

I will add some guards on every functions, but it would be better to identify where the problem is.

[gbalduzzi]

I managed to reproduce the error by adding in my phone languages the en_XA locale (called [Pseudo locale]

[zoontek]

@gbalduzzi On which Android version / phone / simulator?

[gbalduzzi]

I tested on a Huawei P20 Lite with android 8.0.0, but it also occurred in a OnePlus 3T with Android 9. I got the feeling that it's more about some locales than about some specifics phone/android versions

[zoontek]

@gbalduzzi Thanks! It can be enough to reproduce the error and investigate 🙂

[gbalduzzi]

Sharing some more info I collected while testing:

• Removing the call to findBestAvailableLanguage resolved the problem on the library
• Other libraries share the same issue: every call to react-native-device-info will result in the same error
• Even having the pseudo locale as second or third language will result in an error
• It seems to fail while parsing the locale currency

[zoontek]

@gbalduzzi Which version of the library are you using? A fix for this issue has been released in version 1.0.4: #38 (it might not works in every cases)

[zoontek]

@gbalduzzi I made a new release (1.2.0) with fallbacks for unknown countries / currencies.