[ANDROID] SoLoader error using App Bundle

[vanydeasy]

🐛 Bug Report

Please help!
There are some crashes happening in android using app bundle but I am not sure how to reproduce it. It happens on our app with daily crash of 200 users.

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
       at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:30)
       at com.facebook.react.bridge.NativeMap.(NativeMap.java:19)
       at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:25)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:944)
       at java.lang.Thread.run(Thread.java:764)

The errors have multiple variations that occur on various android versions.

Fatal Exception: java.lang.UnsatisfiedLinkError
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: libgnustl_shared.so caused by: dlopen failed: "/data/data/com.traveloka.android/lib-0/libgnustl_shared.so" is 64-bit instead of 32-bit

Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: Dynamic section string-table not found

Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libreactnativejni.so

To Reproduce

We have tried to reproduce it with many devices but we can only reproduce it in one condition.

1. Install the release app
2. Upgrade OS from 32bit to 64bit
3. Open the app

If we reinstall the app afterwards, it works fine.
Although, we are still unsure whether it is the only error case.

Expected Behavior

The app does not crash on any device.

Code Example

android {
    ...
    defaultConfig {
       ...
        ndk {	
            abiFilters "armeabi-v7a", "x86", "arm64-v8a"
        }
    }
}

Environment

React Native Environment Info:
    System:
      OS: macOS 10.14
      CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
      Memory: 4.93 GB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 8.10.0 - ~/.nvm/versions/node/v8.10.0/bin/node
      Yarn: 1.13.0 - /usr/local/bin/yarn
      npm: 6.8.0 - ~/.nvm/versions/node/v8.10.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        Build Tools: 23.0.1, 24.0.0, 24.0.3, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.0, 28.0.2, 28.0.3
        API Levels: 23, 24, 25, 26, 27, 28
    IDEs:
      Android Studio: 3.3 AI-182.5107.16.33.5264788
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3 
      react-native: 0.58.4 => 0.58.4 

[radeno]

Can you sync config files with RN0.58 Android template https://github.com/facebook/react-native/tree/0.58-stable/local-cli/templates/HelloWorld/android and try again?

EDIT:

And update to latest RN 0.58.6 please.

[RoJoHub]

Some Device haven't the lib of armeabi .

How to get lib?

1. rename your apk to xxxx.rar.
2. Go into xxxx/lib/,now you can see armeabi directory.
3. Get libreactnativejni.so

[vanydeasy]

@radeno I have synced all config files to 0.58 except BUCK. Although it's hard to copy it as it is since our app is brownfield. Pretty sure there is no native changes from 0.58.4 to 0.58.6.

@RoJoHub Do you mean that the libreactnativejni.so is not included on some ABIs? since I'm sure it's all there.

[RoJoHub]

Also you should create directory of armabi.
Copy files from armeabi-v7a to armabi.

For your question, please confirm what architecture your device is.
If the device is an armabi architecture, then you can solve your problem.

[radeno]

@vanydeasy i understand your concerns. You can diff files with for example VSCode (Compare file). Or if you upgraded from lower version check it with https://github.com/react-native-community/rn-diff-purge. I just want to as much as possible to have identical configs, to eliminate diffs. It sometimes really helps to find problematic issue.

But i think i have found your issue.
As you can see this commit 07d1075 in description is that SoLoader was updated to newer version for Supporting App Bundle. It is available in 0.59-RC version.
Official production ready should be released in monday/tuesday.

[vanydeasy]

@RoJoHub from this doc, i got that armabi is deprecated meanwhile the crashes happen on several other architectures as well.

@radeno yes we use https://github.com/react-native-community/rn-diff-purge as well to upgrade our app. Do you want me to list down every possible difference based on it?
And also, from what I understand, SoLoader 0.6.0 has been included on 0.58.4.

[radeno]

@vanydeasy you are right. SoLoader was backported. My mistake.
Then it is weird. Is it same results for clean RN 0.58 init?
We don't use 64bit for Android yet because some other packages are not compatible yet.

[RoJoHub]

I think we should browse this page.
https://developer.android.com/ndk/guides/abis?hl=en

Specially.

---

Automatic extraction of native code at install time

When installing an application, the package manager service scans the APK, and looks for any shared libraries of the form:

lib/<primary-abi>/lib<name>.so

If none is found, and you have defined a secondary ABI, the service scans for shared libraries of the form:

lib/<secondary-abi>/lib<name>.so

When it finds the libraries that it's looking for, the package manager copies them to /lib/lib.so, under the application's data directory (data/data/<package_name>/lib/).

If there is no shared-object file at all, the application builds and installs, but crashes at runtime.

[RoJoHub]

To Reproduce
We have tried to reproduce it with many devices but we can only reproduce it in one condition.

Install the release app
Upgrade OS from 32bit to 64bit
Open the app

If you update android,maybe system will not search again.Unless reinstall

[miguelslemos]

I had the same issue with AGP 3.3.2. For now, we are downgrading to AGP 3.2.0 until bump RN to 0.59

facebook/SoLoader#26
#23239

facebook/SoLoader#26 (comment)

[dulmandakh]

@vanydeasy could you please check CPU architecture of devices crashing. It seems that x86_64 is missing from abiFilters, and that might causing issues on x86_64 architecture.