-
Notifications
You must be signed in to change notification settings - Fork 69
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: libv8executor.so #33
Comments
@mars-lan Could you help to unzip your apk and double check if libv8executor.so existed or not? I also published [email protected] yesterday. Please use the version paired with RN 0.61.5 to reduce risk. |
Seems like libv8executor.so exists for all architectures
It still crashes consistently on an x86_64 emulator after updating to [email protected] with the following stacktrace, which seems to suggest a problem loading
|
@mars-lan From the log, it is getting a little wield to me. Did you ever try reinstall your app or cleanup app data which to remove files from Otherwise, please try to unzip your apk the use $ mkdir /tmp/foo && cd /tmp/foo && unzip /path/to/XXX.apk
$ file lib/x86_64/libc++_shared.so
lib/x86_64/libc++_shared.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=7779489e2e0b2b093fd3386d87c28afdbf6ca63a, stripped
$ file lib/x86_64/libfb.so
lib/x86_64/libfb.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5b9bfbac6a6dbf6fa3b245012d913296d5064443, stripped |
Looks like this is most likely a bug in |
same issue as below.
|
Similar to #29 but with a different stacktrace.
Using
react-native
0.61.5
react-native-v8
0.61.4-patch.1
v8-android-intl
7.8.1
The text was updated successfully, but these errors were encountered: