react-native: Hermes enabled bundle causes white screen when installed from Google Play

Hey guys !

For me, it turned out it was a problem of SoLoader, which was fixed in 0.8.0. React Native 0.61.1 doesn’t use this version yet, so the solution was to set it up manually by adding the following to app/build.gradle:

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

I hope it works for you too 😃

@Alaa-Ben Was trying to solve this issue for past 2 days until I met your comment. Thank you very much!! I have found one problem though. Indeed bundleRelease now works in google playstore when I enable SoLoader(0.8.0), it is debug mode(i.e. just react-native run-android) that doesn’t work anymore. App crashes on start. So at the moment, I have to comment out

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

on android/app/build.gradle when I use debug mode to develop, and enable that part again for bundleReleases. Am I the only one with this issue??

This solution works with real devices but breaks react-native run-android on emulators, the app’s crashing after open with errors like this:

java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: APK was built for a different platform

Fixed According to master branch of react-native https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties you need to change SoLoader version to 0.8.2

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

I’m on the 0.62.2 version and this bug has been fixed!

i’am facing this issue RN 0.61.5

Just tested with react-native 0.61.1. Still broken 😢

@SnowLew App Still Crashes on Startup React native After installed from Play Store

“react-native”: “^0.63.3”,

project.ext.react = [
    entryFile: "index.js",
    enableHermes: true,  // clean and rebuild if changing
]

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

I’m on 0.63.2 and this issue is still not fixed for me! Cannot run the Android App in Debug or Release with Hermes enabled or disabled on my Emulator!

Closing this issue as the original bug as described has been fixed.

I can also confirm that is fixed now without any workarounds.

@Alaa-Ben Was trying to solve this issue for past 2 days until I met your comment. Thank you very much!! I have found one problem though. Indeed bundleRelease now works in google playstore when I enable SoLoader(0.8.0), it is debug mode(i.e. just react-native run-android) that doesn’t work anymore. App crashes on start. So at the moment, I have to comment out

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

on android/app/build.gradle when I use debug mode to develop, and enable that part again for bundleReleases. Am I the only one with this issue??

Please upvote the first post, don’t post +1 or same issue. You can subscribe to this issue on the right side.

This bug has been fixed, you can see in 0.62 version.

SO_LOADER_VERSION: 0.8.0

https://github.com/facebook/react-native/blob/0.62-stable/ReactAndroid/gradle.properties

Facing the same issue @desmondmc. Recently upgraded my project from 0.57.8 to 0.60.5. Also enabled def enableSeparateBuildPerCPUArchitecture = true and def enableProguardInReleaseBuilds = true. Can you please write here if you find a solution

This still occurs with React Native and Hermes, can we re-open the issue?

I can confirm @Alaa-Ben solution fixed the blank screen issue when deployed to google play

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

This is very very scary since the the production build with react-native run-android --variant=release works totally fine, but internally it builds an apk, while deploying to playstore it is in the form of aab which totally blanked out because of this issue. Many thanks again to @Alaa-Ben. Personally issue kind of reinforces how fragile is to use react native as I bump into these kind of weird things time and again.

@desmondmc try uploading the apks instead of the app bundle. In my case, uploading the app bundle to the play store showed a white blank screen on start up. But, uploading all the apks generated(with def enableSeparateBuildPerCPUArchitecture = true) did the trick. Give it a try.

@Alaa-Ben Was trying to solve this issue for past 2 days until I met your comment. Thank you very much!! I have found one problem though. Indeed bundleRelease now works in google playstore when I enable SoLoader(0.8.0), it is debug mode(i.e. just react-native run-android) that doesn’t work anymore. App crashes on start. So at the moment, I have to comment out

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

on android/app/build.gradle when I use debug mode to develop, and enable that part again for bundleReleases. Am I the only one with this issue??

This solution works with real devices but breaks react-native run-android on emulators, the app’s crashing after open with errors like this:

java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: APK was built for a different platform

Fixed According to master branch of react-native https://github.com/facebook/react-native/blob/master/ReactAndroid/gradle.properties you need to change SoLoader version to 0.8.2

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

Using this, all work fine in React-Native 0.60.6.

still throwing this error

Hey guys !

For me, it turned out it was a problem of SoLoader, which was fixed in 0.8.0. React Native 0.61.1 doesn’t use this version yet, so the solution was to set it up manually by adding the following to app/build.gradle:

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

I hope it works for you too 😃

In addition to forcing the soloader version, I had to exclude libjscexecutor.so in app/build.gradle to get the app working. This does not seem to break anything else.

packagingOptions {
    exclude '**/libjscexecutor.so'
}

Hey guys !

For me, it turned out it was a problem of SoLoader, which was fixed in 0.8.0. React Native 0.61.1 doesn’t use this version yet, so the solution was to set it up manually by adding the following to app/build.gradle:

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

I hope it works for you too 😃

Thanks, solve it with me, I was trying to find out these errors, I was able to find out when disabled Hermes. Then I searched and found this solution

The play store offers a ‘test store’ for internal tests. I recommend using it from time to time, specially when upgrading React Native versions.

same issue with @herio any test locally on debug or release is working. Only version returning the white screen is from the bundleRelease to play store

react-native: 0.60.4

I’m on react-native 0.63.4 and this is still happening for me when I have hermes enabled. Soon as the app opens up, flashes a white screen and closes. It happens when I do gradlew assembleRelease and install to an emulator, as well as an .aab uploaded to the play store.

Is there any way to tell which Hermes version you’re using?

A (terrible) workaround is to first run assembleRelease (so the js bundle is generated), and then run bundleRelease.

I don’t think this is related to Hermes though, since even when I disabled it I still have the same problem with bundling the app

Facing the same problem only when upload the bundleRelease to play store, assembleRelease is OK. “react-native”: “0.60.5”, “hermes-engine”: “0.1.1”,

Still the same issue with RN 0.62.1

We’ve been getting crash reports on our production app after upgrade to RN 0.61.5. Happens only to a minority of users, and we’re unable to reproduce it on any of our test devices. We’ve released versions with hermes both disabled and enabled and we got the error libhermes.so could not be found on all of these. Also tried forcing the SoLoader version at 0.8.0. Same issue. Is anyone else facing the same?

What we’ve tried so far:

1. Hermes disabled (where we started).
2. Hermes enabled.
3. Hermes disabled and SoLoader forced at 0.8.0.
4. Hermes enabled and SoLoader forced at 0.8.0.

When we tried running a fresh RN app on an emulator, the app crashed immediately. It doesn’t seem to be the same issue, but could be related. https://github.com/facebook/react-native/issues/28308

This issue should be more visible I think. Quite some time of trying and googling until I found it. The provided solution worked for me.

For me this did not work, we’re using react-native-navigation. It works with .apk though so we switched back to that.

Confirm, this change on app/build.gradle file works fine with Hermes enabled and Android App Bundle:

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

Can also confirm that @Alaa-Ben’s solution worked for me. Nice work 👍

This was done by testing in Google Play store. I use RNN and we switched back to APK to work around this issue. Are you using React Native Navigation too?

Seems to be only google play test devices that throw this error. No worries

Hey guys !

For me, it turned out it was a problem of SoLoader, which was fixed in 0.8.0. React Native 0.61.1 doesn’t use this version yet, so the solution was to set it up manually by adding the following to app/build.gradle:

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

I hope it works for you too 😃

This worked for me, thanks.

Just for other’s reference.

The previous issue was resolved. It was because of adding apply ./react.gradle to buid.gradle.

Removing it and adding the entire path in the react-native bundle resolved it.

@roots-ai

@jstheoriginal This didn’t work for me

configurations.all {
    resolutionStrategy {
        force 'org.webkit:android-jsc:r241213'
        force "com.facebook.soloader:soloader:0.8.0"
    }
}

On RN 0.61.4

why do you set different JSC version when you use Hermes? You can either use JSC or Hermes.

@gamingumar I use the workaround I posted in this issue with 0.61.3 without any issues. I use CI to deploy the so the environment is always clean.

@Alaa-Ben feel free, this should look like this https://github.com/facebook/react-native/commit/07d1075f372bb864ddc62b9c8f613b03becfa568

I am getting the same issue, also only when I upload bundle to play store with Hermes enabled. assembleRelease works fine and all works fine with Hermes disabled. RN version 0.61.1