-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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: dlopen failed: cannot locate symbol "__emutls_get_address" referenced by "/data/app/~~Q1vjL-Sbogpgp23q4KuiUA==/com.vastmindz-2Qq1zN8YfrsoxWIi-B5xZQ==/base.apk!/lib/arm64-v8a/libfolly_runtime.so"... #44553
Comments
|
|
This is a duplicate of a lot of similar issues that you can find here: The problem is most likely a wrong version of the NDK you have in your setup. |
You need to make sure you're using the same version of the NDK used to build the |
@cortinico I have used same version of ndk but getting same issue |
Had this issue before, besides what cortinico stated above, this might be a gradle paths issue on your local setup. Can you try this: Go to Note that using global gradle can cause issues down the road so use it with care. |
No need to rebuild third-party
as described in Patch to fix |
@cortinico I need help. I'm encountering the same error and the same problem. Debugger and release mode are not working. It works normally on Android 10, and the NDK version and importing AAR packages are the same. |
Description
I had an error when integrating a third-party Android .aar to my project.
Primarily I have tried on a RN 0.70.0 project and this working fine on RN 0.70.0 then I have created a new project with RN 0.73.0 and just linked the .aar files in libs folder then App Getting Crash while running.
Steps to reproduce
React Native Version
0.73.0
Affected Platforms
Runtime - Android
Output of
npx react-native info
Stacktrace or Logs
Reproducer
#43126
Screenshots and Videos
https://github.com/facebook/react-native/assets/105035653/1296aa84-0ad2-4eeb-85e4-b12003996ce8
The text was updated successfully, but these errors were encountered: