SoLoader 0.8.0 couldn't find DSO to load - issue on .apk build #55
Comments
xserxses
changed the title
xserxses
changed the title
|
Seeing a similar issue on 0.8.0 with a different stack trace. 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. Also attached a a copy of the project to help debug. |
|
Hi, sorry about the delay! 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. |
|
@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 Unfortunately the stack trace from Firebase is limited |
|
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% |
|
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. |
Summary: This logic is supposed to filter out absolutely incompatible ABIs from the list given by `Build.SUPPORTED_ABIS`. This is particularly a problem on Oppo phones where 64-bit-capable devices (as reported in SUPPORTED_ABIS) launch 32-bit processes. However, this logic also ended up reordering the list. In particular, if both `armeabi-v7a` and `x86` were in the list, it would always reorder `armeabi-v7a` first. This is incorrect on devices with houdini-like capabilities, like the Android Pie Google APIs emulator image. This diff preserves the filtering logic but removes the reordering. This addresses one incarnation of Issue #55. Reviewed By: oprisnik Differential Revision: D19506390 fbshipit-source-id: 224155605fde7853227a57ea5b21a4e23ecdd972
|
Thanks for the investigation, @BurntBrunch. Look forward to a new release that includes 20198bf |
|
@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. |
|
@BurntBrunch is dynamic code translation limited to only emulators? |
|
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. |
|
Got it. Let's see if the extra logging can reveal some other bugs then. Look forward to the new release soon. |
|
Version 0.8.1 has been released which includes this fix. |
|
Still an issue for me with version 0.8.1, only error message a little bit changed in crashlitics |
|
Happening to me as well on production on version 0.8.1 of SoLoader. |
|
@BurntBrunch any updates on this? |
|
Still seeing similar issue with SoLoader 0.8.2 with the following (not very helpful) error message. @BurntBrunch any update? |
|
Have the same issue with React Native 0.61.5 and SoLoader 0.8.0 |
|
I am facing similar issue when I set enableSeparateBuildPerCPUArchitecture = true & enableProguardInReleaseBuilds = true in build.grade file. I am testing it on a real device, Oneplus 7 running android 10 ADB logcat SoLoader: couldn't find DSO to load: libfbjni.so caused by: com.facebook.jni.NativeRunnable |
|
@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! |
@BurntBrunch looks like the error code 0 corresponds to |
|
@sn123 do you mind the share the apk that rejected in reviews? |
|
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: ***@***.***>
|
|
@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. |
|
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.
|
|
App woking fine in debug but while build release it crashes immediately react-native-cli: 2.0.1 Error |
|
I have tested on multiple versions and the issue only starts occuring at android 8.1 and below.
I have tried multiple variations of: Very frustrating that we can't support lower end users. |
|
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:
***@***.***>
|
|
@jadonhansen it's better to use the latest version. |
|
i am still facing the same problem, issue is not resolved. i am using |
|
Changed the version to |
It works for me, Thank you @tusharsarkar |
|
@tusharsarkar @nagasai65 what RN version are you guys on? |
Same This works for me |
Hi @sn123, Please let me know if you found any solution to fix this app crash issue. |
|
Facing the same issue in RN |
|
Hi facing same issue did anyone find solution for this |
|
I've solved this issue by doing this, |
|
couldn't find DSO to load: libhermes.so caused by: dlopen failed: library "libjsi.so" not found: |
|
I also have the same issue.. |
better to move with latest version RN-0.71.1 |
I wish I could, but react-native-vision-camera doesn't support it yet.. |
|
Having same problem. |
|
Facing the same issue... none of the solutions worked. Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so |
I'm having the same issue on 71.7 on Android 9 to 12 |
|
Anyone’s got any solution? |
|
Issue continues with the latest soloader version (com.facebook.soloader:soloader: 0.10.5) react-native: 0.72.4 I uncompressed the APK and both files exists in
couldn't find DSO to load: libhermes.so couldn't find DSO to load: libreactnativejni.so |
|
hi. Is there any update on a possible solution for this? I'm building an app and seeing the same issue for Android 10 users.
Screenshot from Crashlytics |
and others
MyApp is crashing while performing tests on Firebase Test lab emulators (x86).
Downgrading to 0.6.1 is fixing the problem.
The text was updated successfully, but these errors were encountered: