-
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
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so caused by: dlopen failed: cannot locate symbol "__emutls_get_address" referenced by "/lib/arm64/libfolly_runtime.so" #37890
Comments
Can we create a reproducer of some sort? Once we have a reproducer I can look into fixing this one. |
|
@cortinico Thanks for getting back. I will try to get back to you with a reproducible example. The only difference I see between our project and vanilla RN 0.71.8 is some extra third-party libraries. |
@cortinico Here is a reproducible example: https://github.com/satheeshwaran/RNSeventOneEight |
That link returns 404 for me |
@cortinico Sorry please check now, I made it public. |
The problem was with react-native-scanbot-sdk and even though I removed a custom The SDK vendor also fixed this issue recently. https://docs.scanbot.io/document-scanner-sdk/react-native/changelog/#version-4150-14-jun-2023
I hope this helps someone. |
Ah great, thanks for the clarification |
Hey @satheeshwaran I am also getting exactly same crash when I am trying to upgrade react native from 0.69.1 to 0.72.4. I also followed your path of debugging and found that I have one sdk |
没有人能解决这个问题,不知道react-native官方能否解决这个问题! |
Facing a similar issue. Tried different solution and also have posted a question on stackoverflow. |
facing the same issue. no solution yet |
Same here. With RN 0.71.7 |
facing the same issue. pls help |
Check whether you have any custom NDK libraries under the |
@cortinico I apologize for reviving this issue, but I have a similar error when integrating a third-party To simulate the problem, I have created a new project with RN dependencies {
implementation (files("libs/canoa-sdk_2.9.2_dw.aar"))
} The error:
Inspecting the I also have tried to add some packagingOptions {
pickFirst 'lib/x86_64/libopencv_java4.so'
pickFirst 'lib/x86_64/libchilkat.so'
pickFirst 'lib/x86_64/libtensorflowlite_jni.so'
pickFirst 'lib/x86_64/libc++_shared.so'
pickFirst 'lib/x86_64/libcanoanative.so'
pickFirst 'lib/x86_64/libsincrSeg.so'
pickFirst 'lib/x86/libopencv_java4.so'
pickFirst 'lib/x86/libchilkat.so'
pickFirst 'lib/x86/libtensorflowlite_jni.so'
pickFirst 'lib/x86/libc++_shared.so'
pickFirst 'lib/x86/libcanoanative.so'
pickFirst 'lib/x86/libsincrSeg.so'
pickFirst 'lib/arm64-v8a/libopencv_java4.so'
pickFirst 'lib/arm64-v8a/libchilkat.so'
pickFirst 'lib/arm64-v8a/libtensorflowlite_jni.so'
pickFirst 'lib/arm64-v8a/libc++_shared.so'
pickFirst 'lib/arm64-v8a/libcanoanative.so'
pickFirst 'lib/arm64-v8a/libsincrSeg.so'
pickFirst 'lib/armeabi-v7a/libopencv_java4.so'
pickFirst 'lib/armeabi-v7a/libchilkat.so'
pickFirst 'lib/armeabi-v7a/libtensorflowlite_jni.so'
pickFirst 'lib/armeabi-v7a/libc++_shared.so'
pickFirst 'lib/armeabi-v7a/libcanoanative.so'
pickFirst 'lib/armeabi-v7a/libsincrSeg.so'
} And: packagingOptions {
pickFirst '**/libopencv_java4.so'
pickFirst '**/libchilkat.so'
pickFirst '**/libtensorflowlite_jni.so'
pickFirst '**/libc++_shared.so'
pickFirst '**/libcanoanative.so'
pickFirst '**/libsincrSeg.so'
} Thank you in advance, I appreciate any help on this. |
Log on RN
|
I don't know if it will help the Tuya users too, but for us, the solution right now is to add the Described here #43126 |
No need to rebuild third-party
as described in Patch to fix |
i tried but still get those errors |
@datdo26 , when you got such error in some third-party module, what's the NDK version in the BTW, are you building on Linux, Windows or macOS? Please choose the right OS's |
I'm using MacOS M1 Pro, i have a custom sdk use I've tried to change NDK version from 23.1.7779620 to NDK 21.4.7075529, tried to do your script but still get that error. I cleaned all caches in android studio and node_module |
@flyskywhy I also have some pickFirst: |
There is just
in my Where is your |
I put that in android/app/build.gradle, i same 3rd-party aar using |
New Version
0.71.8
Old Version
0.68.5
Build Target(s)
Android emulator
Output of
react-native info
System:
OS: macOS 13.0
CPU: (10) x64 Apple M1 Max
Memory: 30.68 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
Watchman: 2023.06.08.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 28, 30, 31, 32, 33
Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2, 29.0.3, 30.0.0, 30.0.1, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0, 33.0.1, 34.0.0
System Images: android-31 | Google APIs ARM 64 v8a, android-31 | Google APIs Intel x86_64 Atom, android-33 | Google APIs Intel x86_64 Atom
Android NDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.10121639
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /Users/satheeshwaran/.jenv/shims/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.8 => 0.71.8
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Issue and Reproduction Steps
We are trying to upgrade our app from 0.68.5 to 0.71.8. iOS seems to work fine but on Android we are getting a crash on launch.
Crash logs:
build.gradle:
app/build.gradle:
gradle.properties
Already tried the solutions mentioned in the below issues but no resolution:
No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found.
#35210Standalone React native 0.71.8 works fine and launches successfully. The problem persists only during the upgrade.
The text was updated successfully, but these errors were encountered: