React-native: enableHermes on React Native 0.60.3 is extremely slow.

[ollydixon]

I'm testing with two real devices and an emulator. They are all extremely slow with the hermes flag enabled. Had to enabled it for 0.60.3 :-(

By extremely slow, pressing something takes about 3 seconds for it to react.

App was working fine before swiching flag.

My configuration is as such:
(Hidious I know)

app/build.gradle

apply plugin: "com.android.application"

import com.android.build.OutputFile

apply plugin: 'io.fabric'
repositories {
    maven { url 'https://maven.fabric.io/public' }
}

project.ext.react = [
        entryFile: "index.js",
        enableHermes: true,
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false)


apply from: "../../node_modules/react-native/react.gradle"

android {
    compileSdkVersion rootProject.ext.compileSdkVersion
    buildToolsVersion rootProject.ext.buildToolsVersion

    defaultConfig {
        applicationId "com.magicword.ahahah"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 46
        versionName "1.4.1"
        ndk {
            abiFilters "armeabi-v7a", "x86", "arm64-v8a"
        }
        multiDexEnabled true
        vectorDrawables.useSupportLibrary = true
    }
    lintOptions {
        abortOnError false
    }
    buildTypes {
        debug {
            manifestPlaceholders = [isDebug: true]
        }
        release {
            manifestPlaceholders = [isDebug: false]
            minifyEnabled false
            useProguard true
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a": 1, "x86": 2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    packagingOptions {
        pickFirst 'lib/x86/libc++_shared.so'
        pickFirst 'lib/x86_64/libjsc.so'
        pickFirst 'lib/arm64-v8a/libjsc.so'
        pickFirst 'lib/arm64-v8a/libc++_shared.so'
        pickFirst 'lib/x86_64/libc++_shared.so'
        pickFirst 'lib/armeabi-v7a/libc++_shared.so'
    }
}

dependencies {
    implementation 'com.android.support:multidex:1.0.3'
    implementation project(':react-native-iap')
    implementation project(':react-native-location')
    implementation project(':react-native-fbsdk')
    implementation project(':react-native-navigation')
    compile fileTree(include: ['*.jar'], dir: 'libs')
    // Android stuff
    implementation 'com.google.android.material:material:1.0.0'
    implementation 'com.android.support:multidex:1.0.3'
    implementation "com.android.support:support-annotations:${rootProject.ext.supportLibVersion}"
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.android.support:animated-vector-drawable:${rootProject.ext.supportLibVersion}"
    implementation "com.android.support:customtabs:${rootProject.ext.supportLibVersion}"
    implementation "com.android.support:design:${rootProject.ext.supportLibVersion}"
    //Google stuff
    implementation "com.google.android.gms:play-services-location:16.0.0"
    implementation 'com.google.android.gms:play-services-identity:16.0.0'
    implementation "com.google.android.gms:play-services-base:17.1.0"
    // Maps
    // React native stuff
    implementation 'com.facebook.react:react-native:+'
    // From node_modules
    // Facebook
    implementation 'com.facebook.android:facebook-android-sdk:4.38.1'
    // Firebase stuff
    implementation project(':react-native-firebase')

    implementation 'com.google.firebase:firebase-core:16.0.8'
    implementation 'com.google.firebase:firebase-firestore:18.2.0'
    implementation 'com.google.firebase:firebase-storage:16.1.0'
    implementation 'com.google.firebase:firebase-auth:16.2.1'
    implementation 'com.google.firebase:firebase-messaging:17.5.0'
    implementation 'com.google.firebase:firebase-functions:16.3.0'
    compile('com.crashlytics.sdk.android:crashlytics:2.9.2@aar') {
        transitive = true
    }
    compile project(path: ':lottie-react-native')
    compile project(path: ':rn-fetch-blob')
    compile project(path: ':react-native-linear-gradient')
    compile project(path: ':react-native-image-crop-picker')
    compile project(path: ':react-native-maps')
    compile project(path: ':react-native-device-info')
    compile project(path: ':react-native-cookies')
    compile project(path: ':react-native-cookies')
    compile project(path: ':react-native-webview')

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermesvm/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply plugin: 'com.google.gms.google-services'
// https://stackoverflow.com/questions/51839721/the-library-com-google-firebasefirebase-iid-is-being-requested-by-various-other
//com.google.gms.googleservices.GoogleServicesPlugin.config.disableVersionCheck = true

android/build.gradle

// Top-level build file where you can add configuration options common to all sub-projects/modules.


buildscript {
    ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 21
        compileSdkVersion = 28
        targetSdkVersion = 27
        supportLibVersion = "28.0.0"
        googlePlayServicesVersion = "16.1.0"
        androidMapsUtilsVersion = "0.5+"
    }
    repositories {
        google()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenLocal()
        jcenter()
        maven { url 'https://maven.fabric.io/public' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.2'
        classpath 'com.google.gms:google-services:4.3.0'
        classpath 'io.fabric.tools:gradle:1.+'
        // NOTE: Do not place your application dependencies here; they belong
        // In the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        maven { url 'https://maven.google.com' }
        maven { url "https://jitpack.io" }
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        mavenLocal()
        jcenter()
    }
}

//Force all projects to use the same build tools.
subprojects {
    afterEvaluate {project ->
        if (project.hasProperty("android")) {
            android {
                compileSdkVersion 28
                buildToolsVersion "28.0.3"
            }
        }
    }
}

subprojects {
    project.configurations.all {
        resolutionStrategy.eachDependency { details ->
            if (details.requested.group == 'com.android.support'
                    && !details.requested.name.contains('multidex') ) {
                details.useVersion "28.0.3"
            }
            if (details.requested.group == 'androidx.core'
                    && !details.requested.name.contains('androidx') ) {
                details.useVersion "1.0.1"
            }
        }
    }
}

[react-native-bot]

Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety?

👉 Click here if you want to take another look at the Bug Report issue template.

[Zloka]

Experiencing similar issues, though I'm using RN 0.60.4.

[ollydixon]

@Zloka I can't revert back from hermes now otherwise the SoLoader fails. The project is stuck now, any ideas?

[Zloka]

@ollydixon Yup, just noticed I have the same issue when I figured I'd forego using hermes for now. Application builds just fine, but crashes on launch with the following output:

2019-08-12 13:02:27.866 14055-14082/fi.mafynetti.mafyclient E/SoLoader: couldn't find DSO to load: libhermes.so
2019-08-12 13:02:27.867 14055-14082/fi.mafynetti.mafyclient E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: fi.mafynetti.mafyclient, PID: 14055
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
        at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
        at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
        at java.lang.Thread.run(Thread.java:764)

[ollydixon]

@Zloka exactly the same issue, I spent two days trying to find a fix. I'll let you know if I find one.

[Zloka]

@gaodeng Been there, done that.

@ollydixon I'll be looking for a fix as well, will let you know if I make any progress. Came across this, which might be relevant: https://github.com/facebook/hermes/issues/78#issuecomment-517810830

[Zloka]

@ollydixon This is what I've got so far:

It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn't setup at all due to enableHermes: false and there's no further error-handling in this case.

In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes.

I'm not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I'm a bit too pressed by other deadlines to further look into it right now.

Here's what my files look like right now:
android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

[ollydixon]

Here's the full error I'm getting

2019-08-12 18:32:28.058 8170-8229/com.polydelic.righter E/SoLoader: couldn't find DSO to load: libhermes.so

    --------- beginning of crash
2019-08-12 18:32:28.058 8170-8229/com.polydelic.righter E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: com.polydelic.righter, PID: 8170
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
        at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
        at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
        at java.lang.Thread.run(Thread.java:919)

I have in the onCreate in MainApplication.java

SoLoader.init(this, false);

No luck.

[Sam-Martin]

I've been having similar issues. A regex heavy task which took 3-5 seconds with hermes enabled took 40-50 seconds with hermes enabled!
With @Zloka 's suggestion I was able to disable Hermes and saved myself from tearing my hair out!

[deceive3w]

try enable debug mode, there no issue on release build

[Ekhui]

I've been having similar issues. A regex heavy task which took 3-5 seconds with hermes enabled took 40-50 seconds with hermes enabled!
With @Zloka 's suggestion I was able to disable Hermes and saved myself from tearing my hair out!

unwork for me ..

[BogdanRad]

I have the same problem :(

[baldursson]

I just upgraded to React Native 0.60.5 just to try Hermes because my Android app was really slow, but it made my app to go from slow to ultra slow. It's totally unusable with Hermes enabled.

[tal987]

any solution?

[baldursson]

Hmm, one thing I see in common with my project and @ollydixon is that we both use the Firebase. That is also the dependency I've had most trouble with compiling. Could try to remove Firebase and see if it helps. How about everyone else who experience the same issue, do you see anything else in common?

[tal987]

@baldursson did you fix the issue? its still very very slow, I'm using firebase too

[baldursson]

@tal987 I haven't had time to try Hermes without Firebase yet. Maybe I will later today, I'll keep you posted

[tal987]

@baldursson did you get to check on release? Is that slow too in release or it’s only problem with develop?

[baldursson]

@tal987 It's the same slow behavior in both release and debug builds. I just tried to remove Firebase and rebuilt my app with Hermes, and I could definitely see an improvement in performance. But, I can't say I noticed any performance boost from compiling without Hermes. It could actually still be slower

[tal987]

@baldursson so what are our options now? We can’t stay with this slow performance. Before the upgrade my performance was very fast...

[baldursson]

@tal987 I have confirmed that my app is still faster without Hermes, so my option is not to use it. It seams like there may be requirements on third party dependencies to be able to use the "boost" Hermes is supposed to achieve. Are these documented?

I haven't tried Hermes in a fresh React Native product, but I guess (hope) it works there

[tal987]

@baldursson but we need the herms for the 64bit to work. Can you still upload your app to google play without herms?

[wouterds]

Can confirm that with _the herms_ enabled our app is noticeably slower (although the startup time seems to have improved somewhat). We need to release some updates asap, but without Hermes we risk 64-bit related crashes on Android - that do not occur with Hermes enabled.

So for now we'll probably make the trade-off of a slower but at least not crashing Android app.

^{Edit: We also use a few Firebase modules if that's any relevant.}

[baldursson]

@baldursson I haven't come as far as updating the app on Google Play yet. But how is Hermes related to 64-bit support? 64-bit support was introduced in React Native 0.59, before Hermes was included

[tal987]

@baldursson the all reason I updated my react native its bc I couldn't upload the app to google play from the reason that its not support 64 bit when I tried to upgrade my app without Hermes my app crashed most of the time... and I read that I need to update to 0.60.5 and enable the hermes...

anyway I had been noticed that when I use debug mode remotely the app work fast again

[wouterds]

@tal987: Ah you're talking about debug mode? Hermes in debug mode is extremely slow (known issue). But we also notice a much slower release build, not as extreme as our debug builds though.

[baldursson]

@tal987 The app is always much faster when remote debugging because the javascript is processed by the computer you are debugging from instead of the phone

[tal987]

@baldursson @wouterds on release mode the app works much faster, still not perfect but faster...

[Zloka]

I haven't had any time to look into using Hermes lately, but that might change soon as our app is nearing release and I'd be interested in resolving this.

@baldursson To add some more context, I'm not using Firebase.

[tal987]

@baldursson @wouterds @Zloka
I did some more tests and my conclusions are that

• With enable Hermes in release mode works faster but still delayed sometimes
  
  
  
  • With disable Hermes in release mode works faster that enable Hermes but I can noticed for very small delay...
  
  
  • For devices with android version smaller than 5 the app crashed when Hermes is enable/disable (probably happens because the react native I have)
  
  
  • Im using react native 0.60.5
  
  

For now I think ill disable the Hermes, please let me know when you fix the performance issue

[dngconsulting]

Same for me here, disabled Hermes, damn slow ...

[nes123]

Great promise big disappointment. The package is just not ready to be delivered in production..

[wouterds]

Looks like there's a new release (0.2.1) of _the herms_.

Since the last release, there have been hundreds of bug fixes, performance improvements, and feature implementations gearing up for major feature milestones.

For React Native developers, the most visible changes in this release are that:

• The speed of reloads in development should have improved
• The C++ runtime library is now packaged in a separate AAR to avoid pickFirst nondeterminisms

Anyone cares to try and see if it improves the situation?

[marf]

Same problem here. With hermes enabled app is significantly slower than before.
I have tried also the newest version of Hermes Engine (0.2.1) but everything is still slow.
Any solutions?

[YGKtech]

Same issues here, updating from RN 0.59 to ~0.60 caused serious performance issues for my project. Disabling hermes helped a bit, but performance was still noticeably degraded, we just had to roll back to 0.59 for now.

iOS builds were not effected

[saudahmed]

I have faced a same problem, enabling Hermes on react native 0.60.5 has significantly lowered app performance. Tap takes 3 seconds to the response. Hermes is now such a big disappointment. Converted my project to use only this feature for quick app starts. I hope so it will be bringing some improvements in the feature. I am also using firebase in my project.

[samulon13]

I lost hours trying to improve my app performance and now im here. ☹️

[sunnylqm]

Maybe related https://github.com/facebook/hermes/issues/111#issuecomment-533313121
If you are doing a lot of string concatenate, I suggest using v8 instead of hermes at the moment

[IamMasterWayne]

Not Working~
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}

[brooklyn097]

Hermes only slow on Debug mode, on a release build it's much faster and i can reduce my app from ~40MB to 17MB.

[DISKONEKTeD]

Yeah, can confirm my app runs for the most part normal on release it seems too (just checked), but super slow on debug. Which lead me to this thread.

[roots-ai]

How to resolve this?

[roots-ai]

@brooklyn097 what version of React Native are you using? Can you please share your build.gradle?

[cisplRejjak]

I am using 0.61.1, it's very slow, please let me know how to solve this.
after completing this app, I'll never work on react native.

fuck react native

[DISKONEKTeD]

@cisplRejjak just don't enable it then? You don't technically need it. The boost bootup time isn't that big anyway, and a smaller file isn't' that big of a deal. It works fine on release it seems, just not while debugging. It's a new feature, so there are bound to be issues. React Native works fine otherwise. It's come a long way. I suggest people to just disable it while debugging and enable it when ya wanna release. Though you'll probably have to test it manually extensively

[roots-ai]

@DISKONEKTeD Issue is before making such major release such issues/concerns should be reported to the developers beforehand. It's been a while since Hermes was released, even new versions of RN have come since then.

[muhammadwafa]

Android 5.0.2
Device Galaxy A5
Release 2015
6 third party Native plugin
react-native v 0.61.2

It get launch in 8 seconds.

Wow very slow, how can I faster it

[akwebengineer26]

I have Also Performance issue with the Hermes Enabled on RN 0.60.4 on android devices,
it extremely slow on debug build and take 2-3 second on click on a static button,
Please Suugest me any Solution,
But it works fine on IOS devices

[keech]

Any updates?

[BartJanvanAssen]

@ollydixon This is what I've got so far:

It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn't setup at all due to enableHermes: false and there's no further error-handling in this case.

In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes.

I'm not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I'm a bit too pressed by other deadlines to further look into it right now.

Here's what my files look like right now:
android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

Looks like i got it working on the 0.61.5 version. i failed to fill the android/build.gradle file correctly... I did change the file but notice i had 2 places where i had to change the maven config 1st place is the allprojects => repositories. the second one is the buildscript => repositories. i forgot the first one and kept on searching for days for this to fix.. maybe i can help someone ;-)

[ollydixon]

@BartJanvanAssen thanks for the reply but we no longer do React Native (Flutter is far far superior) 😎😎

[elie222]

@ollydixon This is what I've got so far:
It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn't setup at all due to enableHermes: false and there's no further error-handling in this case.
In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes.
I'm not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I'm a bit too pressed by other deadlines to further look into it right now.
Here's what my files look like right now:
android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

Looks like i got it working on the 0.61.5 version. i failed to fill the android/build.gradle file correctly... I did change the file but notice i had 2 places where i had to change the maven config 1st place is the allprojects => repositories. the second one is the buildscript => repositories. i forgot the first one and kept on searching for days for this to fix.. maybe i can help someone ;-)

After an hour or two of bashing my head against the wall, this comment fixed my issue. Thanks! I didn't realise it was the bottom section that needed the fix.

[hramos]

Closing after several months without followup from the author. Please make sure to fill in the issue template if you decide to file a new issue.

[msqar]

I'm using Hermes in "true" in RN 0.60.6 and it works extremely fast. Now my app loads 2x faster that when Hermes was in "false". (Release mode)

[ghasemikasra39]

same here. Super slow

[baotoan1905]

Any idea how to disable hermes. I set it false but get error

[ecreeth]

@baotoan1905 if you've already built your app at least once, clean the build running this:

$ cd android && ./gradlew clean

[baotoan1905]

@baotoan1905 if you've already built your app at least once, clean the build running this:

$ cd android && ./gradlew clean

@ecreeth: Thanks for your replying. I have figured it out. It was because of that previously I got issue app crash when generating app bundle in release mode, to deal with it I had to add exclude '**/libjscexecutor.so' to section packagingOptions like bellow.

After comment it out, it works if I want to disable hermes.

[Anujmoglix]

Why react native 0.63 very slow .?

[jeffelector]

@Anujmoglix Same here !!

[AngelLlamosas]

same error in react-native 0.63.0

[Anujmoglix]

React Native team is not working properly now .