Skip to content
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

java.lang.UnsatisfiedLinkError: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:738) #25782

Closed
john1jan opened this issue Jul 23, 2019 · 33 comments
Labels
Bug Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@john1jan
Copy link

App crashes after android app bundle.

React Native version:
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 36.11 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.6.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
SDKs:
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 23.0.1, 26.0.2, 28.0.3
System Images: android-19 | Intel x86 Atom, android-19 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
react: 16.8.5 => 16.8.5
react-native: 0.59.5 => 0.59.5
npmGlobalPackages:
generator-react-native-ignite: 1.13.0
react-native-cli: 2.0.1
react-native-ignite: 1.13.0

Steps To Reproduce

  1. Not able to reproduce, app crashes are increasing

Describe what you expected to happen: No crash

Screenshot 2019-07-23 at 6 13 54 PM

@john1jan john1jan added the Bug label Jul 23, 2019
@react-native-bot
Copy link
Collaborator

It looks like you are using an older version of React Native. Please update to the latest release, v0.60 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 `react-native info` on a project using the latest release.

@react-native-bot react-native-bot added the Ran Commands One of our bots successfully processed a command. label Aug 7, 2019
@react-native-bot
Copy link
Collaborator

I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while.

If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.

@adnkh
Copy link

adnkh commented Aug 25, 2019

Still happening with 0.60.5

@john1jan
Copy link
Author

john1jan commented Aug 26, 2019

@react-native-bot

giphy

@marcorm
Copy link

marcorm commented Oct 10, 2019

Hi @john1jan we're experiencing this kind of issue too. Did you find any solution?

@aashirMIQ
Copy link

Hi @john1jan we're experiencing this kind of issue too. Did you find any solution?

I am also ran into the same issue.

@kubraturan
Copy link

Hi, I have the same problem. Did you find a solution?

@TranHuuTrung
Copy link

Has anyone found a solution to this problem yet?

@john1jan
Copy link
Author

john1jan commented Jan 8, 2020

@react-native-bot the issue is still not resolved we are getting the same crash more and more

@SMKH-PRO
Copy link

SMKH-PRO commented Feb 1, 2020

02-01 19:00:28.632  4467  4506 E AndroidRuntime: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:31)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.react.bridge.Inspector.<clinit>(Inspector.java:19)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.react.bridge.Inspector.getPages(Inspector.java:26)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.react.devsupport.InspectorPackagerConnection.getPages(InspectorPackagerConnection.java:147)
02-01 19:00:28.632  4467  4506 E AndroidRuntime:        at com.facebook.react.devsupport.InspectorPackagerConnection.handleProxyMessage(InspectorPackagerConnection.java:64)

APP CRASHES ON LAUNCH, This is what i found in catlog

@andreslargo
Copy link

Issue persist?

@taschik
Copy link

taschik commented Mar 23, 2020

unfortunately yes :(

@gvsakhil
Copy link

Issue persists still for today

@ArvindNikam76
Copy link

yes

@ghost
Copy link

ghost commented Apr 3, 2020

I upgraded my react native from 59.10 to 62.0, so I got the same issue the following answer is copied from StackOverflow that helped me.

I solved this problem by this steps

install hermesvm : npm i hermesvm
install jsc-android : npm i jsc-android
3.add this lines to app/build.gradle

project.ext.react = [
entryFile: "index.js" ,
enableHermes: false
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);

dependencies {
if (enableHermes) {
def hermesPath = "../../node_modules/hermesvm/android/";
debugImplementation files(hermesPath + "hermes-debug.aar")
releaseImplementation files(hermesPath + "hermes-release.aar")
}
else { implementation jscFlavor }
add this jsc-android block to your android/build.gradle:

allprojects {
repositories {
maven {
url("$rootDir/../node_modules/react-native/android")
}
maven {
url "$rootDir/../node_modules/jsc-android/dist"
}
google()
jcenter()
}
}

cd android && gradlew clean has also helped my developers

If you are upgrading your react-native then, it's possible that upgrade my
not be successful every time so check following link to review changes
https://react-native-community.github.io/upgrade-helper/?from=0.59.10&to=0.62.0
https://react-native-community.github.io/upgrade-helper/?from=version_from&to=version_to

Hope it helps

@john1jan
Copy link
Author

john1jan commented Apr 3, 2020

So you meant to say, after enabling hermes engine this crash got solved ?

@slonv23
Copy link

slonv23 commented Aug 20, 2020

So you meant to say, after enabling hermes engine this crash got solved ?

For me not.

@jimmyceroneii
Copy link

Just as an fyi, the following issue in React Native has many more solutions for the same problem: #23764

@seleziomar
Copy link

solution? I have same problem

@snehalm-iprogrammer
Copy link

I am facing same issue. any solution?

@seleziomar
Copy link

I chose to use the apk, I couldn't solve the bundle problem

@VittoriDavide
Copy link

I am having this error with 0.64 version using hermes and creating app bundle

@emadhajjar
Copy link

I am getting the same issue on 0.64

image

@maxpill
Copy link

maxpill commented Apr 29, 2021

Getting the same issue on 0.64.0

Screenshot 2021-04-29 at 14 33 27

@Andriiklymiuk
Copy link

Is someone found how to solve it?

@ahtokca
Copy link

ahtokca commented Jun 21, 2021

Why the issue is closed if there are so many people experience it?

@emadhajjar
Copy link

werid, still having the same issue.

@pebojote
Copy link

It is so weird that this issue is closed. I think they need to reopen it.

@trickeyd
Copy link

trickeyd commented Aug 3, 2021

I having this too - it's causing so many android crashes on prod! 😭

@vish2595
Copy link

vish2595 commented Aug 24, 2021

I have this too, it's causing so many androids crashes on prod.

@omarkhaled11
Copy link

same here, still happening with .aab builds

@roots-ai
Copy link

Any updates?

@adrielschmitz
Copy link

Same here, on 0.64.1 and react 17.0.2

@facebook facebook locked as resolved and limited conversation to collaborators Oct 6, 2021
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests