react-native: React Native (0.60.4) Android app crashes after splash screen when Hermes is enabled

Downgrading React Native works for me.

do cd android && ./gradlew clean && cd … and build again : )

The painful upgrade process to 0.60 must be the worst one so far. Fetch stops working, splash screens are not compatible with Hermes. These are not exotic edge cases, this are very common scenarios. The premature issue closing doesn’t help either.

Please disable ram-bundle when using Hermes. They are currently not compatible but also when you are using Hermes with bytecode and inline requires the RAM bundling optimizations should not be necessary any longer 😃

@cpojer But I did not include the rum-bundle and inline-require. And I still have a problem. Why you close issue ?

Same here but it just hangs without a crash on 0.60.5 with Hermes enabled, this only happens when using ./gradlew bundleRelease and not when using ./gradlew assembleRelease

Same here but it just hangs without a crash on 0.60.5 with Hermes enabled, this only happens when using ./gradlew bundleRelease and not when using ./gradlew assembleRelease

+ 1

Still unclear why @cpojer closed this, as this is clearly not solved.

I just did a 0.57.4 to 0.59.10 on another project. Completely painless, done in 10 minutes. Definitely holding off on 0.60 until the dust settles on the major blockers.

still not working even hermes is not enabled

@cpojer Please re-open this issue ASAP.

@cpojer After I have removed the usage of ram-bundle and inline-require in my project (also updated metro’s config to match this), I still encounter the same problem. I think this issue should still be open.

hello,every one. i am facing the same problem,and i do the follow to fix it.

1. change the file like @RageBill said
2. cd ./android && ./gradlew clean
3. cd …/ && react-native run-android

Same here, after upgrade from 0.59.2 to 0.60.3, the app is installed as expected. When launched, splash appears and crash without error. Tested on API 28 and API 29

Hello 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 suspect this problem happens with FlatList components. Now that I have everything set up, I can use Hermes in my app. However, once I enter any pages with a FlatList component, the app crashes again and the same error shows:

2019-07-24 17:23:36.690 9011-9080 A/libc: /Users/willholen/intern/hermes/include/hermes/VM/HandleRootOwner.h:413: hermes::vm::PinnedHermesValue *hermes::vm::GCScope::newHandle(hermes::vm::HermesValue): assertion "getHandleCountDbg() < handlesLimit_ && "Too many handles allocated in GCScope"" failed
2019-07-24 17:23:36.690 9011-9080 A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 9080 (mqt_js)

It’s incomprehensible to me that this is still a problem in RN 0.60.4

I’m having anrs all over the place with hermes, not just with onesignal. Why would they release 0.60.4 without testing it. I’m glad I halted the rollout before I nuked all my users. I’m pretty sure this is the last straw for me with RN after the signal 11 disaster in May. I’m going to just build in a web view from now on.

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

@rezaarifian Yes, there is significant increase in app size due to hermes but if you are looking for playstore submission you can use “app.aab” file which is lesser than the size of “app.apk”

@rezaarifian Are you using react-native-firebase ?

Should we reopen this issue in another thread since there is no response from @cpojer?

Literally upgraded from 0.59.8 to 0.60.4 to use ram-bundles WITH Hermes, to now have this issue closed. 😄

Not workin release build, RN 0.60.4, hermess enabled, error:

* * * * * * * * * * * * * * * *
Build fingerprint: 'xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.6.0.PFGMIXM:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 8796, tid: 8853, name: mqt_js  >>> ru.insales.mobile <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message too long: claimed length = 612
    r0  00000000  r1  00002295  r2  00000006  r3  00000008
    r4  0000225c  r5  00002295  r6  c80776ac  r7  0000010c
    r8  c8d74500  r9  c8077bfe  r10 ea343d8c  r11 00000000
    ip  ea33c3bc  sp  c8077698  lr  ea2a67f9  pc  ea29e01e

backtrace:
    #00 pc 0001d01e  /system/lib/libc.so (abort+58)
    #01 pc 0001d28f  /system/lib/libc.so (__assert2+22)
    #02 pc 00068415  /data/app/ru.insales.mobile-**********==/lib/arm/libc++_shared.so
    #03 pc 00068595  /data/app/ru.insales.mobile-**********==/lib/arm/libc++_shared.so
    #04 pc 0006fb1d  /data/app/ru.insales.mobile-***********==/lib/arm/libc++_shared.so
    #05 pc 0006facb  /data/app/ru.insales.mobile-***********==/lib/arm/libc++_shared.so (std::terminate()+70)
    #06 pc 0001199f  /data/app/ru.insales.mobile-***********==/lib/arm/libhermes.so

******** - for security, I hid my keys, but the problem is the same. Drop on the splash screen.