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

[taschik]

I uploaded a RN0.60.4 release build to Google Play and they ran automated tests leading to a lot of crashes coming in with the following stack trace:

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 738(SoLoader.java:738)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName + 591(SoLoader.java:591)
       at com.facebook.soloader.SoLoader.loadLibrary + 529(SoLoader.java:529)
       at com.facebook.soloader.SoLoader.loadLibrary + 484(SoLoader.java:484)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> + 20(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create + 27(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run + 949(ReactInstanceManager.java:949)
       at java.lang.Thread.run + 818(Thread.java:818)

Affected OS is always 6.0.1. Interestingly Hermes is not even enabled in my build.gradle:

project.ext.react = [
  entryFile: "index.android.js",
  enableHermes: false,  // clean and rebuild if changing
  bundleInDebug: false,
  bundleInRelease: true,
  root: "../../",
 ]
...
def enableHermes = project.ext.react.get("enableHermes", false);
...
// Hermes config
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }

I looked into the app bundle and extracted the apk for the device type that is crashing. It contains the libjsc.so file but not the libhermes.so. Imho this 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. I guess, they should be excluded?

I filed a report with the Hermes project here but they referred me to here.

React Native version:

System:
    OS: macOS 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 88.63 MB / 32.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
    Android SDK:
      API Levels: 23, 26, 27, 28
      Build Tools: 23.0.1, 25.0.0, 26.0.3, 27.0.3, 28.0.1, 28.0.2, 28.0.3
      System Images: android-24 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6156.11.34.5692245
    Xcode: 10.3/10G8 - /usr/bin/xcodebuild
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-native: ^0.60.4 => 0.60.4
  npmGlobalPackages:
    eslint-plugin-react-native: 3.5.0
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

Steps To Reproduce

1. Upload an RN0.60.4 app bundle with crash reporting to Playstore
2. check the crash reports

Describe what you expected to happen:

• The Google Play devices should not crash.
• Hermes library should not be loaded if disabled.
• libhermes-executor-release.so and libhermes-executor-debug.so should not get bundled

[owinter86]

I think this is related to my issue I posted on the Hermes repo.

https://github.com/facebook/hermes/issues/80

[taschik]

I am not so sure, because I did not even have Hermes activated because I was experiences issues even building it. However, the devices that run the app crash because they try to load it but it is not bundled (as configured).

[lachtos]

I'm having occasional crashes like this in production with hermes disabled also on 0.60.4

[MayrPatrick]

I am also having similar crashes as described here but WITH having hermes enabled as described wtihin facebook/hermes#76 .
Any idea why that might be happening?

[wsdt]

Having this issue too, when hermes disabled.

RN: 0.60.4

Device
Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.3 GB
Disk free: 2.06 GB

Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so at com.facebook.soloader.SoLoader.doLoadLibraryBySoName + 738(SoLoader.java:738) at com.facebook.soloader.SoLoader.loadLibraryBySoName + 591(SoLoader.java:591) at com.facebook.soloader.SoLoader.loadLibrary + 529(SoLoader.java:529) at com.facebook.soloader.SoLoader.loadLibrary + 484(SoLoader.java:484) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> + 20(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create + 27(HermesExecutorFactory.java:27) at com.facebook.react.ReactInstanceManager$5.run + 949(ReactInstanceManager.java:949) at java.lang.Thread.run + 818(Thread.java:818)

[Ekhui]

same problem in 5.1.1

[Ekhui]

anyone fixed it?

[fengyutongxing]

issue
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so

use version 0.60.0

[karvulf]

I got the same problem if I integrate my react-native-app to an existing android-app. I use react-native-version 0.60.4.
I documentated my code there: #25985

Edit: I could fix my problem. Maybe it helps you. ->#25985

[emrebicer]

Having the same issue, the project works fine on my local emulator but it gives the exact same error
with @wsdt , any solutions yet?

[arjun-mavonic]

How is react 60 stable I don't understand.

I have had crashes for
Device
Brand: LGE
Model: Nexus 5X
React Native Version: 0.60.3
Android Version: 6.0.1

I had created android app bundle( .aab file ) with hermes enabled. I have only debug and release variant. release variant has this problem.
Issue is opened on Aug 3 and it's been so many days, not a single working fix is available. Really frustrating.