Skip to content

SoLoaderDSONotFoundError: couldn't find DSO to load: libreactnative.so #55637

Open
Open
SoLoaderDSONotFoundError: couldn't find DSO to load: libreactnative.so#55637
Labels
Needs: Author FeedbackNeeds: ReproThis issue could be improved with a clear list of steps to reproduce the issue.

Description

@JaydeepAgravat
JaydeepAgravat
opened on Feb 20, 2026

Description

Description
continuation of #49111 & #55562 which was closed without resolution, even though many others have the same issue.

it crash on multiple real android devices on production, particularly android 11 & 12.

Steps to reproduce

run app

React Native Version

0.83.1

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info

System:
  OS: macOS 15.5
  CPU: (8) arm64 Apple M1
  Memory: 125.44 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 24.13.0
    path: /Users/sst/.nvm/versions/node/v24.13.0/bin/node
  Yarn:
    version: 1.22.22
    path: /Users/sst/.nvm/versions/node/v24.13.0/bin/yarn
  npm:
    version: 11.6.2
    path: /Users/sst/.nvm/versions/node/v24.13.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/sst/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.5
      - iOS 18.5
      - macOS 15.5
      - tvOS 18.5
      - visionOS 2.5
      - watchOS 11.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2025.1 AI-251.26094.121.2513.14007798
  Xcode:
    version: 16.4/16F6
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.16
    path: /opt/homebrew/Cellar/openjdk@17/17.0.16/libexec/openjdk.jdk/Contents/Home/bin/javac
  Ruby:
    version: 3.3.0
    path: /Users/sst/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.0
    wanted: 20.0.0
  react:
    installed: 19.2.0
    wanted: 19.2.0
  react-native:
    installed: 0.83.1
    wanted: 0.83.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true

Stacktrace or Logs

Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError: couldn't find DSO to load: libreactnative.so
	existing SO sources: 
		SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~XqhJ1EpBs99Ahf1FxVSQNw==/my.app-s-j3U1pjJ9NznSe6OnKJYQ==/lib/arm64 flags = 0]]
		SoSource 1: DirectApkSoSource[root = [/data/app/~~XqhJ1EpBs99Ahf1FxVSQNw==/my.app-s-j3U1pjJ9NznSe6OnKJYQ==/base.apk!/lib/arm64-v8a]]
		SoSource 2: DirectorySoSource[root = /system/lib64 flags = 2]
		SoSource 3: DirectorySoSource[root = /vendor/lib64 flags = 2]
	Native lib dir: /data/app/~~XqhJ1EpBs99Ahf1FxVSQNw==/my.app-s-j3U1pjJ9NznSe6OnKJYQ==/lib/arm64

       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
       at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:943)
       at com.facebook.soloader.SoLoader.loadLibraryOnAndroid(SoLoader.java:859)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:842)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:812)
       at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.<clinit>(ReactNativeFeatureFlagsCxxInterop.kt:28)
       at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.override(ReactNativeFeatureFlagsCxxInterop.kt)
       at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxAccessor.override(ReactNativeFeatureFlagsCxxAccessor.kt:615)
       at com.facebook.react.internal.featureflags.ReactNativeFeatureFlags.override(ReactNativeFeatureFlags.kt:402)
       at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:97)
       at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:43)
       at com.facebook.react.ReactNativeApplicationEntryPoint.loadReactNative(ReactNativeApplicationEntryPoint.java:31)
       at my.app.MainApplication.onCreate(MainApplication.kt:36)
       at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1211)
       at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6728)
       at android.app.ActivityThread.access$1500(ActivityThread.java:247)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2057)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:201)
       at android.os.Looper.loop(Looper.java:288)
       at android.app.ActivityThread.main(ActivityThread.java:7842)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
       at de.robv.android.xp0sed.Xp0sedBridge.main(Xp0sedBridge.java:112)

MANDATORY Reproducer

run app

Screenshots and Videos

No response

