Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Maximum call stack size exceeded if HMR not active #14614

Closed
luchillo17 opened this issue Jun 19, 2017 · 2 comments
Closed

[Bug] Maximum call stack size exceeded if HMR not active #14614

luchillo17 opened this issue Jun 19, 2017 · 2 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@luchillo17
Copy link

Description

I created an app with CRNA, then ejected to normal RNA, then followed this tutorial to allow typescript code, at the end when running in device the app returned error Maximum call stack exceeded, however it fixes when i activate HMR from the app menu.

Reproduction Steps

I've linked a repo, just clone, install deps, start React-Native packager and run in Android with react-native run-android, the red screen with error should show, if nothing shows (not even text) then close the app in emulator and open again.

Lastly to make that red screen go away, open the app menu with Ctrl + M (in linux, idk how to in OSX), and activate HMR.

Actual screen of error:
image

Sample Code

Repo mentioned above: https://github.com/luchillo17/react-native-error-repo

Additional Information

  • React Native version: react-native@0.44.3
  • React version: react@16.0.0-alpha.6
  • Platform: Android (don't have Mac for test in IOS)
  • Development Operating System: Ubuntu 17.04
  • Build tools: I've installed most android sdk versions:
    image
@ValentinBlokhin
Copy link

+1

@hramos
Copy link
Contributor

hramos commented Aug 31, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Aug 31, 2017
@hramos hramos closed this as completed Aug 31, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Aug 31, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants