You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please see #8267.
This usually means React is an inconsistent state caused by an earlier error in your code.
If you don't see this error it might be because you have a catch block silently swallowing it.
Closing as there's been no update and it's likely related to #8267. @kevart if provide a case reproducing the issue we can look into re-opening it if its identified as a different issue.
Getting this error in IE. The build application works fine in mozilla and chrome. Moreover, the standalone express server app runs fine too in IE but the built js file using webpack and babel fails to navigate when used inside of a jsp file
@AjayU I discovered it was because I was using for(let key of something) { } loops in my code. Apparently this isn't polyfilled properly. Replacing them with .map({})'s worked. Had nothing to do with react-router - it was just that was firing the render call that caused the error to happen.
Please read this comment: #8579 (comment).
When you see this issue without a descriptive error before it, your code is swallowing errors.
I'm locking the issue because further comments will just confuse people googling it. The cause of this error is always another error that happened earlier (but that your code might have swallowed it).
A small update on this. We just released React 16 beta which shouldn’t emit cryptic errors like this one. Even if the application code swallows an error, React 16 will still print it to the console. It might be too early for you to try React 16 (since ecosystem is still preparing for it), but this error should never occur in the future after you switch to it.
Activity
gaearon commentedon Dec 15, 2016
Please see #8267.
This usually means React is an inconsistent state caused by an earlier error in your code.
If you don't see this error it might be because you have a
catchblock silently swallowing it.Related explanations: #7617 (comment), #4199 (comment).
If you’re sure this is not the problem please provide a reproducing example.
aweary commentedon Dec 20, 2016
Closing as there's been no update and it's likely related to #8267. @kevart if provide a case reproducing the issue we can look into re-opening it if its identified as a different issue.
AjayU commentedon May 31, 2017
Getting this error in IE. The build application works fine in mozilla and chrome. Moreover, the standalone express server app runs fine too in IE but the built js file using webpack and babel fails to navigate when used inside of a jsp file
bhgames commentedon Jun 6, 2017
Same here @AjayU
bhgames commentedon Jun 7, 2017
@AjayU I discovered it was because I was using for(let key of something) { } loops in my code. Apparently this isn't polyfilled properly. Replacing them with .map({})'s worked. Had nothing to do with react-router - it was just that was firing the render call that caused the error to happen.
vTrip commentedon Jun 19, 2017
this issue occurs for me specifically when using
setStategaearon commentedon Jun 19, 2017
Please read this comment: #8579 (comment).
When you see this issue without a descriptive error before it, your code is swallowing errors.
I'm locking the issue because further comments will just confuse people googling it. The cause of this error is always another error that happened earlier (but that your code might have swallowed it).
gaearon commentedon Jul 27, 2017
A small update on this. We just released React 16 beta which shouldn’t emit cryptic errors like this one. Even if the application code swallows an error, React 16 will still print it to the console. It might be too early for you to try React 16 (since ecosystem is still preparing for it), but this error should never occur in the future after you switch to it.