[0.67] Android release crash: couldn't find DSO to load: libjscexecutor.so #32928
Comments
|
There has been another report of this happening: #32927 I've investigated locally and I can confirm that if you generate a fresh project like so We'll look closer into that. The good news is that I've also noticed that by turning on Hermes the issue disappears (which is probably why we didn't catch it 😢) and the app builds successfully also in production mode:
So for now I recommend you turn on Hermes on Android to address this - bear in mind that Hermes is planned to become the default engine for React Native. cc @cortinico & @LZHD |
kelset
changed the title
kelset
added
Impact: Crash
Impact: Regression
Yup that's definitely a regression, and we probably want to call a point release for this hotfix (which is forthcoming). |
Summary: As the title says, we dont' want to remove `libjscexecutor.so` when baking release builds and having JSC enable as this leads to instacrashes. Fixes facebook#32928 Fixes facebook#32927 Changelog: [Android] [Fixed] - Do not remove libjscexecutor.so from release builds Differential Revision: D33681932 fbshipit-source-id: 4a71fd6cfaae35a1f24f048648e32d78d573a457
kelset
added
Resolution: PR Submitted
Thanks for the issue report @coolguy001tv. I was actually wrong as both Sadly this slipped through the release testing process as we mostly focus our testing on Hermes rather than JSC. Also as a workaround while we work on a point release, you can still use this in your project.ext.react = [
enableHermes: false,
+ deleteDebugFilesForVariant: { false }
] |
|
It works fine, thank you very much |
Summary: Pull Request resolved: #32932 As the title says, we dont' want to remove `libjscexecutor.so` when baking release builds and having JSC enable as this leads to instacrashes. Fixes #32928 Fixes #32927 Changelog: [Android] [Fixed] - Do not remove libjscexecutor.so from release builds Reviewed By: ShikaSD Differential Revision: D33681932 fbshipit-source-id: 5b59fd1fb76c80c191198d65c916bbbd9232c75b
|
Thanks for so quick replies. |
kelset
added
Resolution: Fixed
|
Im getting this error even when I enable hermes |
|
|
|
So, I'm getting this error too. =/
|
|
Firebase Crashlytics just reported this error to me, this is happening in production, seems already 2 users experienced this: Here's the stack trace Device: Operating system Crash |
|
@nriccar I get it on react-native 0.69 with hermes activated on release build. Debug build works fine. This should be re-opened. |
|
the issue has not been resolved yet, please reopen the ticket |
Same for me, please reopen this issue |
Hello, if you are experiencing this issue in react-native 0.69+ Hope it helps! |
|
Did you guy solve the issue on RN 0.68.2. I'm facing the same issue when trying to use Dexguard(with either Hermes enable or not). Any helps please? Really appreciate that. Thanks |
|
The issue still persists |
|
Still getting the issue for 0.67.1, it happens only when I update my app with an in-app update, and after a successful update app crash with the below error, later if I open the app it's working fine SoLoader: couldn't find DSO to load: libhermes-executor-debug.so E/SoLoader: couldn't find DSO to load: libjscexecutor.so Hermes is enabled |
|
I think this should be re-opened |
|
I am getting this issue on crashlytics on upgrading to 0.68.1, in desperate need of a solution. |
|
E/SoLoader: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found: needed by /data/app/~~MAQLtBH_YH1akJlLHwB6BA==/com.xx.xx.staging1-5oLdcBbfLWDCumShj7vLSw==/lib/arm64/libjscexecutor.so in namespace classloader-namespace result: 0 getting same error on develop mode with flavours enabled. herms enabled. |
|
same issue +1 |
|
facing same issue, with react native version .66 and hermes enabled |
|
Any updates here? Sad to see the state of production level |
|
Same here: |
|
Okay ! Here is my fix for this I was facing this issue, I managed to fix this
clean gradle and re run the entire app this issue will be gone. but for |
|
Seeing this issue right now with RN |
|
Seeing this as well upgrading from |
|
Any solution here? I upgraded from 0.67.2 to 0.70.4. |
|
same here. RN 0.70.4 with hermes. If I add the following to my the app doesn't crash, but the error is still there. |
|
Solution that worked for me, |
|
for those who're still struggling with this issue while Hermes is on, just refer to just refer to the following comment #33177 (comment). You most likely have the custom variation that isn't picked up by hermes, so you have to provide proper settings for |
|
This worked for me: change and also put |
this finally worked for me :) |
and others
Description
In android release, it will crash.
The android log shows that libjscexecutor.so is not found.
the detailed log :
Version
0.67.0
Output of
npx react-native infoSteps to reproduce
just use the lastest rn version:
npx react-native init rn67 --version 0.67.0then into the android directory, run:
gradlew assembleReleasethen grab the app-release.apk and install it via adb.
Then it crashed with the log above.
I find this error still exist in 0.67.0RC version( tested in rc6, which will crash), but in 0.66.4, there is no crash.
Further deep in, I find it may be related to this: 6f12674
U may see the conversation below this commit: if i comment the 3 lines, i find the android release won't crash, but as @cortinico said, libjscexecutor.so shouldn't be in release.
So what's the best for me to do?
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: