App Crashes When Hermes is Disabled on Some Android 10 Devices `couldn't find DSO to load: libhermes.so SoSource` about react-native HOT 6 OPEN

from react-native.

from react-native.

It looks like you have set your minSdkVersion to 24 @Abhishek-Khanduri so perhaps this is relevant to you

from react-native.

This is my code in app/build.gradle

This is how the app/build.gradle file should look like in a 0.71 project:
https://github.com/facebook/react-native/blob/0.71-stable/template/android/app/build.gradle

So your application is definitely misconfigured @Abhishek-Khanduri

from react-native.

my minSdkVersion is 21 but i am facing this same issue multiple of times. @cortinico @brien-crean

from react-native.

@sudhanshu-busy I followed a systematic approach to troubleshoot and resolve the crash issue with our React Native app on an Android 10 device. Here are the steps I took:

Set Up Sample App:

• Created a fresh sample app using React Native 0.71.0.
• Disabled Hermes.
• Tested the sample app on an Android 10 device, and it worked as expected without any crashes.

Configuration Transfer:

• Moved multiple configuration files(build.gradle and app/build.gradle) from the sample app to our app.
• With these minimal changes, our app worked without crashing.

Incremental Configuration Addition:

• Gradually re-added all additional configurations that had been added during the development of our app.
• Monitored the app's behavior after each addition.

Identified Problematic Code Snippet:

• Discovered a code snippet related to file versioning that was affecting the specific file versions being added to the APK.
  Noted that this snippet was not present in the sample app's configuration.

Isolated the Issue:

• Upon re-adding the problematic snippet, the app encountered the same error related to the Hermes engine that had been occurring for the past week.

This is the code snippet that we suspect that is causing the issue

allprojects {
    repositories {
        maven {
            url "https://github.com/jitsi/jitsi-maven-repository/raw/master/releases"
        }
        configurations.all {
            resolutionStrategy {
                eachDependency { DependencyResolveDetails details ->
                    if (details.requested.group == 'com.facebook.react' && details.requested.name == 'react-native') {
                        def file = new File("$rootDir/../node_modules/react-native/package.json")
                        def version = new groovy.json.JsonSlurper().parseText(file.text).version
                        details.useVersion version
                    }
                }
            }
        }
    }
}

You can use similar approach to back trace the root cause

from react-native.