-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found #25537
Comments
@nicsachin For me, it's still not working. Did you tried running the sample project I've shared? |
hi @mhrpatel12 , I'm having same issue. You can follow this link. Add following code in build.gradle
in dependency add in following
|
Still no working,,, |
View the upgrade guide You're likely missing the step android/build.gradle
|
I'm not migrating from .59 to .60. This issue happens even on a brand new android project which uses AndroidX. |
Duplicate of #25415 |
@mhrpatel12 check out your file though. You're missing pieces |
@BrendonSled Were you able to run the app successfully after making those changes? |
@mhrpatel12 Have you made sure |
@chrisspankroy yes, I have made sure that |
Could you give it a try? I tried using your sample project. After done following changes, it works at my side Add
|
@crispywong thank you, it's working now. |
For me worked that fix with
in build.gradle |
it is work for me, thanks |
|
Did you add below in
|
|
@Villar74 thanks its work for me. |
if you have this error it means that you have a jsc aar missing, you can find it in node_modules\jsc-android\dist Make sure it is included in your dependencies |
I think if peoples sure that config for android correct. So, check your android/app/build.gradle If have two lines after:
Replace your
|
How? |
check your android/app/build.gradle
|
@zhuweideng Thanks |
|
Having the same issue with the same specs |
me too |
why are they not answering, i am facing this issue too |
I don't understand what you mean please. |
how to fix this stupid issue wtf ? |
Same issue, successful build locally. Crash on boot looking for libjscexecutor.so and expo-modules-core lib .so files. The expo-modules-core stuff might be related to not being able to make use of the CMake scripts when building. Possibly related to the missing libjsexecutor.so stuff too though. Feels like the gradle build is missing something. P.S. There has been stuff added to the project build.gradle and app/build.gradle to pull in two third-party libs but otherwise the gradle is what's output by npx expo prebuild --clean. We also had to comment out the externalNativeBuild CMakeLists.txt block in the expo-modules-core build.gradle as it was killing builds, what's throwing the CMake build process off is unclear. Proven very hard to track down but it seems to have no reference to ReactAndroid despite the CMake directory args being set what seems to be correctly. I'm surprised libjscexecutor.so is attempted to be loaded given hermes is the engine used. I've debugged both the debug and release gradle builds, that hermesEnabled flag in gradle.properties is definitely set to true and picked up in the app/build.gradle.
Project build.gradle:
Project app/build.gradle:
Project gradle.properties:
|
my issue is with libturbomodulejsijni.so RN : 63.4 |
Facing this issue in React Native 0.69
|
Downgrading to Expo v49.0.0 with React Native v0.72.6 fixed this issue for us. |
@rossparachute I am not using expo. :( |
Ah sorry, @aadityapaliwal94 - seems there's a few causes for this! Upgrading React Native to 72 might be worth trying. Hope you can find a solution soon. :) |
Upgrading to upper version fixed for me |
Thanks @rossparachute and @Linuhusainnk Updating react native version at this point is too much work for me. But I am able to run it once updated on v0.69.7 Used this as ref - #35210 |
Dear Team, I have been encountering the same issue over the past few days. Despite my efforts to implement various solutions, I have been unsuccessful in replicating the problem. I have thoroughly reviewed and attempted all possible solutions, but the issue persists. To provide more context, could you please specify the nature of the problem you're experiencing, any error messages received, or any unexpected behavior encountered? Additionally, if there are specific details about the code or environment that could be relevant, please share them. Your detailed information will greatly assist in diagnosing and resolving the issue. |
same issue here |
same issue here, react native version 0.72.6, expo: 49.0.15. This happened when I integrate with existing app. If I build the expo app from start then no problem |
It's somehow related to Proguard because today i got the issue when enabled it. |
I'm still having the same issue with RN 0.72.6 and expo 49.0 |
Has anyone found a fix to it ? facing the same issue when the app is installed, it immediately crashes with the same error. I'm working on RN 0.72.6 and expo 49.0. Please tell how can i resolve this issue ? |
same issue, also RN 0.72.6 and expo 49.0 EDIT: My error was related to another error crashing the app as a function was called before it was initialized. Hard to debug but fixed this at least. |
Here too RN v0.72.4 and Expo 49.0.8 |
same issue, also RN 0.72.6 and expo 49.0 |
I had the same issue. For me I was having the following snippet I removed Then the issue git fixed. |
why is this closed? error is still there |
Dont use expo to build android apps , its much easier to debug and fix the errors , expo is good only with ios |
I am use EAS with expo ejected using prebuild which allows me to modify platform native code but nothing suggested here or on other places so far has worked. |
You are probably missing some dependencies |
I am also facing this issue on React Native v0.66.3 when I update the Gradle plugin after updating compileSdkVersion to 34.
However, variant=debug works fine. |
this also happens to me, trying to update compileSdkVersion to 34 on react-native 0.66.5 |
App crash on Android integration with existing apps.
Crash log.
React Native version:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 1.19 GB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.5.0 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 21, 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 23.0.1, 25.0.2, 26.0.2, 27.0.3, 28.0.0, 28.0.3, 29.0.0, 29.0.0
System Images: android-22 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: ^0.60.0 => 0.60.0
npmGlobalPackages:
react-native-cli: 2.0.1
Steps To Reproduce
implementation 'com.facebook.react:react-native:+'
Sample project on GitHub which reproduces crash.
The text was updated successfully, but these errors were encountered: