hermes: [CRASH] Android 6.0.1 crashes with java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so

I am using firebase to track the crashes and a few of my users with following Android version are having crashes:

Android 4.2.2 Android 4.3 Android 4.3.1 Android 4.4.2 Android 5.1

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

I am using RN 0.60.5 and split APKs.

I’m seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled.

Thanks @mhorowitz for the hint. I did look into the app bundle and extracted the apk for the device type. It contains the libjsc.so file but not the libhermes.so. Which imho is correct because my gradle is configured to not include it. The big question is why does it want to load it if it not enabled? What also surprised me is that I found libhermes-executor-release.so and libhermes-executor-debug.so in it too. Shouldn’t they be excluded too? If you think it will make sense to bring this up in the react-native project, I will do so and link the issue here.

the relevant bit of code is here: https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/ReactInstanceManagerBuilder.java#L288-L296 React Native tries to load JSC, and if it’s not present, it tries to load Hermes. If the latter fails, you get the exception you’re seeing.

Since you’re building for JSC, the latter error is expected, but the first error is not. From your screen shot, libjscexecutor.so seems to be present, but the code is swallowing the error loading JSC, which is what would tell us what’s wrong. I’ve asked someone here to improve the error reporting. In the interim, you could hack this code to comment out the try/catch. This will break enableHermes in the gradle files, but it should illuminate the problem.

One hypothesis is that the failing devices are not arm32, and the libraries for that platform are different.

I it makes sense to open an RN issue. I’m not sure what the problem is, but I suspect the fix will need to be in the react-native repo.

You’re right that those hermes .so files should be excluded, but that’s a separate problem.

facebook/react-native#25986 (comment) @Zloka

YES，but not work. My project has used Jsc, and disable Hermes. It OK in android 6.* 7.* It has crashed in android 5.0

Something wrong with SoLoader.loadLibrary(“jscexecutor”);

private JavaScriptExecutorFactory getDefaultJSExecutorFactory(String appName, String deviceName) {
    try {
      // If JSC is included, use it as normal
      SoLoader.loadLibrary("jscexecutor"); // something wrong with here
      return new JSCExecutorFactory(appName, deviceName);
    } catch(UnsatisfiedLinkError jscE) {
      jscE.printStackTrace();  // something wrong with here
      // Otherwise use Hermes
      return new HermesExecutorFactory();
    }
  }

The crash is here https://github.com/facebook/react-native/issues/25923#issuecomment-554295179

I’m still trying to find the solution. -!!!

Our build pipeline does fresh checkouts removing all gradle caches programmatically and running gradle in a non-daemon mode.

rm -rf node_modules && rm -rf $TMPDIR/react-*
rm -rf $HOME/.gradle/caches
npm i

echo "Build Android"
bundle exec fastlane android build flags:--no-daemon --env=live

Shouldn’t that be sufficient and not require us to run a ./gradlew clean ?

Thanks for the more detailed report! A few other people have reported similar issues in https://github.com/facebook/react-native/issues/25601 and running ./gradlew clean has fixed it. Can you try that?