Activity

  1. JaydeepAgravat
    added
    Needs: Triage 🔍
    on Feb 20, 2026
  2. react-native-bot
    added
    Needs: Author Feedback
    Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.
    on Feb 20, 2026

  3. react-native-bot commented on Feb 20, 2026

    @react-native-bot
    react-native-bot
    on Feb 20, 2026
    Collaborator

    Warning

    Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:


    You can read more about about it on our website: How to report a bug.

  4. react-native-bot
    removed
    Needs: Triage 🔍
    on Feb 20, 2026

  5. tominou commented on Feb 20, 2026

    @tominou
    tominou
    on Feb 20, 2026

    I think this is more of an Android issue.

    Adding this in your app/build.gradle should fix it :

    android {
    packagingOptions {
        jniLibs {
            useLegacyPackaging = true
        }
    }
}

  6. Nader-CS commented on Feb 24, 2026

    @Nader-CS
    Nader-CS
    on Feb 24, 2026

    I think this is more of an Android issue.

    Adding this in your app/build.gradle should fix it :

    android {
    packagingOptions {
        jniLibs {
            useLegacyPackaging = true
        }
    }
}

    can anyone confirm this ?

  7. MaxwellKJr commented on Feb 24, 2026

    @MaxwellKJr
    MaxwellKJr
    on Feb 24, 2026

    I think this is more of an Android issue.

    Adding this in your app/build.gradle should fix it :

    android {
    packagingOptions {
        jniLibs {
            useLegacyPackaging = true
        }
    }
}

    tried this, seems the issue wasn't fixed. Got the same Crashlytics report after using this solution

  8. rahulnainwalttn commented on Feb 26, 2026

    @rahulnainwalttn
    rahulnainwalttn
    on Feb 26, 2026

    Facing same issue -

          Fatal Exception: com.facebook.soloader.x: couldn't find DSO to load: libreactnative.so
existing SO sources: 
	SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/lib/arm64 flags = 0]]
	SoSource 1: DirectApkSoSource[root = [/data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/split_config.xxhdpi.apk!/lib/x86_64, /data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/split_config.en.apk!/lib/x86_64, /data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/base.apk!/lib/x86_64, /data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/split_config.arm64_v8a.apk!/lib/x86_64]]
	SoSource 2: DirectorySoSource[root = /system/lib64 flags = 3]
	SoSource 3: DirectorySoSource[root = /vendor/lib64 flags = 3]
Native lib dir: /data/app/~~1_drNTJ9A9Lf9JknlnAQeg==/com.astro.sott-noSOXCAuD1Ev8F29gTCedQ==/lib/arm64

   at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
   at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
   at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:943)
   at com.facebook.soloader.SoLoader.loadLibraryOnAndroid(SoLoader.java:859)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:842)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:812)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.<clinit>(ReactNativeFeatureFlagsCxxInterop.kt:28)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxAccessor.override(ReactNativeFeatureFlagsCxxAccessor.java:875)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlags.override(ReactNativeFeatureFlags.kt:558)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:101)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:43)
   at com.facebook.react.ReactNativeApplicationEntryPoint.loadReactNative(ReactNativeApplicationEntryPoint.java:31)
   at com.myproject.MainApplication.onCreate(MainApplication.kt:63)
   at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1386)
   at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7504)
   at android.app.ActivityThread.-$$Nest$mhandleBindApplication()
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2416)
   at android.os.Handler.dispatchMessage(Handler.java:107)
   at android.os.Looper.loopOnce(Looper.java:232)
   at android.os.Looper.loop(Looper.java:317)
   at android.app.ActivityThread.main(ActivityThread.java:8705)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:886)

  9. tominou commented on Feb 26, 2026

    @tominou
    tominou
    on Feb 26, 2026

    It seems to be an issue only on ROOTED devices.
    Check if you have xp0sed in the logs, or if crashlytics flags the device as rooted.

    I dont think we can do much against heavily modified rooted devices.

  10. Nader-CS commented on Feb 27, 2026

    @Nader-CS
    Nader-CS
    on Feb 27, 2026

    It seems to be an issue only on ROOTED devices. Check if you have xp0sed in the logs, or if crashlytics flags the device as rooted.

    I dont think we can do much against heavily modified rooted devices.

    No, all devices that encountered this error are not rooted.

  11. dimlksiin-tech commented on Mar 1, 2026

    @dimlksiin-tech
    dimlksiin-tech
    on Mar 1, 2026
          Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError: couldn't find DSO to load: libreactnative.so
