App: [$250] đź’Ą Crash đź’Ą `com.facebook.soloader.SoLoader$1.load`
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn’t find DSO to load: libhermes.so caused by: couldn’t find DSO to load: libjsi.so caused by: couldn’t find DSO to load: libfolly_json.so caused by: couldn’t find DSO to load: libglog.so caused by: couldn’t find DSO to load: libc++_shared.so caused by: dlopen failed: “/data/data/com.expensify.chat/lib-3/libc++_shared.so” is for EM_AARCH64 (183) instead of EM_X86_64 (62) result: 0 result: 0 result: 0 result: 0 result: 0
SoLoader.java line 405 com.facebook.soloader.SoLoader$1.load
Number of Crashes: 26
Device Information
- Platforms: Android
- App Versions:
1.1.82-5 - Devices: OnePlus OnePlus8Pro 11
Stacktraces
Android 1.1.82-5
com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:918)
com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl (SoLoader.java:740)
com.facebook.soloader.SoLoader.loadLibraryBySoName (SoLoader.java:654)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:634)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:582)
com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> (HermesExecutor.java:20)
com.facebook.hermes.reactexecutor.HermesExecutorFactory.create (HermesExecutorFactory.java:29)
com.facebook.react.ReactInstanceManager$5.run (ReactInstanceManager.java:1066)
java.lang.Thread.run (Thread.java:923)
Internal Firebase Info
đź’Ą DO NOT EDIT THIS SECTION đź’Ą
Crash IDs: fd07e92456e1225a6955d168c0d130a8
Exception: couldn't find DSO to load: libhermes.so caused by: couldn't find DSO to load: libjsi.so caused by: couldn't find DSO to load: libfolly_json.so caused by: couldn't find DSO to load: libglog.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.expensify.chat/lib-3/libc++_shared.so" is for EM_AARCH64 (183) instead of EM_X86_64 (62) result: 0 result: 0 result: 0 result: 0 result: 0
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 26 (10 by maintainers)
This seems to be a known issue: https://github.com/facebook/react-native/issues/29528#issuecomment-737734746 Should be a non-issue in terms of react-native version upgrades but I understand your concern around that. Updating the react native template makes sense.
Happy to open that PR, I have a corresponding proposal on Upwork.
That would be a nice feature – feel free to post a feature request in #expensify-open-source.
Thanks for confirming, it’s possible to do this if we wanted to, but I agree it’s better to keep them separated.
I haven’t come across this one yet. Do we have reproducible steps?