jpush / jpush/jpush-react-native
Android couldn't find DSO to load: libreactnativejni.so
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
你的运行环境
- 插件版本:
- react-native 版本：0.59
期望效果
启动不应该闪退
实际效果
下载了app之后，打开app 还没有初始化极光,就闪退了
重现步骤
- 混合打包安卓 armeabi-v7a arm64-v8a
- 在OPPO R9M (android 5.1)上 启动就闪退
- ...
4.但是如果我只打包一个armeabi-v7a 是没有问题的
Debug logs
Android ：
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.xxxx.xxxxx/lib-main/libc++_shared.so" is 64-bit instead of 32-bit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction details in issue #884 and compare the mixed armeabi-v7a/arm64-v8a packaging setup against the Android build configuration. Check common_problems.md first, then investigate the reported libc++_shared.so and libreactnativejni.so loading errors on the OPPO R9M. Done means the app launches on the mixed-ABI build without this crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100