[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.

[owinter86]

Hey @arjun-livquik you will need to build apk if you plan to have hermes enabled as its not currently compatible with app bundles.

#25927

[arjun-mavonic]

Thanks @owinter86
Could be that app might work just fine with APKs, because I have submitted APKs for staging build and had never seen this crash.
Sure will use APKs instead.

[jsaraiva]

Hello.

Have you tried with the latest release of Hermes?
#25646 (comment)

Of course, the "sdk<=19" problem does not apply to you, but there were lots of other fixes to Hermes too.
BTW, I built and submitted .aab release builds with hermes to the Play Store, and they haven't had any problems.

Also, be sure to clean the android build folders (I usually build with "./gradlew clean assembleRelease bundleRelease", just in case) if you change the "hermes enabled/disabled" setting.

Cheers!

[arjun-mavonic]

@jsaraiva Ofcourse I run ./gradlew clean bundleRelease everytime for creating .aab file. I have now rolled out to Alpha with all the APKs along with universal apk for now.

[IamMasterWayne]

"couldn't find DSO to load: libhermes.so "
React Native Version: 0.61.2
enableHermes: false
Still facing this issue

[fonov]

received from crashlytics

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.soloader.SoLoader.assertInitialized(SoLoader.java)
       at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java)
       at java.lang.Thread.run(Thread.java:760)

Brand: Xiaomi
Model: Redmi 4X
Orientation: Portrait
RAM free: 1.49 GB
Disk free: 18.04 GB
Version: 7.1.2
Orientation: Portrait
Rooted: No

[Tim-Snow]

I'm seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, only on android 6 LGE devices.

[waqas19921]

I am also seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, on google nexus 5x

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.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.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
       at java.lang.Thread.run(Thread.java:818)

Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.12 GB
Disk free: 218.66 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes

[acoutts]

I was able to resolve it with a ./gradlew clean in the /android folder.

[joseguya]

I am also seeing this crash in production with RN 0.61.2, using android bundles with hermes disabled, on google nexus 5x

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.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.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
       at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
       at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
       at java.lang.Thread.run(Thread.java:818)

Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.12 GB
Disk free: 218.66 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes

I have the same issue with the same version of android.

My Crashlytics report:

Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.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.hermes.reactexecutor.HermesExecutor.(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:952)
at java.lang.Thread.run(Thread.java:818)

Device
Brand: LGE
Model: Nexus 5X
Orientation: Portrait
RAM free: 3.18 GB
Disk free: 495.84 MB
Operating System
Version: 6.0.1
Orientation: Portrait
Rooted: Yes
Crash
Date: Nov 5, 2019, 5:05:00 PM
App version: 2.3.2 (2320)

[olegdev]

Same issues on Android 6.0.1
Any solution?

[ammarRajabA]

Any workaround for this issue, I'm trying to run a beta release on Google play and this crash shows in Crashlytics

[Symous]

I met the same issue and solved by this .

[MarinaAmy]

Hello,
I have the same worries, I've been going around in circles for several weeks because of hermes, I'm depressed: /

SoLoader: couldn't find DSO to load: libhermes-inspector.so caused by: dlopen failed: cannot locate symbol "_ZTIN8facebook6hermes8debugger13EventObserverE" referenced by "/data/data/com.test/lib-main/libhermes-inspector.so". .. result: 0
2020-11-03 11: 09: 53.512 16167-16270 / com.test E / SoLoader: couldn't find DSO to load: libhermes-executor-debug.so caused by: couldn't find DSO to load: libhermes-inspector .so caused by: dlopen failed: cannot locate symbol "_ZTIN8facebook6hermes8debugger13EventObserverE" referenced by "/data/data/com.test/lib-main/libhermes-inspector.so" ... result: 0 result: 0
2020-11-03 11: 09: 53.558 16167-16272 / com.test A / libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xffffffff in tid 16272 (mqt_js), pid 16167 (com.test )

Can somebody help me please ?

[namxg6626]

this problem occurred while I upgrading from 0.59.4 to 0.61.0

in android/app/build.gradle
I've added

project.ext.react = [
    //...
    enableHermes: true
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);

and

dependencies {
    //...
    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
    //...
}

and it works :)
hope this solution is useful for someone

[Michaelvons]

This is because SOLoader is absent.

Ensure

implementation'com.facebook.soloader:soloader:0.9.0+'

is added under dependencies in android/app/build.gradlle

clean your build
cd android
./gradlew clean

Try bundling
./gradlew bundleRelease

Exit android folder
cd ../

Try running
npx react-native run-android --variant=release

[badredaha]

@Michaelvons nice one 👍 ... but did you know why ? i have this probleme just with the last Android sdk 11 (Level 30)

[MarinaAmy]

Hello, could someone explain this error to me and tell me how to resolve it please?

DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

I use the react-native-jitsi-meet library

Thank you

[tiggem1993]

Hello, could someone explain this error to me and tell me how to resolve it please?

DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

I use the react-native-jitsi-meet library

Thank you

1. Update packagingOptions as per mention in url:
   Android build starts failing after updating to RN 0.58  react-native-community/jsc-android-buildscripts#80

2. Four types of JS Engine, choose as mention in this article:

• JSC (v241213.1.0),
• new JSC(v245459.0.0),
• Hermes and
• react-native-v8 (BEST ONE)

Article Link https://medium.com/walmartglobaltech/react-native-memory-profiling-jsc-vs-v8-vs-hermes-1626949a653b

[tvpranav]

