Comments (93)
approached
commented on May 7, 2024
76
What fixed it for us what upgrading the SOLoader.
In android/app/build.gradle:
dependencies {
implementation 'com.facebook.soloader:soloader:0.9.0+'
from soloader.
soroushm
commented on May 7, 2024
30
go to the android directory and run dis command "./gradle clean" its work for me
from soloader.
syrakozz
commented on May 7, 2024
22
cd android && ./gradlew clean
This is worked for me
from soloader.
oprisnik
commented on May 7, 2024
14
Version 0.8.1 has been released which includes this fix.
from soloader.
sintylapse
commented on May 7, 2024
12
Still an issue for me with version 0.8.1, only error message a little bit changed in crashlitics
couldn't find DSO to load: libhermes.so result: 0
instead of
couldn't find DSO to load: libhermes.so
from soloader.
bigggge
commented on May 7, 2024
11
Have the same issue with React Native 0.61.5 and SoLoader 0.8.0
Device: Galaxy J2 Prime ,Redmi Note 4, HUAWEI Y3II
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
at java.lang.Thread.run(Thread.java:818)
from soloader.
soroushm
commented on May 7, 2024
10
same here on upgrade react-native to 62.2
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java)
at java.lang.Thread.run(Thread.java:818)
from soloader.
arjun1194
commented on May 7, 2024
8
i am still facing the same problem, issue is not resolved. i am using soloader:0.10.3
from soloader.
thanakij
commented on May 7, 2024
7
Another one from me, but this time I have updated SoLoader to the latest version (0.10.1).
Version:
- react-native 0.62.2
- implementation 'com.facebook.soloader:soloader:0.10.1+'
- Distribution: Android App Bundle (AAB)
Device: Pixel 3 XL (Android 9)
Log:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: e.f.y0.a[root = /data/data/com.?/lib-main flags = 1]
SoSource 1: e.f.y0.c[root = /data/app/com.?-QVmp1vNO5-Hi12o_PNJV0w==/lib/arm64 flags = 0]
SoSource 2: e.f.y0.c[root = /vendor/lib64 flags = 2]
SoSource 3: e.f.y0.c[root = /system/lib64 flags = 2]
Native lib dir: /data/app/com.?-QVmp1vNO5-Hi12o_PNJV0w==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:918)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:740)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:654)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:634)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:582)
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:997)
at java.lang.Thread.run(Thread.java:764)
from soloader.
mars-lan
commented on May 7, 2024
6
@BurntBrunch thanks for looking into this. Actually it seems that the "brokenness" affects real devices as well. Seeing similar crashes in production on these devices running Android 6-9
Nexus 6
Xiaomi Mi 9X, Redmi Pro, Mi 5
Trend TaintArt for x86
X9 (Maybe Vivo X9?)
Vivo s1
Huawei Enjoy 9s
Others (Samsung, Asus, LGE, Google, Lenovo)
Unfortunately the stack trace from Firebase is limited
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libv8executor.so
com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:789)
com.facebook.soloader.SoLoader.loadLibraryBySoName (SoLoader.java:639)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:577)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:525)
com.facebook.v8.reactexecutor.V8Executor.<clinit> (V8Executor.java:16)
com.facebook.v8.reactexecutor.V8ExecutorFactory.create (V8ExecutorFactory.java:17)
com.facebook.react.ReactInstanceManager$5.run (ReactInstanceManager.java:952)
java.lang.Thread.run (Thread.java:761)
from soloader.
mars-lan
commented on May 7, 2024
6
Still seeing similar issue with SoLoader 0.8.2 with the following (not very helpful) error message. @BurntBrunch any update?
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libv8executor.so result: 0
com.facebook.soloader.SoLoader.doLoadLibraryBySoName
from soloader.
thanakij
commented on May 7, 2024
6
Hi @BurntBrunch, this is another one to help you with the debugging.
Version:
- react-native 0.62.2
implementation 'com.facebook.soloader:soloader:0.9.0+'
Distribution: Android App Bundle (AAB)
Device: Galaxy S5 (Android 5.1.1)
Log:
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so
SoSource 0: e.f.z0.a[root = /data/data/com.?/lib-main flags = 1]
SoSource 1: e.f.z0.c[root = /data/app/com.?-1/lib/x86 flags = 0]
SoSource 2: e.f.z0.c[root = /system/vendor/lib flags = 2]
SoSource 3: e.f.z0.c[root = /system/lib flags = 2]
Native lib dir: /data/app/com.?-1/lib/x86 result: 0
com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:896)
com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl (SoLoader.java:725)
com.facebook.soloader.SoLoader.loadLibraryBySoName (SoLoader.java:649)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:629)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:577)
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:997)
from soloader.
mightyorange
commented on May 7, 2024
6
go to the android directory and run dis command "./gradle clean" its work for me
@soroushm Thanks. Is it ./gradlew clean ? ---> This command fixed the issue on my side...
from soloader.
BurntBrunch
commented on May 7, 2024
5
Hi, sorry about the delay!
I've investigated this a bit and I am reasonably convinced that particular emulator image (Pie SDK 28 Google APIs x86) is just broken.
The Google APIs version is reporting both x86 and armv7 compatibility when the non-Google version correctly only reports x86. As a workaround, can you try using an SDK 29 (Q) Google APIs image? In my testing, that image should behave better.
I've also posted this on the Android bug tracker here.
from soloader.
mars-lan
commented on May 7, 2024
5
Definitely seeing fewer crashes with 0.9.0 but still not zero. Good news is that it's giving more logs now. Below is an example for Nexus 6. Looks like it's still trying to load from an incorrect location.
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libv8executor.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.invisatime/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/com.invisatime-1/lib/arm flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/com.invisatime-1/lib/arm
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.v8.reactexecutor.V8Executor.<clinit>(V8Executor.java:16)
at com.facebook.v8.reactexecutor.V8ExecutorFactory.create(V8ExecutorFactory.java:20)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:997)
at java.lang.Thread.run(Thread.java:761)
from soloader.
velevtzvetlin
commented on May 7, 2024
4
@saczuac
does this fix it for you? It did for me:
configurations.all {
resolutionStrategy {
force "com.facebook.soloader:soloader:0.8.2"
}
}
from soloader.
xserxses
commented on May 7, 2024
3
Happening to me as well on production on version 0.8.1 of SoLoader.
Xperia X Performance - Android 8.0.0
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: couldn't find DSO to load: libfb.so caused by: Error: Cannot load /data/user/0/com.mypackage/lib-main/libfb.so result: 0 result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:825)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:673)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:611)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:559)
at com.facebook.yoga.YogaNative.<clinit>(YogaNative.java:15)
at com.facebook.yoga.YogaNative.jni_YGConfigNew(YogaNative.java)
at com.facebook.yoga.YogaConfig.<init>(YogaConfig.java:20)
at com.facebook.yoga.YogaConfigFactory.create(YogaConfigFactory.java:5)
at com.facebook.litho.yoga.LithoYogaFactory.createYogaConfig(LithoYogaFactory.java:26)
at com.facebook.litho.NodeConfig.<clinit>(NodeConfig.java:45)
at com.facebook.litho.NodeConfig.getYogaConfig(NodeConfig.java:66)
from soloader.
NetPumi2
commented on May 7, 2024
3
Some more data from me
Setup:
"react-native": "0.63.0"
implementation 'com.facebook.soloader:soloader:0.9.0+'
enableHermes: false
Distribution: Android App Bundle (AAB)
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/se.myApp.myApp/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/se.myApp.myApp-1/lib/arm flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/se.myApp.myApp-1/lib/arm
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:1017)
at java.lang.Thread.run(Thread.java:818)
from soloader.
Poojapandey89
commented on May 7, 2024
3
Any luck for the issue? Have tried multiple solutions but still facing it. The same issue is causing number of crashes in production app.
"react-native": "0.63.0"
implementation 'com.facebook.soloader:soloader:0.9.0+'
from soloader.
Daavidaviid
commented on May 7, 2024
3
Me too.
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so SoSource 0: com.facebook.soloader.ApkSoSource
I'm using soloader 0.9.0+ and it happened since the update to 0.63.2.
It happened on devices with Android 10 and 11. Don't know why tho.
from soloader.
ghasemikasra39
commented on May 7, 2024
3
@saczuac
does this fix it for you? It did for me:configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.8.2" } }
Did not help for me.
from soloader.
prox2
commented on May 7, 2024
3
@simpleton
as @thanakij I am having this issue only on android 11
I was facing the issue yesterday and Crashlytics was reporting this crash with the following logs:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.a[root = /data/data/com.xxx/lib-main flags = 1]
SoSource 1: com.facebook.soloader.c[root = /data/app/~~4hdNB904_wPx4ByZ7-TUcQ==/com.xxx-yEWAHbjKZX3Pd5CctUWLDg==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.c[root = /vendor/lib64 flags = 2]
SoSource 3: com.facebook.soloader.c[root = /system/lib64 flags = 2]
Native lib dir: /data/app/~~4hdNB904_wPx4ByZ7-TUcQ==/com.xxx-yEWAHbjKZX3Pd5CctUWLDg==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:262)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:99)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:2)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:100)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:1)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:2)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:58)
at java.lang.Thread.run(Thread.java:923)
I am using implementation "com.facebook.soloader:soloader:0.10.3+"
However when i opened the run logs in android studio i saw the following error after the app crashes
Caused by java.lang.RuntimeException: Requested enabled DevSupportManager, but DevSupportManagerImpl class was not found or could not be created
at com.facebook.react.devsupport.DevSupportManagerFactory.create(DevSupportManagerFactory.java:90)
at com.facebook.react.ReactInstanceManager.<init>(ReactInstanceManager.java:237)
at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:280)
at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:87)
at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:39)
at com.xxx.MainApplication.onCreate(MainApplication.java:51)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7573)
at android.app.ActivityThread.access$1500(ActivityThread.java:301)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2169)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:246)
at android.app.ActivityThread.main(ActivityThread.java:8633)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
this error is actually caused by implementation 'com.squareup.okhttp3:okhttp:4.9.2'
so what i added i have added
implementation 'com.squareup.okhttp3:okhttp:4.9.2'
implementation 'com.squareup.okhttp3:logging-interceptor:4.4.1'
implementation 'com.squareup.okhttp3:okhttp-urlconnection:4.4.1'
in android/app/build.gradle
then i cleaned the build folder and reinstall the app again and it is working without any crash even no more reported crashes in firebase Crashlytics
Honestly I have no idea how the Crashlytics is reporting fatal error related to soloader while the issue was caused by okhttp
from soloader.
tusharsarkar
commented on May 7, 2024
3
Changed the version to 0.10.1 solve the issue at my end.
implementation 'com.facebook.soloader:soloader:0.10.1+'
from soloader.
pratheepkanati
commented on May 7, 2024
2
if you using proguard
try this rule's worked for me
-keep class com.facebook.soloader.{*;}
-keep class com.facebook.yoga.{;}
-keep class com.facebook.jni.**{;}
-keep class com.facebook.fbjni.**{*;}
from soloader.
charleston10
commented on May 7, 2024
2
I'm a native android programmer, and this problem happens when compiling the app through Play from the android studio itself
Behind it, it generates an apk with ABI with simpler architecture for the OS
If you generate the APK via Build or via ADB, the APK architecture will be generated using the architecture defined by build.gradle or the standard architecture
In this case I want to make it clear, that there is a difference between creating apk via Play and via Build / ADB
from soloader.
charleston10
commented on May 7, 2024
2
@charleston10 Interesting, Thank you so much for your tips! And Do you know what could we do to fix this issue?
I believe it is not a problem in the RN, but in how the android studio behaves in generating an apk
you can fix it, but I wouldn’t put much effort into it, since it’s a way the tool works
one of the alternatives and force the type of the build setting to ABI for the same architecture as RN
ABI - Application Binary Interface
See https://developer.android.com/studio/build/configure-apk-splits
from soloader.
thanakij
commented on May 7, 2024
2
We have upgraded soloader to 0.10.3 but somehow Crashlytics is still reporting this issue...
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so SoSource 0: c.g.b1.d[root = /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 flags = 0] SoSource 1: c.g.b1.c[root = null] SoSource 2: c.g.b1.d[root = /vendor/lib flags = 2] SoSource 3: c.g.b1.d[root = /system/lib flags = 2] Native lib dir: /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 result: 0
This time the report says the device is running Android 8.1.0 (Nexus 5X) at SoLoader.java line 1098.
from soloader.
msgharpu
commented on May 7, 2024
2
We are also seeing similar crashes in Android 10 and 11 devices with RN version = 0.64 and Soloader = 0.8.2.
Is there any update on this bug? or anyone knows of a workaround?
from soloader.
nagasai65
commented on May 7, 2024
2
@tusharsarkar @nagasai65 what RN version are you guys on? facing same issue, soloader is
0.10.3+, and RN is0.66.0
Same 0.66, make sure remove the plus on suffix
implementation 'com.facebook.soloader:soloader:0.10.1+' -> implementation 'com.facebook.soloader:soloader:0.10.1'
This works for me
from soloader.
vpeeee
commented on May 7, 2024
1
去掉defaultConfig里面的 ndk
在外面加上以下代码:
splits {
abi {
reset()
enable enableSeparateBuildPerCPUArchitecture
universalApk false // If true, also generate a universal APK
include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
}
}
亲测有效, 不知道为啥
from soloader.
khaishien
commented on May 7, 2024
1
i managed to resolve this crash by releasing apk instead of aab for playstore.
version for the production app
"react-native": "0.61.5"
force 'com.facebook.soloader:soloader:0.9.0'
it should be an issue on how bundletool manage the native library with the aab package while install into devices through playstore.
from soloader.
saczuac
commented on May 7, 2024
1
Same issue here, with:
Setup:
"react-native": "0.63.2"
implementation 'com.facebook.soloader:soloader:0.9.0+'
enableHermes: false
Distribution: Android App Bundle (AAB)
Device: Nexus 5X (Android 6.0.1)
Log:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.metropolis/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/com.metropolis-1/lib/arm flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/com.metropolis-1/lib/arm
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.(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:29)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1017)
at java.lang.Thread.run(Thread.java:818)
from soloader.
ghasemikasra39
commented on May 7, 2024
1
Same here:
Version:
"react-native": "0.64.1"
implementation 'com.facebook.soloader:soloader:0.10.1'
enableHermes: true
E/AndroidRuntime: FATAL EXCEPTION: create_react_context
Process: one.realnote.app, PID: 15083
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so caused by: couldn't find DSO to load: libjsi.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/one.realnote.app/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/one.realnote.app-DyBwcPq-Y_Q92-gHnKVpLA==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
Native lib dir: /data/app/one.realnote.app-DyBwcPq-Y_Q92-gHnKVpLA==/lib/arm64
result: 0 result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:918)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:740)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:654)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:634)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:582)
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:929)
Caused by: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjsi.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/one.realnote.app/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/one.realnote.app-DyBwcPq-Y_Q92-gHnKVpLA==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
Native lib dir: /data/app/one.realnote.app-DyBwcPq-Y_Q92-gHnKVpLA==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:918)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:740)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:640)
at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:121)
at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:477)
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:860)
... 8 morefrom soloader.
agrass
commented on May 7, 2024
1
Hello! this error still with the configuration SoLoader 0.9+ when using RN 59. Anyone already managed to fix this issue? Thanks
java.lang.UnsatisfiedLinkErrorSoLoader.java:896
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libv8executor.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.app/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/com.app-1/lib/arm flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/com.app-1/lib/arm
from soloader.
RodolfoGS
commented on May 7, 2024
1
@agrass I'm not sure if fix libv8executor.so too ¯\_(ツ)_/¯
from soloader.
He1nr1chK
commented on May 7, 2024
1
I had the issue on RN version 64.2 and what solved it for me was upgrading my hermes-engine version to 0.7.0. Apparently there is strict version compatibility. Hope this saves someone the 4 hours I just wasted.
from soloader.
prox2
commented on May 7, 2024
1
We have upgraded soloader to 0.10.3 but somehow Crashlytics is still reporting this issue...
Fatal Exception: java.lang.UnsatisfiedLinkError couldn't find DSO to load: libhermes.so SoSource 0: c.g.b1.d[root = /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 flags = 0] SoSource 1: c.g.b1.c[root = null] SoSource 2: c.g.b1.d[root = /vendor/lib flags = 2] SoSource 3: c.g.b1.d[root = /system/lib flags = 2] Native lib dir: /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 result: 0This time the report says the device is running Android 8.1.0 (Nexus 5X) at SoLoader.java line 1098.
me too having same issue with version 0.10.3 and Android 11
from soloader.
thanakij
commented on May 7, 2024
1
Hi @simpleton, please see the log below:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: c.g.b1.d[root = /data/app/com.xxx-QOZMQQzcNNsbGdCAr64Kcw==/lib/arm64 flags = 0]
SoSource 1: c.g.b1.c[root = null]
SoSource 2: c.g.b1.d[root = /system/lib64 flags = 2]
SoSource 3: c.g.b1.d[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/com.xxx-QOZMQQzcNNsbGdCAr64Kcw==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743)
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:997)
at java.lang.Thread.run(Thread.java:764)
from soloader.
thanakij
commented on May 7, 2024
1
(1) I cannot reproduce this myself.
(2) Because Crashlytics is saying the crash is for line 1098, this should just help confirm that I am using the latest v0.10.3.
I have pinned the version of SoLoader to be 0.10.3 in my android/app/build.xml:
implementation "com.facebook.soloader:soloader:0.10.3+"
(3) Anyway, my estimate is that around 0.08% of my Android users have experienced this crash.
From the pattern in my Crashlytics, trying to make sense out of it,
it is likely that only some certain devices are affected.
It means that if this issue affects a user, she will just have a consistent early crash every time when she tries to open the app.
But for most users, they wouldn't run into this same issue.
from soloader.
simpleton
commented on May 7, 2024
1
0.10.3 should fix this issue
…On Tue, Jan 11, 2022 at 9:34 PM Mayuresh Gharpure ***@***.***> wrote:
We are also seeing similar crashes in Android 10 and 11 devices with RN
version = 0.64 and Soloader = 0.8.2.
Is there any update on this bug? or anyone knows of a workaround?
—
Reply to this email directly, view it on GitHub
<#55 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADO6YQQENUZAPEEYVS3IITUVUHFFANCNFSM4J2NKS4A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from soloader.
sn123
commented on May 7, 2024
1
This is giving me sleepless nights now - I have an app which keeps getting rejected in review since it crashes on reviewers phone. The phones in question are:
- Samsung Galaxy A52, Pixel 4xl - unfortunately, I don't have access to any of these phones and it works on the phones that we do have.
Have pinned soloader to .10.3
implementation 'com.facebook.soloader:soloader:0.10.3+'
and also added this in ndk filter as per another bug workaround:
ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'
Still no dice. Using RN "react-native": "^0.63.4"
Below is the error log in crashlytics:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so
SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64 flags = 0]
SoSource 1: com.facebook.soloader.DirectApkSoSource[root = null]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743)
at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:34)
at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:17)
at com.facebook.react.bridge.Arguments.createMap(Arguments.java:155)
at expo.modules.updates.UpdatesController$1.onBackgroundUpdateFinished(UpdatesController.java:266)
at expo.modules.updates.loader.LoaderTask$3.onFailure(LoaderTask.java:263)
at expo.modules.updates.loader.RemoteLoader.finishWithError(RemoteLoader.java:123)
at expo.modules.updates.loader.RemoteLoader.access$000(RemoteLoader.java:22)
at expo.modules.updates.loader.RemoteLoader$1.onFailure(RemoteLoader.java:78)
at expo.modules.updates.loader.FileDownloader$2.onResponse(FileDownloader.java:109)
at expo.modules.updates.loader.FileDownloader$4.onResponse(FileDownloader.java:243)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
aabs are being generated using appcenter to clearing gradle build cache isn't required. Any pointers on what could be done?
from soloader.
nasir-azeemi
commented on May 7, 2024
1
@tusharsarkar @nagasai65 what RN version are you guys on?
facing same issue, soloader is 0.10.3+, and RN is 0.66.0
from soloader.
kirannk-1306
commented on May 7, 2024
1
This is giving me sleepless nights now - I have an app which keeps getting rejected in review since it crashes on reviewers phone. The phones in question are:
- Samsung Galaxy A52, Pixel 4xl - unfortunately, I don't have access to any of these phones and it works on the phones that we do have.
Have pinned soloader to .10.3
implementation 'com.facebook.soloader:soloader:0.10.3+'and also added this in ndk filter as per another bug workaround:ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'Still no dice. Using RN"react-native": "^0.63.4"Below is the error log in crashlytics:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64 flags = 0] SoSource 1: com.facebook.soloader.DirectApkSoSource[root = null] SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2] SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2] Native lib dir: /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64 result: 0 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743) at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:34) at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:17) at com.facebook.react.bridge.Arguments.createMap(Arguments.java:155) at expo.modules.updates.UpdatesController$1.onBackgroundUpdateFinished(UpdatesController.java:266) at expo.modules.updates.loader.LoaderTask$3.onFailure(LoaderTask.java:263) at expo.modules.updates.loader.RemoteLoader.finishWithError(RemoteLoader.java:123) at expo.modules.updates.loader.RemoteLoader.access$000(RemoteLoader.java:22) at expo.modules.updates.loader.RemoteLoader$1.onFailure(RemoteLoader.java:78) at expo.modules.updates.loader.FileDownloader$2.onResponse(FileDownloader.java:109) at expo.modules.updates.loader.FileDownloader$4.onResponse(FileDownloader.java:243) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923)aabs are being generated using appcenter to clearing gradle build cache isn't required. Any pointers on what could be done?
This is giving me sleepless nights now - I have an app which keeps getting rejected in review since it crashes on reviewers phone. The phones in question are:
- Samsung Galaxy A52, Pixel 4xl - unfortunately, I don't have access to any of these phones and it works on the phones that we do have.
Have pinned soloader to .10.3
implementation 'com.facebook.soloader:soloader:0.10.3+'and also added this in ndk filter as per another bug workaround:ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'Still no dice. Using RN"react-native": "^0.63.4"Below is the error log in crashlytics:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64 flags = 0] SoSource 1: com.facebook.soloader.DirectApkSoSource[root = null] SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2] SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2] Native lib dir: /data/app/~~1r_ebB2J2znWSeO1aO24nw==/com.omozing_developers.omozing_updated-858k-71AkAC-TA0IVHCXyA==/lib/arm64 result: 0 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743) at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:34) at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:17) at com.facebook.react.bridge.Arguments.createMap(Arguments.java:155) at expo.modules.updates.UpdatesController$1.onBackgroundUpdateFinished(UpdatesController.java:266) at expo.modules.updates.loader.LoaderTask$3.onFailure(LoaderTask.java:263) at expo.modules.updates.loader.RemoteLoader.finishWithError(RemoteLoader.java:123) at expo.modules.updates.loader.RemoteLoader.access$000(RemoteLoader.java:22) at expo.modules.updates.loader.RemoteLoader$1.onFailure(RemoteLoader.java:78) at expo.modules.updates.loader.FileDownloader$2.onResponse(FileDownloader.java:109) at expo.modules.updates.loader.FileDownloader$4.onResponse(FileDownloader.java:243) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923)aabs are being generated using appcenter to clearing gradle build cache isn't required. Any pointers on what could be done?
Hi @sn123, Please let me know if you found any solution to fix this app crash issue.
from soloader.
mars-lan
commented on May 7, 2024
Seeing a similar issue on 0.8.0 with a different stack trace.
2019-12-26 11:43:06.860 14603-14619/? W/System.err: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.awesomeproject/lib-main/libc++_shared.so" has unexpected e_machine: 40 (EM_ARM)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at java.lang.Runtime.load0(Runtime.java:928)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at java.lang.System.load(System.java:1633)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader$1.load(SoLoader.java:393)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:77)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:587)
2019-12-26 11:43:06.861 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:111)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:587)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:111)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8Executor.<clinit>(V8Executor.java:16)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8ExecutorFactory.create(V8ExecutorFactory.java:17)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
2019-12-26 11:43:06.862 14603-14619/? W/System.err: at java.lang.Thread.run(Thread.java:764)
2019-12-26 11:43:06.863 14603-14619/? E/SoLoader: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-main/libc++_shared.so" has unexpected e_machine: 40 (EM_ARM)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: com.facebook.soloader.SoLoader$WrongAbiError: APK was built for a different platform
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:645)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:587)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:111)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:587)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:111)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
2019-12-26 11:43:06.864 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8Executor.<clinit>(V8Executor.java:16)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8ExecutorFactory.create(V8ExecutorFactory.java:17)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at java.lang.Thread.run(Thread.java:764)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: Caused by: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-main/libc++_shared.so" has unexpected e_machine: 40 (EM_ARM)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.865 14603-14619/? W/System.err: ... 18 more
2019-12-26 11:43:06.865 14603-14619/? E/SoLoader: couldn't find DSO to load: libfb.so caused by: APK was built for a different platform
2019-12-26 11:43:06.866 14603-14619/? W/System.err: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libfb.so caused by: APK was built for a different platform
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:587)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadDependencies(DirectorySoSource.java:111)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.UnpackingSoSource.loadLibrary(UnpackingSoSource.java:458)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:731)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
2019-12-26 11:43:06.866 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8Executor.<clinit>(V8Executor.java:16)
2019-12-26 11:43:06.867 14603-14619/? W/System.err: at com.facebook.v8.reactexecutor.V8ExecutorFactory.create(V8ExecutorFactory.java:17)
2019-12-26 11:43:06.867 14603-14619/? W/System.err: at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
2019-12-26 11:43:06.867 14603-14619/? W/System.err: at java.lang.Thread.run(Thread.java:764)
2019-12-26 11:43:06.867 14603-14619/? E/SoLoader: couldn't find DSO to load: libv8executor.so caused by: couldn't find DSO to load: libfb.so caused by: APK was built for a different platform
--------- beginning of crash
2019-12-26 11:43:06.868 14603-14619/? E/AndroidRuntime: FATAL EXCEPTION: create_react_context
Process: com.awesomeproject, PID: 14603
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libv8executor.so caused by: couldn't find DSO to load: libfb.so caused by: APK was built for a different platform
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
at com.facebook.v8.reactexecutor.V8Executor.<clinit>(V8Executor.java:16)
at com.facebook.v8.reactexecutor.V8ExecutorFactory.create(V8ExecutorFactory.java:17)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
at java.lang.Thread.run(Thread.java:764)
Was able to reproduce this reliably by applying the following patch to the standard RN starter project on a stock "Google Play Intel x86 Atom System Image API 28 rev 9" emulator.
--- build.gradle 2019-12-26 11:52:32.000000000 -0800
+++ build.gradle.original 2019-12-26 11:52:04.000000000 -0800
@@ -191,12 +191,6 @@
}
}
-configurations.all {
- resolutionStrategy {
- force "com.facebook.soloader:soloader:0.8.0"
- }
-}
-
// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
Also attached a a copy of the project to help debug.
from soloader.
xserxses
commented on May 7, 2024
Update: Downgrading to 0.6.1 didn't fix the problem. After releasing it to production we faced some crashes from Sony devices.
Xperia XZ 33%
Xperia X Compact 29%
Xperia X 17%
Xperia X Performance 14%
Xperia XA 5%
Xperia Z5 Compact 1%
Xperia Z5 1%
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: couldn't find DSO to load: libfb.so caused by: Error: Cannot load /data/user/0/com.mypackagi/lib-main/libfb.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 774(SoLoader.java:774)
at com.facebook.soloader.SoLoader.loadLibraryBySoName + 627(SoLoader.java:627)
at com.facebook.soloader.SoLoader.loadLibrary + 565(SoLoader.java:565)
at com.facebook.soloader.SoLoader.loadLibrary + 513(SoLoader.java:513)
at com.facebook.yoga.YogaNative.<clinit> + 15(YogaNative.java:15)
at com.facebook.yoga.YogaNative.jni_YGConfigNew(YogaNative.java)
at com.facebook.yoga.YogaConfig.<init> + 20(YogaConfig.java:20)
at com.facebook.yoga.YogaConfigFactory.create + 5(YogaConfigFactory.java:5)
at com.facebook.litho.yoga.LithoYogaFactory.createYogaConfig + 26(LithoYogaFactory.java:26)
at com.facebook.litho.NodeConfig.<clinit> + 45(NodeConfig.java:45)
at com.facebook.litho.NodeConfig.getYogaConfig + 66(NodeConfig.java:66)
from soloader.
BurntBrunch
commented on May 7, 2024
Google are reporting that the image is actually correct because there's runtime dynamic code translation in that image.
I have some thoughts on how to fix all this but it's not trivial, especially because I don't know what SELinux will let me do. Stay tuned.
from soloader.
mars-lan
commented on May 7, 2024
Thanks for the investigation, @BurntBrunch. Look forward to a new release that includes 20198bf
from soloader.
BurntBrunch
commented on May 7, 2024
@mars-lan this commit addressed the issue described, as it pertains to emulators. I don't think the other samples you saw are the same issue. I've added extended logging in the exception message for the WrongAbiError exceptions, hope that gives more clues.
from soloader.
mars-lan
commented on May 7, 2024
@BurntBrunch is dynamic code translation limited to only emulators?
from soloader.
BurntBrunch
commented on May 7, 2024
As far as I know, yes. x86 devices are very rare in the wild (they have libhoudini which does similar things on them) and all the devices you mentioned are definitely ARM.
from soloader.
mars-lan
commented on May 7, 2024
Got it. Let's see if the extra logging can reveal some other bugs then. Look forward to the new release soon.
from soloader.
xserxses
commented on May 7, 2024
@BurntBrunch any updates on this?
from soloader.
vajid-khan
commented on May 7, 2024
I am facing similar issue when I set enableSeparateBuildPerCPUArchitecture = true & enableProguardInReleaseBuilds = true in build.grade file.
with above setting set to false, release apk works fine but I need to set it to true to decrease bundle size
I am testing it on a real device, Oneplus 7 running android 10
react: "16.11.0",
react-native: "0.62.0"
ADB logcat
SoLoader: couldn't find DSO to load: libfbjni.so caused by: com.facebook.jni.NativeRunnable
05-05 10:09:05.304 4646 4677 E AndroidRuntime: FATAL EXCEPTION: create_react_context
05-05 10:09:05.304 4646 4677 E AndroidRuntime: Process: com.my_app, PID: 4646
05-05 10:09:05.304 4646 4677 E AndroidRuntime: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libfbjni.so caused by: com.facebook.jni.NativeRunnable
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.SoLoader.a(Unknown Source:325)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.SoLoader.a(Unknown Source:104)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.SoLoader.a(Unknown Source:108)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.SoLoader.a(Unknown Source:1)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.j.a(Unknown Source:0)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.soloader.o.a.a(Unknown Source:10)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.jni.HybridData.(Unknown Source:2)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.react.bridge.WritableNativeMap.initHybrid(Native Method)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.react.bridge.WritableNativeMap.(Unknown Source:0)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.react.jscexecutor.a.create(Unknown Source:2)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at com.facebook.react.q$e.run(Unknown Source:58)
05-05 10:09:05.304 4646 4677 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
from soloader.
yeshmesh
commented on May 7, 2024
@BurntBrunch Thnx a lot dude, i had an API version 28 then i downloaded 29. It worked. Was spending 2 days figuring this out. Thank you again!
from soloader.
mars-lan
commented on May 7, 2024
Still seeing similar issue with SoLoader 0.8.2 with the following (not very helpful) error message. @BurntBrunch any update?
Fatal Exception: java.lang.UnsatisfiedLinkError couldn't find DSO to load: libv8executor.so result: 0 com.facebook.soloader.SoLoader.doLoadLibraryBySoName
@BurntBrunch looks like the error code 0 corresponds to LOAD_RESULT_NOT_FOUND (https://github.com/facebook/SoLoader/blob/master/java/com/facebook/soloader/SoSource.java#L28). Are you able to shed some light here?
from soloader.
abhishekdewan101
commented on May 7, 2024
Not sure if this will work with all the apps out there but in the case of my app I figured that the /data/app// dir has all the so's already present ready to be used and all our SoLoader.init was doing was backing them up to lib-main ( for some reason the copying corrupts the files or makes them unusable) so the solution was in to initialize SoLoader in the mode where it doesn't back up the so's to the lib-main folder by providing SoLoader.init(context, SOLOADER_DISABLE_BACKUP_SOSOURCE) in application onCreate() (or where ever is more suitable). This way we never get a libs-main folder in your application directory and since SoLoader already has an idea of looking into /data/app// dir it works from them :) Again not sure if this is the right way to handle this but is a workaround :(
from soloader.
greg7gkb
commented on May 7, 2024
SOLOADER_DISABLE_BACKUP_SOSOURCE change did not resolve this for my case (RN 61.5, target API 29)
from soloader.
mars-lan
commented on May 7, 2024
Rolling 0.9.0 to production and haven't seen any crash so far. Hoping this is fixed by 3311e1a.
from soloader.
slavikdenis
commented on May 7, 2024
Hope more data helps.
Setup:
"react-native": "0.63.2"implementation 'com.facebook.soloader:soloader:0.9.0+'enableHermes: false
Distribution: Android App Bundle (AAB)
Device: Nexus 5X (Android 6.0.1)
Log:
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.metropolis/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/com.metropolis-1/lib/arm flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/com.metropolis-1/lib/arm
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:1017)
at java.lang.Thread.run(Thread.java:818)
I'm gonna try this workaround for the next production build #59 (comment)
from soloader.
NetPumi2
commented on May 7, 2024
go to the android directory and run dis command "./gradle clean" its work for me
@soroushm Thanks. Is it
./gradlew clean? ---> This command fixed the issue on my side...
I do this command before every release and I still have this issue on production
from soloader.
RodolfoGS
commented on May 7, 2024
@charleston10 Interesting, Thank you so much for your tips! And Do you know what could we do to fix this issue?
from soloader.
Prernabudh
commented on May 7, 2024
@saczuac
does this fix it for you? It did for me:configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.8.2" } }
With which version of React native did this work for you?
from soloader.
LFMAKER
commented on May 7, 2024
How to reproduce this issue in emulator?
from soloader.
roots-ai
commented on May 7, 2024
I'm a native android programmer, and this problem happens when compiling the app through Play from the android studio itself
Behind it, it generates an apk with ABI with simpler architecture for the OS
If you generate the APK via Build or via ADB, the APK architecture will be generated using the architecture defined by build.gradle or the standard architecture
In this case I want to make it clear, that there is a difference between creating apk via Play and via Build / ADB
@charleston10 Can you please elaborate on what settings to keep in app/build.gradle to make this work?
Happening in RN 0.65 as well, without Android Studio. facebook/react-native#32245
from soloader.
RodolfoGS
commented on May 7, 2024
@agrass I'm not sure, but maybe it will be fixed in this PR facebook/react-native#30749 recently merged 🤞
from soloader.
agrass
commented on May 7, 2024
Thanks @RodolfoGS! you already tried that?? That error with libhermes.so it suppose be solved same way the libv8executor.so? because that fix it seems to apply only for libhermes.
from soloader.
simpleton
commented on May 7, 2024
Version 0.10.3 has been released which includes several fixes.
from soloader.
simpleton
commented on May 7, 2024
Can you share the crash backtrace or log?
…On Tue, Dec 7, 2021 at 12:26 PM Mubarak ***@***.***> wrote:
We have upgraded soloader to 0.10.3 but somehow Crashlytics is still
reporting this issue...
Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so SoSource 0: c.g.b1.d[root = /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 flags = 0] SoSource 1: c.g.b1.c[root = null] SoSource 2: c.g.b1.d[root = /vendor/lib flags = 2] SoSource 3: c.g.b1.d[root = /system/lib flags = 2] Native lib dir: /data/app/com.xxx-vcqrW3oazAf0i2rlQsiIbA==/lib/x86 result: 0
This time the report says the device is running Android 8.1.0 (Nexus 5X)
at *SoLoader.java line 1098*.
me too having same issue with version 0.10.3 and Android 11
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#55 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADO6YVDAFPRD66VVFCELCDUPZUYBANCNFSM4J2NKS4A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
from soloader.
simpleton
commented on May 7, 2024
do you have a reproduction of this crash? if you had, can you check whether the libhermes in the /data/app/com.xxx-QOZMQQzcNNsbGdCAr64Kcw==/lib/arm64?
you're using v0.10.3, right?
from soloader.
raldred
commented on May 7, 2024
We're seeing crashes for customers using Nexus 5X.
RN: 0.64.2
SoLoader: 0.10.1
enableHermes: false
jscFlavor: 'org.webkit:android-jsc:+'
do we need to pin soloader to 0.10.3?
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.residently.app/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/com.residently.app-wGEqSbt7uvrlwjEyhnlnQQ==/lib/x86 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/com.residently.app-wGEqSbt7uvrlwjEyhnlnQQ==/lib/x86
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:764)
from soloader.
msgharpu
commented on May 7, 2024
0.10.3 should fix this issue
…
On Tue, Jan 11, 2022 at 9:34 PM Mayuresh Gharpure @.> wrote: We are also seeing similar crashes in Android 10 and 11 devices with RN version = 0.64 and Soloader = 0.8.2. Is there any update on this bug? or anyone knows of a workaround? — Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADO6YQQENUZAPEEYVS3IITUVUHFFANCNFSM4J2NKS4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.>
Thanks @simpleton. Will try this. Could you please point to the PR or commit which fixes this?
We don't have a way to repro this bug, hence wanted to look at the change to understand the fix a little more
from soloader.
simpleton
commented on May 7, 2024
@sn123 do you mind the share the apk that rejected in reviews?
from soloader.
sn123
commented on May 7, 2024
It’s an aab and not the apk. I don't think sharing it would be an issue - let me know if aab is fine.
I did unzip aab and had these folders inside lib: x86, x86_64, arm64-v8a and armeabi-v7a. If you look at crash log, soloader seems to be looking under lib/arm folder which doesn’t exist. In case it matters, Crash log is from crashlytics.
…________________________________
From: Sim Sun ***@***.***>
Sent: Friday, January 28, 2022 9:25:47 PM
To: facebook/SoLoader ***@***.***>
Cc: Sachin Nigam ***@***.***>; Mention ***@***.***>
Subject: Re: [facebook/SoLoader] SoLoader 0.8.0 couldn't find DSO to load - issue on .apk build (#55)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@sn123<https://github.com/sn123> do you mind the share the apk that rejected in reviews?
—
Reply to this email directly, view it on GitHub<#55 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADE6NHMQH6BGEOWGPGVHRK3UYK4AHANCNFSM4J2NKS4A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
from soloader.
sn123
commented on May 7, 2024
@simpleton - here's the link for aab. https://goavega-my.sharepoint.com/:u:/p/snigam/EZjlcSYiklxBooSHmBr7YWcBbBzUuOTEaoCEOiXoSqucHw?e=aAaprM Let me know if you specifically need apk.
from soloader.
sn123
commented on May 7, 2024
@simpleton - here's the link for aab. https://goavega-my.sharepoint.com/:u:/p/snigam/EZjlcSYiklxBooSHmBr7YWcBbBzUuOTEaoCEOiXoSqucHw?e=aAaprM Let me know if you specifically need apk.
For whatever it's worth - I upgraded react native to 0.67 and was able to get through the review process. I did make quite a few sweeping changes as well so not sure if the issue was just with React Native versions or somewhere else, for e.g. I removed all expo packages and replaced them with regular react native packages. Anyway, hopefully I can sleep peacefully now. I'll leave the aab file out there for anyone who wants to debug it.
from soloader.
abhilakshyadobhal
commented on May 7, 2024
As mentioned I tried to do this it worked but if in my app's code I'm keeping the condition for checking whether my device is rooted or not it is detecting the device as rooted device.
What fixed it for us what upgrading the SOLoader.
In android/app/build.gradle:
dependencies { implementation 'com.facebook.soloader:soloader:0.9.0+'
from soloader.
sarmad6146324
commented on May 7, 2024
App woking fine in debug but while build release it crashes immediately
react-native-cli: 2.0.1
react-native: 0.67.4
Error
E/HwDetectorWithState: a: 3 E/AndroidRuntime: FATAL EXCEPTION: main Process: com.rnespclient, PID: 21704 java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.rnespclient/lib-main flags = 1] SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~w2nIgrLTQGqeN-xT7qolwQ==/com.rnespclient-txIJ5efndrtcV97wOdorlA==/lib/arm64 flags = 0] SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2] SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2] Native lib dir: /data/app/~~w2nIgrLTQGqeN-xT7qolwQ==/com.rnespclient-txIJ5efndrtcV97wOdorlA==/lib/arm64 result: 0 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743) at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(JSCExecutor.java:24) at com.facebook.react.jscexecutor.JSCExecutor.<clinit>(JSCExecutor.java:20) at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(Unknown Source:0) at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:352) at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:319) at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:95) at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:42) at com.rnespclient.MainApplication.onCreate(MainApplication.java:55) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1242) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7220) at android.app.ActivityThread.access$1600(ActivityThread.java:265) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2169) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:257) at android.app.ActivityThread.main(ActivityThread.java:8220) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
from soloader.
jadonhansen
commented on May 7, 2024
I have tested on multiple versions and the issue only starts occuring at android 8.1 and below.
How has this issue been open for so long?
I have tried multiple variations of:
dependencies { implementation 'com.facebook.soloader:soloader:0.9.0+'
and
configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.9.0" }
with different soloader versions and in the different build.gradle files with no luck.
Very frustrating that we can't support lower end users.
from soloader.
simpleton
commented on May 7, 2024
Are you using Hermes in your app? Does it happen all the time?
…On Tue, Apr 26, 2022 at 1:34 PM Jadon Hansen ***@***.***> wrote:
I have tested on multiple versions and the issue only starts occuring at
android 8.1 and below.
How has this issue been open for so long?
[image: Screenshot 2022-04-26 at 20 01 14]
<https://user-images.githubusercontent.com/35688233/165387113-e332ab86-a726-42aa-97ea-d468fbc26852.png>
I have tried multiple variations of:
dependencies { implementation 'com.facebook.soloader:soloader:0.9.0+'
and
configurations.all { resolutionStrategy { force
"com.facebook.soloader:soloader:0.9.0" }
with different soloader versions and in the different build.gradle files
with no luck.
Very frustrating that we can't support lower end users.
—
Reply to this email directly, view it on GitHub
<#55 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADO6YRUANFM7DOOY57CSDTVHBHOLANCNFSM4J2NKS4A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from soloader.
simpleton
commented on May 7, 2024
@jadonhansen it's better to use the latest version.
from soloader.
nagasai65
commented on May 7, 2024
Changed the version to
0.10.1solve the issue at my end. implementation 'com.facebook.soloader:soloader:0.10.1+'
It works for me, Thank you @tusharsarkar
from soloader.
DevVibhor
commented on May 7, 2024
Facing the same issue in RN 0.63.2
I have tried with all different versions of soloader mentioned above but still no luck. In my case, it is crashing for Android 10 devices in debug and release mode.
This issue first came to me right after switching to Mac M1 from Intel Mac.
from soloader.
swaroopaillinda
commented on May 7, 2024
Hi facing same issue did anyone find solution for this
from soloader.
DevVibhor
commented on May 7, 2024
I've solved this issue by doing this,
https://stackoverflow.com/a/74486848/20503822
from soloader.
98rahul
commented on May 7, 2024
couldn't find DSO to load: libhermes.so caused by: dlopen failed: library "libjsi.so" not found:
not solved by changing the above different soloader version mention .
Have anyone able to resolve this error.
from soloader.
unicornRainbows
commented on May 7, 2024
I also have the same issue..
from soloader.
98rahul
commented on May 7, 2024
I also have the same issue..
better to move with latest version RN-0.71.1
and chill 🎉🎉
from soloader.
unicornRainbows
commented on May 7, 2024
I also have the same issue..
better to move with latest version RN-0.71.1 and chill 🎉🎉
I wish I could, but react-native-vision-camera doesn't support it yet..
from soloader.
miteshdb
commented on May 7, 2024
Having same problem.
React Native : 0.64.4
implementation 'com.facebook.soloader:soloader:0.9.0+'
from soloader.
malikzype
commented on May 7, 2024
Facing the same issue... none of the solutions worked.
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.a[root = /data/data/...../lib-main flags = 1]
SoSource 1: com.facebook.soloader.d[root = /data/app/~~MPKzZHrXvYC8_UVhanEkkg==/......-3O2d9zcsgjcplUI6W_P4_A==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.d[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.d[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/~~MPKzZHrXvYC8_UVhanEkkg==/....-3O2d9zcsgjcplUI6W_P4_A==/lib/arm64
from soloader.
RubenPM-dev
commented on May 7, 2024
better to move with latest version RN-0.71.1 and chill 🎉🎉
I'm having the same issue on 71.7 on Android 9 to 12
from soloader.
shailesh-galgal
commented on May 7, 2024
Anyone’s got any solution?
from soloader.
RodolfoGS
commented on May 7, 2024
Issue continues with the latest soloader version (com.facebook.soloader:soloader: 0.10.5)
Devices impacted are 100% Google Nexus 5X
And all devices dispatch 2 crashes, one with libhermes.so and the other one with libreactnativejni.so
react-native: 0.72.4
I uncompressed the APK and both files exists in lib/x86/:
lib/x86/libhermes.so<-- existslib/x86/libreactnativejni.so<-- exists
couldn't find DSO to load: libhermes.so
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/__hidden__/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/__hidden__-Puw4sCzSdJ_xR3BEfMgpxA==/lib/x86 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/__hidden__-Puw4sCzSdJ_xR3BEfMgpxA==/lib/x86
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 host.exp.exponent.MainApplication.onCreate(MainApplication.java:113)
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)
couldn't find DSO to load: libreactnativejni.so
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/__hidden__/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/__hidden__-Puw4sCzSdJ_xR3BEfMgpxA==/lib/x86 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
Native lib dir: /data/app/__hidden__-Puw4sCzSdJ_xR3BEfMgpxA==/lib/x86
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.react.bridge.ReactBridge.staticInit(ReactBridge.java:34)
at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:17)
at com.facebook.react.bridge.Arguments.createMap(Arguments.java:159)
at expo.modules.updates.statemachine.UpdatesStateContext.getWritableMap(UpdatesStateContext.kt:53)
at expo.modules.updates.UpdatesController.sendUpdateStateChangeEventToBridge(UpdatesController.kt:561)
at expo.modules.updates.statemachine.UpdatesStateMachine.sendChangeEventToJS(UpdatesStateMachine.kt:65)
at expo.modules.updates.statemachine.UpdatesStateMachine.processEvent(UpdatesStateMachine.kt:47)
at expo.modules.updates.UpdatesController$start$1.onRemoteCheckForUpdateStarted(UpdatesController.kt:285)
at expo.modules.updates.loader.LoaderTask.launchRemoteUpdateInBackground$lambda$1(LoaderTask.kt:338)
at expo.modules.updates.loader.LoaderTask.$r8$lambda$jwzCL9xjo0jbCNnExNO-hPCX6iI()
at expo.modules.updates.loader.LoaderTask$$ExternalSyntheticLambda1.run(:6)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
from soloader.
Related Issues (20)
- Wrongly loaded directApkLdPath HOT 2
- "java.lang.UnsatisfiedLinkError: couldn't find DSO to load" on 64-bit only environment HOT 9
- API sigh ault
- SoLoader: libjscexecutor.so not found on /data/app/ HOT 4
- UnsatisfiedLinkError: couldn't find DSO to load: libgifimage.so caused by: dlopen failed HOT 1
- YogaLayout does not recalculate its dimension for any runtime change in children dimension HOT 1
- Lo
- couldn't find DSO to load: libhermes-executor-debug.so HOT 3
- SoLoader version with errors The app uses a buggy version of the SoLoader SDK, which can cause crashes. Update to a valid version of SoLoader. HOT 3
- Please add troubleshooting docs for "couldn't find DSO to load" errors
- [test_only] test task creation
- Insecure hashing algorithm MD5 used
- Your app uses a defective version of the SoLoader SDK, which can cause your app to crash. Update to a fixed version of SoLoader.
- MainApplication.onCreate java.io.IOException - could not delete: /data/user/0/PACKAGE_NAME/lib-0/libfolly_futures.so HOT 1
- Pixel 8 Issue - UnsatisfiedLinkError HOT 8
- dso_lock: open failed: EACCES (Permission denied) HOT 2
- Next version release HOT 2
- UnsatisfiedLinkError dlopen failed: library "libhermes.so" not found HOT 2
- java.lang.UnsatisfiedLinkError dlopen failed: library "libhermes.so" not found
- android.os.strictmode.DiskReadViolation crash on app start
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from soloader.