react-native: Upgrading from v0.70.6 to v0.71.0 causing extremely slow debugging mode on Android

@cortinico Without Hermes it works fine.

Thanks for the confirmation. We’ll be releasing 0.71.1 sometime next week with the fix for this. I believe the version of Hermes that comes with 0.71.0 is coming with Hermes in Debug mode which is causing this. I’ll publish an update on this issue once we have the point release out.

For the time being you can either:

• Disable Hermes
• Stay on 0.70.x

@alabsi91 Thanks for the repro, I was able to confirm that the fix is working. It will be available in 0.71.1

And no, the issue is not related to react-navigation but to how we build and bundle Hermes

Can confirm it’s been fixed on 0.71.1. 🎉

I am having the same issue after upgrading, It takes about 2-4 after pressing something to respond, and the whole application is slow.

@cortinico Without Hermes it works fine.

I’ve set hermesEnabled=false at android/gradle.properties

ok artifacts are out now, 0.71.1 can be used and yes it should have the fix you need 😃

Oh, I spent so many time today thinking that one of my dependencies works wrong… Yeah, seems like this is React Native issue

@GuidoGagliardini @hassanannajjar Maybe hermesEnabled works better than hermbesEnabled?

as soon as maven publishes the artifacts, yeah… sadly there’s some hiccup on their side so please keep an eye on https://github.com/facebook/react-native/issues/35904

hermesEnabled = false newArchEnabled = false react-native 0.71.11 has the same issue Very slow.

I want to add, that not only buttons (touchable) works slowly. UI updates on active screen are throttling. And what is interesting - React Navigation transition animations works fine. And ScrollView works fine. Perf monitor shows -2 FPS sometimes (whatever that means)

0.71.8 has same issue

I was thinking like should we really use react-native for cross-platform app development anymore!

Is there anyone to occuring still this issue? I’m on 0.71.3 and it’s very slow on Android.

@cortinico

• Tested on Android Emulator and Samsung S10 device - debug mode - Hermes enabled.
• a simple test app with react navigation and FlatList, I hope this will hellp. https://github.com/alabsi91/RN071-hermes-debug-throttle-issue

+1

at least 2 to 4 seconds for any button to take action.

I’m guessing it has something to do with forcing all libraries to use 0.71.0

since i can only launch the app if i’ve built with the following in app/build.gradle:

configurations.all {
    resolutionStrategy {
        force 'com.facebook.react:react-native:0.71.0'
    }
}

cause otherwise i would get the following error:

couldn’t find DSO to load: libjscexecutor.so

Another thing that may or may not be the cause is that my project is still in javascript as i haven’t moved to typescript as stated in 0.71.0

Why is upgrading react-native is so HARD? cant upgrade to 0.71 and upgrade helper cannot help me!!

I’m facing the same issue. On the bright side, everything is normal in the release apk. By the way Cortinico I’m using Hermes.

We’re experiencing the same issue, we upgraded from RN 0.70.1.

we have an hiccup for the Hermes fix in the sense that we need to wait for a piece of the pipeline to get released and there’s a problem with getting it out of the door because of old credentials 😅 we want this fix to land asap but no clear ETA of when we’ll be unlocked (doesn’t depend on us) - as soon as we know more we’ll let you know

1. Hermes
2. Yes. I started new project. You can see that links on default page work a bit slowly. But if you setup basic React Navigation with 2 screens you can see how long it takes to start switching screens

p.s. production build via ./gradlew assembleRelease works fine, no throttling. Only dev mode issue on android

i’m same issue on 0.70.6, very slow navigation in tabs. I can’t find a solution, and I already have hermbesEnabled = false

hermesEnabled=false I noticeably improved the performance of the app

@AliZaib-Emumba I don’t think the answer you’re looking for is in this issue. This issue was caused by 0.71.0 which is resolved in 0.71.2. Your problem is probably different.

Can we close because of release v0.71.1 ?