@Michaelvons nice one 👍 ... but did you know why ? i have this probleme just with the last Android sdk 11 (Level 30)

Same issue for me with Level 30. Please let me know the solution.

[Desintegrator]

has same issue on android 4 when hermes is disabled

[napsta32]

I hope this get fixed soon. Android 6.0.1 is not working in the Play Store and I am unable to reproduce this error. Is there any emulator where I can check this is failing?

[Desintegrator]

@napsta32 at least you should be able to reproduce error at android 4.4 emulator. Not sure about android 6

[esutton]

Any suggestion on how to reproduce for verification a given solution fixes this problem?

• Google Play testing always reports fatal exception on Android 6.0.1, Nexus 5X devices
• I cannot reproduce by copying APK to locally installed AVD:
  • Nexus 5X, Android 6.0 (Google APIs), API 23 )
  • Nexus 5X, Android 4.4 (Google APIs), API 19 )

Current Verification Procedure:

1. Search StackOverflow, GitHub, etc. and make a suggested change to a build.gradle
2. Upload AAB to Google Play
3. Wait many hours until Google Play testing triggers a string of fatal exceptions and Firebase Crashlytics report emails notification to developer.
   Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
4. Repeat at Step nil #1

I have tried enableHermes: false and various versions of resolution strategies for "com.facebook.soloader:soloader:0.9.0+ without success.

Why is it trying to load Hermes when enableHermes is set to false?

		"react-native": "0.60.6",
		"react-native-maps": "0.26.1",

[Prernabudh]

RN 0.62.2 here with hermes enabled. For me adding

configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.8.2" } }

to my top-level build.gradle and

implementation "com.facebook.soloader:soloader:0.8.2"

as well as

ndk { abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64" }

to my app-level build.gradle did the trick. I think that especially the latter made the difference as before both apk's and aab's showed an additional (fifth) lib folder armeabi which did not contain all lib files, in particular not libhermes.so.

Did this fix issue for you? I've been trying to find a solution for this problem. I too have RN version 62.2

[fatihyildizhan]

Is there any difference for hermes on/off, app-bundle or APK?

package.json

"react": "16.13.1",
"react-native": "^0.63.4",
"@react-native-firebase/app": "^11.1.2",
"@react-native-firebase/crashlytics": "^11.1.2",

Most crashes device

Nexus 5X
Android 6.0.1

Fatal Exception: java.lang.UnsatisfiedLinkError
couldn't find DSO to load: libhermes.so SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com

ext {
        buildToolsVersion = "29.0.2"
        minSdkVersion = 17
        compileSdkVersion = 29
        targetSdkVersion = 29
    }

[JmStefanAndroid]

any solutions?

[fatihyildizhan]

@JmStefanAndroid Add configurations.all section to android > build.gradle > allprojects . This solved the issue for me. Plus, I run cd android ./gradlew clean before each release.

allprojects {
    repositories {
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }

        configurations.all {
            resolutionStrategy {
                // use 0.9.0 to fix crash on Android 11
                force "com.facebook.soloader:soloader:0.9.0+"
			}
		}

        google()
        jcenter()
        maven { url 'https://www.jitpack.io' }
    }
}

[troZee]

In my case I needed to add hermes path for each android build type

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each build type.

[juanamd]

I'm having this same issue with the following conditions:
-RN v0.63.4
-Hermes NOT enabled -> Using JSC
-Latest SoLoader (0.10.1)
-Using app bundle
-Run gradle clean before bundleRelease
-Issue only happens to certain devices on production (multiple Android versions and manufacturers)

After digging for a while I found this PR which mentions the "cause" of this issue when considering the previously mentioned conditions.
The PR author does a really good job explaining how this problem occurs.
In short, it's not related to Hermes at all, but the real error is being discarded and Hermes is being loaded instead as a fallback, which in turn fails since it's not enabled.
That PR solves the "error swallowing" problem so the real error can be propagated when the app crashes.
Please do merge that PR so we can figure out the real cause of this problem.

[rafalzawadzki]

In my case I needed to add hermes path for each android flavour

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each flavour.

Thanks! This worked for us, had to add the staging flavor.

[Grewer]

I've tried all of the above, and the result is still a failure

[janet-rivas]

I'm using hermes and RN 0.64.2 and android flavors

this combination works for me

android > build.gradle > allprojects

allprojects {
    repositories {
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }

        configurations.all {
            resolutionStrategy {
                // use 0.9.0 to fix crash on Android 11
                force "com.facebook.soloader:soloader:0.9.0+"
			}
		}

        google()
        jcenter()
        maven { url 'https://www.jitpack.io' }
    }
}

  if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        devImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

then

cd android
./gradlew clean

and build again

[kubanac95]

In my case I needed to add hermes path for each android build type

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
        qaImplementation files(hermesPath + "hermes-release.aar")
        stageImplementation files(hermesPath + "hermes-release.aar")
        prodImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

Probably it should be mentioned in the doc, that it needs to be added for each build type.

Thanks!

[gz1992]

configurations.all {
resolutionStrategy {
force "com.facebook.soloader:soloader:0.8.2"
}
}

hey, for me worked when i commented also everything related to flipper :)

[cortinico]

This and all the "couldn't find DSO to load" bugs have been fixed in React Native 0.71.

The issue on previous versions was a "too aggressive" clean-up logic in the react.gradle file. In 0.71 the clean-up logic has been rewritten to be more Android friendly and is now living inside the React Native Gradle Plugin.

I'm closing this, please update to 0.71 and open a new issue if the "couldn't find DSO to load" crash is still happening on 0.71+.