-
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
Android signed release build cannot find DSO to load - Unsatisfied Link Error #23902
Comments
It looks like you are using an older version of React Native. Please update to the latest release, v0.59 and verify if the issue still exists. The "Resolution: Old Version" label will be removed automatically once you edit your original post with the results of running |
Hello there 👋 this issue has been reported for an old version of React Native. Ideally we'd like everyone to be using 0.59 (see the awesome changes it brought) but we know updating can be a pain. We are going to close this issue because it's from a version before 0.57, which is really old. But please, if it's actually still an issue with 0.59 please comment below and we can reopen it. Even better, please send us a pull request with a fix 😊 |
Fixed in 0.59 thanks! |
Still having the bug with RN 0.59.8. My package.json file is
Exception:
|
I am also facing this issue on React Native 0.59.8.
is there any fix/workaround? |
Hi, Even we are facing the same issue. It works fine with Standalone Apks (generated from bundle). But starts crashing with multi-apk install. Kindly help to resolve this. Tried with RN Version 0.53.3, 0.58.6 and 0.59.0.
|
Still getting same error on android signed apk, debug apk works normally. Using react-native 0.60.4
Stack Trace:
Does anyone have any idea? |
If you use realm, update it to the latest version, which is 64bit compatible |
Did u get any fix ? |
@shaktimoyal Did you find the solution? |
Working on it . Not able to find yet. |
@shukerullah @shaktimoyal |
I am not using realm. Simply using react native 0.59.0 version and crash report at Firebase test lab says following : java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.aasaanjobs.employee.aasaanjobsemployee/lib-4/libc++_shared.so" is 32-bit instead of 64-bit |
have u included 64 bit architecture in your gradle configurations? |
Yes, i have added. apply plugin: "com.android.application" import com.android.build.OutputFile /**
project.ext.react = [ apply from: "../../node_modules/react-native/react.gradle" /**
/**
android {
signingConfigs {
} dependencies {
// Run this once to be able to run the application with BUCK apply plugin: "com.google.gms.google-services" // this code has been added due to an build error occured because of codepush and google play services 4.2.0 version |
TLDR I was trying to create separate build per CPU Architecture and
After release build I can see now all the missing |
Bug Description
When running a signed release build on a physical device (Google Pixel 2) the application fails to open and crashes immediately with the error message below. Debug build runs without error.
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealmreact.so caused by: Error: Cannot load /data/app/com.singletrack-oLMiw4nVqqKxhbcbq5quCg==/lib/arm/librealmreact.so
From the error message it is looking for the librealmreact.so binary in /lib/arm/ but when I analyse the APK the librealmreact.so is located in /lib/armeabi-v7a/ but I do not know why it is searching on the wrong path.
Gradle config
apply plugin: "com.android.application"
import com.android.build.OutputFile
project.ext.react = [
entryFile: "index.js",
inputExcludes: ["ios/", "Tests/", "bundle_out/", "default.realm", "default.realm.lock", "default.realm.management/"],
nodeExecutableAndArgs: hasProperty("NODE_PATH")?[NODE_PATH]:["node"]
]
apply from: "../../node_modules/react-native/react.gradle"
apply from: "../../node_modules/react-native-sentry/sentry.gradle"
def enableSeparateBuildPerCPUArchitecture = false
def enableProguardInReleaseBuilds = false
android {
compileSdkVersion rootProject.ext.compileSdkVersion
}
dependencies {
implementation project(':realm')
implementation project(':react-native-sentry')
implementation project(':react-native-push-notification')ns')
implementation project(':react-native-svg')
implementation fileTree(include: ['*.jar'], dir: 'libs')
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
implementation 'com.facebook.react:react-native:+'
// From node_modules
}
// 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) {
from configurations.compile
into 'libs'
}
Expected Behavior
Application should open and run without error
Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
Memory: 679.33 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.15.0 - /usr/local/opt/node@8/bin/node
npm: 6.4.1 - /usr/local/opt/node@8/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 23, 26, 27, 28
Build Tools: 23.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3
System Images: android-26 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5264788
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: ^0.57.1 => 0.57.8
npmGlobalPackages:
create-react-native-app: 2.0.2
The text was updated successfully, but these errors were encountered: