Skip to content

RangeError: Maximum call stack size exceeded, js engine: hermes when upgrading to 0.64 from 0.63.4 #31173

Closed as not planned
Closed as not planned
RangeError: Maximum call stack size exceeded, js engine: hermes when upgrading to 0.64 from 0.63.4#31173
Labels
Needs: Triage 🔍StaleThere has been a lack of activity on this issue and it may be closed soon.

Description

@aprilmintacpineda
aprilmintacpineda
opened on Mar 17, 2021

Please provide all the information requested. Issues that do not follow this format are likely to stall.

Description

I have upgraded following https://react-native-community.github.io/upgrade-helper/?from=0.63.4&to=0.64.0 but when I run on real devices, I got:

 WARN  Require cycle: node_modules/core-js/internals/microtask.js -> node_modules/core-js/internals/microtask.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/rn-fetch-blob/index.js -> node_modules/rn-fetch-blob/polyfill/index.js -> node_modules/rn-fetch-blob/polyfill/Blob.js -> node_modules/rn-fetch-blob/index.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/rn-fetch-blob/index.js -> node_modules/rn-fetch-blob/polyfill/index.js -> node_modules/rn-fetch-blob/polyfill/XMLHttpRequest.js -> node_modules/rn-fetch-blob/index.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/rn-fetch-blob/index.js -> node_modules/rn-fetch-blob/polyfill/index.js -> node_modules/rn-fetch-blob/polyfill/Fetch.js -> node_modules/rn-fetch-blob/index.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 ERROR  RangeError: Maximum call stack size exceeded, js engine: hermes
 LOG  Running "my_app" with {"rootTag":1,"initialProps":{}}
 ERROR  Invariant Violation: "my_app" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes

This happens both on iOS and Android. I am not sure what's causing the errors. I have cleaned, reinstalled everything, but the error persists.

React Native version:

Please see above

Steps To Reproduce

Still not sure as I have simply upgraded to latest version.

Expected Results

Should still work as it did with 0.63.4

Snack, code example, screenshot, or link to a repository:

N/A

Activity

  1. aprilmintacpineda
    added
    Needs: Triage 🔍
    on Mar 17, 2021

  2. oleksandr-dziuban commented on Mar 22, 2021

    @oleksandr-dziuban
    oleksandr-dziuban
    on Mar 22, 2021

    I have same when I run react native storybook on Hermes engine on iOS/Android. If I disable Hermes and rebuild app everything is OK

  3. MateusAndrade commented on Oct 13, 2021

    @MateusAndrade
    MateusAndrade
    on Oct 13, 2021
    Contributor

    Disabling the inlineRequires at metro.config, fixed this for me on Android, but I still need to test on iOS. (Testing with rn 0.66.0)

  4. halaei commented on Dec 5, 2021

    @halaei
    halaei
    on Dec 5, 2021
    Contributor

    Do you have a js file in your code that has too many exports, e.g 500 exports?

  5. liebharc commented on Oct 22, 2022

    @liebharc
    liebharc
    on Oct 22, 2022

    We just encountered this issue as well when enabling hermes with react native "0.70.3". We don't have js files with a lot of exports, but we also have warnings due to "Require cycles" in luxon and aws-amplify.

  6. aurangs7 commented on May 17, 2023

    @aurangs7
    aurangs7
    on May 17, 2023

    Has anyone found the solution? I am also getting the same error in only Android OS.

    Screenshot_1684315281

  7. liebharc commented on May 17, 2023

    @liebharc
    liebharc
    on May 17, 2023

    We got this fixed in our case by fixing the required cycles.

    More concretely the cycles were within aws-amplify and we could prevent them by never importing aws-amplify but use e.g. @aws-amplify/auth instead.

    I could imagine that the exact cause might be different for you @aurangs7 , so it might require some investigation.

  8. aurangs7 commented on May 17, 2023

    @aurangs7
    aurangs7
    on May 17, 2023

    @liebharc According to your comment I fixed all the required cycles but still getting that error, it seems related to the babel. it's been 4 days no clue why this happening. debugging it.....

  9. julianD77 commented on Sep 21, 2023

    @julianD77
    julianD77
    on Sep 21, 2023

    We had this issue on updating from RN0.66.5 to 0.72.4 and affecting Android only.

    The error we were seeing on launching the App once the bundled had loaded was:

    ERROR Warning: React instrumentation encountered an error: RangeError: Maximum call stack size exceeded

    We found that the cause was a legacy call to the Babel Polyfill package which was present only in our index.android.js

    import '@babel/polyfill';

    So we removed this line and following that we no longer hit the error on App launch.

  10. github-actions commented on Mar 20, 2024

    @github-actions
    github-actionsbot
    on Mar 20, 2024 – with GitHub Actions

    This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

  11. github-actions
    added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Mar 20, 2024

  12. github-actions commented on Mar 27, 2024

    @github-actions
    github-actionsbot
    on Mar 27, 2024 – with GitHub Actions

    This issue was closed because it has been stalled for 7 days with no activity.

  13. github-actions
    closed this as not plannedon Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Triage 🔍StaleThere has been a lack of activity on this issue and it may be closed soon.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions