Open mfazekas opened 4 years ago
To reproduce:
react-native init mapboxtest2 --version 0.61.1
cd mapboxtest2
npm install @react-native-mapbox-gl/maps@8.0.0-rc2 --save
adb shell pm uninstall com.mapboxtest2
react-native run-android
# also start adb logcat to observe the soLoader error
Any input on the above?! I'd be happy to debug it, but I'd need some hints to where to look.
One thing that i found is that on old emulators - API 27 -
SysUtils.getSupportedAbis()
return 'x86` only,
while on devices we're having the issue with - API R -
SysUtils.getSupportedAbis()
return 'x86,
armeabi-v7`
Apparently they do seems to have some support for both x86
and some kind of arm
emulation.
Can confirm that we are seeing the same thing. The error occurs on API 30 and API 28 but not API 29.
Upgrading from React-Native 0.61 to 0.63 solved it for us.
I was running into the same issue but wasn't able to simply upgrade react-native because of some other dependencies.
The fix for this issue is part of SoLoader 0.8.1, you only need to force this dependency to a version higher than 0.8.0.
Root level build.gradle
allprojects {
repositories {
google()
center()
...
// force dependency versions on all subprojects
configurations.all {
resolutionStrategy {
// use 0.9.0 to fix crash on Android 11
force "com.facebook.soloader:soloader:0.9.0"
}
}
}
}
I was running into the same issue but wasn't able to simply upgrade react-native because of some other dependencies.
The fix for this issue is part of SoLoader 0.8.1, you only need to force this dependency to a version higher than 0.8.0.
Root level
build.gradle
allprojects { repositories { google() center() ... // force dependency versions on all subprojects configurations.all { resolutionStrategy { // use 0.9.0 to fix crash on Android 11 force "com.facebook.soloader:soloader:0.9.0" } } } }
This made my day. I was trying to make the apk from last 6 hours
I was running into the same issue but wasn't able to simply upgrade react-native because of some other dependencies.
The fix for this issue is part of SoLoader 0.8.1, you only need to force this dependency to a version higher than 0.8.0.
Root level
build.gradle
allprojects { repositories { google() center() ... // force dependency versions on all subprojects configurations.all { resolutionStrategy { // use 0.9.0 to fix crash on Android 11 force "com.facebook.soloader:soloader:0.9.0" } } } }
this worked for me. thanks a lot.
For OS 7 it is not working, for others it got fixed, any clue?
I was running into the same issue but wasn't able to simply upgrade react-native because of some other dependencies.
The fix for this issue is part of SoLoader 0.8.1, you only need to force this dependency to a version higher than 0.8.0.
Root level
build.gradle
allprojects { repositories { google() center() ... // force dependency versions on all subprojects configurations.all { resolutionStrategy { // use 0.9.0 to fix crash on Android 11 force "com.facebook.soloader:soloader:0.9.0" } } } }
Thank you for this fix. It works in most cases but there are still some devices causing issues even after these changes. For example I have seen One Plus 8 Pro
struggling with a similar issue (stack trace below) on Android 11
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.myspinny.inspection.rn/lib-3/libc++_shared.so" is for EM_AARCH64 (183) instead of EM_X86_64 (62) result: 0 result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:896)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:725)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:649)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:629)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:29)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1024)
at java.lang.Thread.run(Thread.java:923)
@sarthakpranesh we had the same issue in the exact same setup.
We're seeing this on devices such as Galaxy S9, One Plus 8, One Plus 5T,HUAWEI P30 All running Android 10.
React Native 0.70.6 React Native Gradle Plugin 0.70.3
I though I had solved the issue by upgrading to soloader:0.10.4+
as suggested by Google support but it doesn't seems so.
Here is my current config on react native 0.71.2
. In app/build.gradle
I have something like this:
android {
applicationVariants.all { variant ->
variant.outputs.each { output ->
// For each separate APK per architecture, set a unique version code as described here:
// https://developer.android.com/studio/build/configure-apk-splits.html
// Example: versionCode 1 will generate 1001 for armeabi-v7a, 1002 for x86, etc.
def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
def abi = output.getFilter(OutputFile.ABI)
if (abi != null) { // null for the universal-debug, universal-release variants
output.versionCodeOverride =
defaultConfig.versionCode * 1000 + versionCodes.get(abi)
}
}
}
}
dependencies {
implementation 'com.facebook.soloader:soloader:0.10.4+'
}
In build.gradle
I have:
allprojects {
repositories {
configurations.all {
resolutionStrategy {
force 'com.facebook.soloader:soloader:0.10.4+'
}
}
}
}
@cglacet does it work in react-native@0.71.3?
@RohovDmytro I have no idea, the problem with this issue is that I can't reproduce it myself, I only see crashlytics logs of customers experiencing the crash.
We're seeing this on devices such as Galaxy S9, One Plus 8, One Plus 5T,HUAWEI P30 All running Android 10.
React Native 0.70.6 React Native Gradle Plugin 0.70.3
Have you fixed this issue yet?
I was running into the same issue but wasn't able to simply upgrade react-native because of some other dependencies. The fix for this issue is part of SoLoader 0.8.1, you only need to force this dependency to a version higher than 0.8.0. Root level
build.gradle
allprojects { repositories { google() center() ... // force dependency versions on all subprojects configurations.all { resolutionStrategy { // use 0.9.0 to fix crash on Android 11 force "com.facebook.soloader:soloader:0.9.0" } } } }
Thank you for this fix. It works in most cases but there are still some devices causing issues even after these changes. For example I have seen
One Plus 8 Pro
struggling with a similar issue (stack trace below) on Android 11Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.myspinny.inspection.rn/lib-3/libc++_shared.so" is for EM_AARCH64 (183) instead of EM_X86_64 (62) result: 0 result: 0 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:896) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:725) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:649) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:629) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:29) at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1024) at java.lang.Thread.run(Thread.java:923)
I have same issue
We're also seeing this crash with RN 0.71.6 and SoLoader 0.10.4 on a OnePlus 8 Pro device running Android 11.
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_runtime.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/my.bundle.id/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
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1127)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:943)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:855)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:802)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:772)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:24)
I also have the error showing up in my crashlytics:
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_runtime.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.app..../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
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1127)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:943)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:855)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:802)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:772)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:24)
at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:369)
at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:316)
at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:94)
at expo.modules.ReactNativeHostWrapperBase.createReactInstanceManager(ReactNativeHostWrapperBase.kt:32)
at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:41)
at com.app.nohto.MainApplication.onCreate(MainApplication.java:67)
Device Brand: OnePlus Model: OnePlus8Pro Operating system Version: Android 11 Rooted: Yes
Ditto.
We're also seeing this crash with RN 0.71.6 and SoLoader 0.10.4 on a OnePlus 8 Pro device running Android 11.
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_runtime.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/my.bundle.id/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 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1127) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:943) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:855) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:802) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:772) at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:24)
I'm seeing this with oneplus8pro and soloader 10.5 as well:
implementation 'com.facebook.soloader:soloader:0.10.5+'
What's more confusing to me is: oneplus8pro seems to be a 64-bit ARM device, yet the code is expecting EM_X86_64 instead of EM_AARCH64...?
Unfortunately for now, I've had to shift away from using Hermes 😭 ... and since oneplus8pro is ARM 64-bit, it doesn't seem like I can build another bundle targeting just that...
Anyone have any other ideas on things to try?
Anyone found solution @vinnybad @JDouven ?
Anyone found solution @vinnybad @JDouven ?
No for me
+1 we have same issue here, any solution lately?
+1 having the same issue on OnePlus8Pro with Android 11
This issue affects our app as well, using RN 0.71. From Crashlytics we can see it mostly affects OnePlus and Google devices.
the same here RN: 0.71.6 REALM: 11.8.0 Metro: active
missing libhermes..
works fine in mode dev. release broke before splash
+1 having the same issue on OnePlus8Pro with Android 11
same issues
+1 having the same issue on OnePlus8Pro with Android 11
same issues
We noticed in our app it's mostly Android 8 and Android 11 on Google and OnePlus devices that it's happening.
We are noticing the same thing. Currently OnePlus and Android 11. We cant seem to replicate it though.
We have the same issue on OnePlus.
I'm on React Native 71.8 and I'm currently seeing this on Android 11 OnePlus devices.
Should I be worried about adding the line force "com.facebook.soloader:soloader:0.9.0"
across all configurations? I understand this mainly helps Android 8 and some Android 11 devices. Will this mess up the other devices I have that are on Android 11, 12, and 13?
I'm on React Native 71.8 and I'm currently seeing this on Android 11 OnePlus devices.
Should I be worried about adding the line
force "com.facebook.soloader:soloader:0.9.0"
across all configurations? I understand this mainly helps Android 8 and some Android 11 devices. Will this mess up the other devices I have that are on Android 11, 12, and 13?
Do you have physical access to the device? If so, you could see if libhermes is missing on the device via adb.
I'm on React Native 71.8 and I'm currently seeing this on Android 11 OnePlus devices. Should I be worried about adding the line
force "com.facebook.soloader:soloader:0.9.0"
across all configurations? I understand this mainly helps Android 8 and some Android 11 devices. Will this mess up the other devices I have that are on Android 11, 12, and 13?Do you have physical access to the device? If so, you could see if libhermes is missing on the device via adb.
Apparently SoLoader issues are supposed to be fixed on React Native 72. I’ve just released a new version of my app and will see if that fixes it
Our app is using RN 0.71.1
, soloader:0.10.4
with hermesEnabled=true
We see 2 separate issues:
Reported on OnePlus8Pro
, Android 11, similar to the original issue of this thread:
libc++_shared.so" is for EM_AARCH64 (183) instead of EM_X86_64 (62)
It's interesting, that One Plus 8
is also mentioned by @raldred
We're seeing this on devices such as Galaxy S9, One Plus 8, One Plus 5T,HUAWEI P30
The chipsets and their respective instruction sets are as follows:
So all of those devices are AARCH64 and it's unclear why the error says instead of EM_X86_64
Reported on Nexus 5X
, Android 8.1.0:
couldn't find DSO to load: libhermes.so
This one is different from original issue of this thread.
@cglacet what's the functional difference between adding com.facebook.soloader:soloader:0.10.4+
as a dependency in android/app/build.gradle vs. as a resolutionStrategy in android/build.gradle?
I'm on React Native 71.8 and I'm currently seeing this on Android 11 OnePlus devices. Should I be worried about adding the line
force "com.facebook.soloader:soloader:0.9.0"
across all configurations? I understand this mainly helps Android 8 and some Android 11 devices. Will this mess up the other devices I have that are on Android 11, 12, and 13?Do you have physical access to the device? If so, you could see if libhermes is missing on the device via adb.
Apparently SoLoader issues are supposed to be fixed on React Native 72. I’ve just released a new version of my app and will see if that fixes it
fixed??
I'm on React Native 71.8 and I'm currently seeing this on Android 11 OnePlus devices. Should I be worried about adding the line
force "com.facebook.soloader:soloader:0.9.0"
across all configurations? I understand this mainly helps Android 8 and some Android 11 devices. Will this mess up the other devices I have that are on Android 11, 12, and 13?Do you have physical access to the device? If so, you could see if libhermes is missing on the device via adb.
Apparently SoLoader issues are supposed to be fixed on React Native 72. I’ve just released a new version of my app and will see if that fixes it
fixed??
Yes it was fixed for me! My Android applications haven’t been getting this sort of crash since I did the work to upgrear to my React Native 72 version. I didn’t do any of the other SoLoader hacks at all
+1 Still facing issues
Yes it was fixed for me! My Android applications haven’t been getting this sort of crash since I did the work to upgrear to my React Native 72 version. I didn’t do any of the other SoLoader hacks at all
Still getting
Fatal Exception: java.lang.UnsatisfiedLinkError
dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/myapp-KP_lyfJO9YCo9WMKKk39Pg==/base.apk"],nativeLibraryDirectories=[/data/app/myapp-KP_lyfJO9YCo9WMKKk39Pg==/lib/arm64, /system/lib64, /system/vendor/lib64]]] couldn't find "libhermes.so"
after upgrading to rn 0.72 but not having
dlopen failed: "/lib-main/libc++_shared.so" is for EM_ARM (40) instead of EM_386
error anymore
+1 Still facing issues
This work for me
project.ext.react = [
enableHermes: true, // clean and rebuild if changing
]
if (enableHermes) {
// def hermesPath = "../../node_modules/hermes-engine/android/";
// debugImplementation files(hermesPath + "hermes-debug.aar")
// releaseImplementation files(hermesPath + "hermes-release.aar"
implementation("com.facebook.react:hermes-engine:0.69.12") { // replace the RN version with the one you are using
exclude group:'com.facebook.fbjni'
}
} else {
implementation jscFlavor
}
I'm using:
"react-native": "0.69.12",
did any one fix that ?
Still happening to some devices:
Nexus 5X One plus 8 pro
React-Native 0.72.4 Android NDK 23.1.7779620 minSdkVersion 21 compileSdkVersion 33 targetSdkVersion 33
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_runtime.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/fr.waeve.mob/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
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1228)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1044)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:956)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:903)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:869)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:24)
at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:379)
at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:325)
at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:96)
at expo.modules.ReactNativeHostWrapperBase.createReactInstanceManager(ReactNativeHostWrapperBase.kt:32)
at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:42)
at fr.waeve.mob.MainApplication.onCreate(MainApplication.java:76)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1194)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6735)
at android.app.ActivityThread.access$1300(ActivityThread.java:239)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1915)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7680)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:423)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
We have the same issue.
Android 8 & 11 Nexus 5X One Plus 8 Pro
"react-native": "0.72.4"
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1228)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1044)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:956)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:903)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:869)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:24)
at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:379)
at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:325)
at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:96)
at expo.modules.ReactNativeHostWrapperBase.createReactInstanceManager(ReactNativeHostWrapperBase.kt:32)
at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:42)
at dk.guloggratis.MainApplication.onCreate(MainApplication.java:71)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5740)
at android.app.ActivityThread.-wrap1()
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
Same issue,
One Plus 8 Pro Android 11
"react-native": "0.71.3"
if (hermesEnabled.toBoolean()) { implementation("com.facebook.react:hermes-android") } else { implementation jscFlavor }
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_runtime.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/{mypackagename}/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
Same issue,
One Plus 8 Pro Android 11
"react-native": "0.71.3"
if (hermesEnabled.toBoolean()) { implementation("com.facebook.react:hermes-android") } else { implementation jscFlavor }
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_runtime.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/{mypackagename}/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
The same for me((
Same issue, One Plus 8 Pro Android 11 "react-native": "0.71.3" if (hermesEnabled.toBoolean()) { implementation("com.facebook.react:hermes-android") } else { implementation jscFlavor } 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_runtime.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/{mypackagename}/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
The same for me((
The same for me too! Using RN 0.66.5
Seeing this issue as well.
RN: 0.72.7
` buildToolsVersion = "33.0.0" minSdkVersion = 23 compileSdkVersion = 33 targetSdkVersion = 33 kotlin_version = '1.6.10' // <- add this line ndkVersion = "21.4.7075529"
react = [
enableHermes: true, // clean and rebuild if changing
enableVmCleanup: false, //this
] `
Brand:Google Model:Pixel 6 Pro Orientation:Portrait RAM free: 1.88 GB Disk free: 1.58 GB
Operating System Version:Android 12 Orientation:Portrait Rooted:No
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_runtime.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/watch.panpan/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 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1127) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:943) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:855) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:802) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:772) at com.facebook.hermes.reactexecutor.HermesExecutor.loadLibrary(HermesExecutor.java:26)
Here too on RN 0.72.4, all OnePlus8Pro devices
Same here, OnePlus8Pro and RN 0.63.0
Same here, OnePlus8Pro and react-native 0.72.6
Same here, OnePlus8Pro on 0.70.6
We're having
.so
loading error when running app on Android emulator R level. Doesn't seems to appear on API 29.I've verified that the apk has correct architecture in the proper folder:
After apk install the lib folder contains proper i386 .so-s. But when starting the app the
lib-main
folder contains ARM .so-s.See the relevant logcat in this gist https://gist.github.com/mfazekas/c593726e061a59d265835ead1c5db0dd
Not sure if related but the log has those line:
I can confirm that he file with length 997224 is 386. The arm version which is incorrectly used has
575328
bytes.https://github.com/react-native-mapbox-gl/maps/issues/737