existing SO sources: 
	SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/lib/arm64 flags = 0]]
	SoSource 1: DirectApkSoSource[root = [/data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.it.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.sq.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.th.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.iw.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.kk.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.lo.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.in.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.nl.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.kn.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.vi.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.sk.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.el.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.ur.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.be.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.mdpi.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.ta.apk!/lib/x86_64, /data/app/~~ENdcHK_0Bv_e3y3A5EsT7Q==/com.plus24-Ys-F38pclQb_sSqqU2LYMQ==/split_config.bn<truncated: 7373 chars>
   at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
   at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
   at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:943)
   at com.facebook.soloader.SoLoader.loadLibraryOnAndroid(SoLoader.java:859)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:842)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:812)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.<clinit>(ReactNativeFeatureFlagsCxxInterop.kt:28)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxAccessor.override(ReactNativeFeatureFlagsCxxAccessor.kt:615)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlags.override(ReactNativeFeatureFlags.kt:402)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:97)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:43)
   at com.facebook.react.ReactNativeApplicationEntryPoint.loadReactNative(ReactNativeApplicationEntryPoint.java:31)
   at com.plus24.MainApplication.onCreate(MainApplication.kt:36)
   at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1194)
   at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6735)
   at android.app.ActivityThread.access$1300(ActivityThread.java:239)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1915)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loop(Looper.java:223)
   at android.app.ActivityThread.main(ActivityThread.java:7680)
   at java.lang.reflect.Method.invokeNative(Method.java)
   at java.lang.reflect.Method.invoke(Method.java:423)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

  12. dimlksiin-tech commented on Mar 2, 2026

    @dimlksiin-tech
    dimlksiin-tech
    on Mar 2, 2026

    android/app/build.gradle

    packaging {
    jniLibs {
        useLegacyPackaging = true
    }
}

    починилось, крашей больше нет !!!

  13. dimlksiin-tech commented on Mar 2, 2026

    @dimlksiin-tech
    dimlksiin-tech
    on Mar 2, 2026

    Думаю, это скорее проблема Android.
    Добавление этого в ваш файл app/build.gradle должно решить проблему:

    android {
    packagingOptions {
        jniLibs {
            useLegacyPackaging = true
        }
    }
}

    Может кто-нибудь это подтвердить?

    I checked - it's true, there are no crashes

    // checked and it works
    packaging {
    jniLibs {
    useLegacyPackaging = true
    }
    }

    packaging

    packagingOptions - old

  14. iAndrew25 commented on Mar 11, 2026

    @iAndrew25
    iAndrew25
    on Mar 11, 2026

    any updates?

  15. 38 remaining items

  16. christopherboisvert commented on Jul 14, 2026

    @christopherboisvert
    christopherboisvert
    on Jul 14, 2026

    I have the same bug with Expo 57 and react-native 0.86.0

  17. christopherboisvert commented on Jul 14, 2026

    @christopherboisvert
    christopherboisvert
    on Jul 14, 2026

    Still same issue Android 11, OnePlus8Pro, Honor 10i

    Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError: couldn't find DSO to load: libc++_shared.so
	existing SO sources: 
		SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/lib/x86_64 flags = 0]]
		SoSource 1: DirectApkSoSource[root = [/data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.pa.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.uz.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.sw.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.hy.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.hu.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.is.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.mdpi.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.cs.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.gl.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.ka.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.fa.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.sq.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/base.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJI<truncated: 9557 chars>
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
       at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
       at com.facebook.soloader.SoLoader.loadDependency(SoLoader.java:920)
       at com.facebook.soloader.DirectApkSoSource.loadDependencies(DirectApkSoSource.java:166)
       at com.facebook.soloader.DirectApkSoSource.loadLibrary(DirectApkSoSource.java:76)

    Weirdly, I got this error on the same exact devices too. OnePlus Pro 8, Huawei Honor 10. But in fact, my firebase testers didn't use any of those devices. Where is the source of these error devices if they don't get any access to the apk?

    Is it maybe the automated testing that Google Play does ?

  18. rishabhshuklayt commented on Jul 17, 2026

    @rishabhshuklayt
    rishabhshuklayt
    on Jul 17, 2026

    +1 with the Model:Nexus 5X reports

    I am Facing The Same Issue

    The phone officially stopped receiving updates at Android 8.0 But Logs shows it was Android 13 may be custom ROM installations, And May be The Hardware and Software compatibility lead to this issue . It may be a Automated Google Play Crawler

  19. jaredandrews commented on Jul 27, 2026

    @jaredandrews
    jaredandrews
    on Jul 27, 2026

    Just to add a data point, I have an app that is only released via Google Play Internal Testing right now. I got 13 instances of this crash over the last week and started looking into it this morning.

    The report shows a non-rooted LGE Nexus 5X running Android 13 as the culprit.

    I only have 5 testers right now. None of them are using this device.

    This leads me to believe it is some automated Google Play testing.

    I always assumed that the automated Google Play testing happened prior to release, but some network logs I have from their bot thrashing around seem to indicate that automated testing is happening well after a new version of the app is released. Both instances of this occurred about 12 hours after new builds were released.

    I am uploading aab releases generated with eas build --local FWIW.

  20. yittoo commented on Jul 30, 2026

    @yittoo
    yittoo
    on Jul 30, 2026

    Okay as people above me think I think it is correlated to google play. I cross checked our app's putting to prod dates (which is 1-2 day within review) with crashes here are my findings.

    Comparing release dates with crashlytics

    Release dates (usually 1 or 2 day before is added to review)

    30 july 2026 11:10
    20 Jul 2026 10:43
    30 Jun 2026 09:53
    19 Jun 2026 09:42
    2 Jun 2026 10:04
    1 Jun 2026 10:07

    Crashlytics reports

    29 july - 16 reports
    18-22 july range - no reports
    30 june - 3 reports
    21 june - 5 reports
    4 june - 3 reports
    3 june - 3 reports

    Another fact about these reports

    All reports are usually within seconds of each other in single run, it rarely is 40minute between them, but often it can be in span of 30 seconds or same second different devices.

    My own conclusion

    I think these are google simulators, my gut feeling is 99% sure. I think each time they use different set of simulators, and if you are lucky all miss, thus no report, if you are unlucky 16 reports like today's for us. Our users are people who use app for their livelihood and if there are crashes, they are extremely verbal in feedback, and there's nothing related to this being reported.

    Also

    we in our acceptance environment had this occur too, we release aab to acceptance also, and none of our internal testers have said oneplus device in acceptance crashes

    Edit:

    Usually it's following devices for us

    OnePlus 8 Pro
    Huawei HRY-LX1T
    Google Pixel 6 Pro
    Nexus 5x
    Qemu Standard PC (i440FX + PIIX, 1996)

  21. jaredandrews commented on Jul 30, 2026

    @jaredandrews
    jaredandrews
    on Jul 30, 2026

    @yittoo

    All reports are usually within seconds of each other in single run, it rarely is 40minute between them, but often it can be in span of 30 seconds or same second different devices.

    I have also observed this.

  22. sudomastery
    added a commit that references this issue on Jul 30, 2026

    Fix two crash-on-launch bugs found while verifying the FCM removal on…

    9e90cdb

  23. baldev-foremost commented on Aug 19, 2026

    @baldev-foremost
    baldev-foremost
    on Aug 19, 2026

    Is there any update?

    Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError: couldn't find DSO to load: libreactnative.so
    existing SO sources:
    SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~ALfTaAsZz5rLNQ5DQxOVig==/com.fairly-hYvGAqrNx-cuYD578ukioA==/lib/arm64 flags = 0]]
    SoSource 1: DirectApkSoSource[root = [/data/app/~~ALfTaAsZz5rLNQ5DQxOVig==/com.fairly-hYvGAqrNx-cuYD578ukioA==/base.apk!/lib/arm64-v8a]]
    SoSource 2: DirectorySoSource[root = /system/lib64 flags = 2]
    SoSource 3: DirectorySoSource[root = /vendor/lib64 flags = 2]
    Native lib dir: /data/app/~~ALfTaAsZz5rLNQ5DQxOVig==/com.fairly-hYvGAqrNx-cuYD578ukioA==/lib/arm64

       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
   at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
   at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:943)
   at com.facebook.soloader.SoLoader.loadLibraryOnAndroid(SoLoader.java:859)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:842)
   at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:812)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.<clinit>(ReactNativeFeatureFlagsCxxInterop.kt:28)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxInterop.override(ReactNativeFeatureFlagsCxxInterop.kt)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsCxxAccessor.override(ReactNativeFeatureFlagsCxxAccessor.kt:725)
   at com.facebook.react.internal.featureflags.ReactNativeFeatureFlags.override(ReactNativeFeatureFlags.kt:468)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:101)
   at com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load(DefaultNewArchitectureEntryPoint.kt:43)
   at com.facebook.react.ReactNativeApplicationEntryPoint.loadReactNative(ReactNativeApplicationEntryPoint.java:31)
   at com.fairly.MainApplication.onCreate(MainApplication.kt:43)
   at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1223)
   at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6762)
   at android.app.ActivityThread.access$1500(ActivityThread.java:256)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2091)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loopOnce(Looper.java:201)
   at android.os.Looper.loop(Looper.java:288)
   at android.app.ActivityThread.main(ActivityThread.java:7870)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)

  24. arvindyadav2 commented on Aug 30, 2026

    @arvindyadav2
    arvindyadav2
    on Aug 30, 2026

    Still same issue Android 11, OnePlus8Pro, Honor 10i

    Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError: couldn't find DSO to load: libc++_shared.so
	existing SO sources: 
		SoSource 0: ApplicationSoSource[DirectorySoSource[root = /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/lib/x86_64 flags = 0]]
		SoSource 1: DirectApkSoSource[root = [/data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.pa.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.uz.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.sw.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.hy.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.hu.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.is.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.mdpi.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.cs.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.gl.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.ka.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.fa.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/split_config.sq.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJICUPwedg==/base.apk!/lib/arm64-v8a, /data/app/~~NRdeT6_6awFBDJfpLjBEug==/com.abc.abc.abc.unblock-GhyXLKHaM-QFNJI<truncated: 9557 chars>
       at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1216)
       at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:1078)
       at com.facebook.soloader.SoLoader.loadDependency(SoLoader.java:920)
       at com.facebook.soloader.DirectApkSoSource.loadDependencies(DirectApkSoSource.java:166)
       at com.facebook.soloader.DirectApkSoSource.loadLibrary(DirectApkSoSource.java:76)

    Weirdly, I got this error on the same exact devices too. OnePlus Pro 8, Huawei Honor 10. But in fact, my firebase testers didn't use any of those devices. Where is the source of these error devices if they don't get any access to the apk?

    Is it maybe the automated testing that Google Play does ?

    same for me OnePlus Pro 8

  25. arvindyadav2 commented on Aug 30, 2026

    @arvindyadav2
    arvindyadav2
    on Aug 30, 2026

    did anyone find any solution for this error please help ?

  26. haitienwork commented on Aug 30, 2026

    @haitienwork
    haitienwork
    on Aug 30, 2026

    did anyone find any solution for this error please help ?

    check the previous comment. still no solution bcs real device with same model still got no crash. its Google Bot and still dont know how they tested.
    Just dont know is it affect Vital Points on Play Console will be less suggestion app or not

  27. arvindyadav2 commented on Aug 30, 2026

    @arvindyadav2
    arvindyadav2
    on Aug 30, 2026

    did anyone find any solution for this error please help ?

    check the previous comment. still no solution bcs real device with same model still got no crash. its Google Bot and still dont know how they tested. Just dont know is it affect Vital Points on Play Console will be less suggestion app or not

    Do we have any confirmed solution for this crash yet? Since it’s affecting our crash-free users percentage, can we identify what Google’s test device/environment is doing and whether there’s a safe fix we can apply?

  28. arvindyadav2 commented on Aug 30, 2026

    @arvindyadav2
    arvindyadav2
    on Aug 30, 2026
    Image

  29. DavideMariuzzo118118money commented on Sep 15, 2026

    @DavideMariuzzo118118money
    DavideMariuzzo118118money
    on Sep 15, 2026

    I had the same issue, might be because SoLoader.init(this,false) was left on MainApplication.kt. I've removing it according to https://react-native-community.github.io/upgrade-helper/?from=0.75.1&to=0.78.0, I'll need to wait and see if the crash persist after the change

  30. amrit-hash commented on Sep 15, 2026

    @amrit-hash
    amrit-hash
    on Sep 15, 2026

    Adding production data that matches this issue closely, and also matches the pattern in the linked #49111.

    Environment

    React Native 0.81.5, Expo SDK 54
    New Architecture enabled (newArchEnabled: true), Hermes enabled
    targetSdk/compileSdk 36, AGP 8.13.2, NDK 27.1.12297006
    Distribution: Google Play Store only, Production track (confirmed internally — no sideloading/alternate stores)
    Crash

    Fatal Exception: com.facebook.soloader.SoLoaderDSONotFoundError
couldn't find DSO to load: libc++_shared.so
...
com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:1216)
com.facebook.react.ReactNativeApplicationEntryPoint.loadReactNative (ReactNativeApplicationEntryPoint.java:31)
com.ikmobile.app.MainApplication.onCreate (MainApplication.kt:48)
android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1194)

    The DirectorySoSource root reports one ABI's native lib dir (lib/x86_64), while the fallback DirectApkSoSource search only enumerates a different ABI's split config APKs — the same architecture-directory mismatch signature described in #49111.

    Scale

    77 crash events / 7 unique users so far, recurring across two consecutive shipped versions (same crash before and after a version bump, no code changes to the crash path in between)
    Confirmed affected devices: Huawei, OnePlus, and a Google Pixel 6 Pro — so this isn't limited to OEM/non-GMS devices
    Added PackageManager.getInstallSourceInfo() as a Crashlytics custom key to rule out sideloading: 61% (41/50 events) confirm install_source = com.android.vending (genuine Play Store installs), remainder reported "unknown"

    Happy to share more device/OS breakdowns or try a proposed repro/workaround if one comes up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Author FeedbackNeeds: ReproThis issue could be improved with a clear list of steps to reproduce the issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions