"Unexpected fiber popped" / "An unexpected error has occurred"
See original GitHub issueBug report
Describe the bug
At least two of the NextJS examples do not work when run “out of the box”.
To Reproduce
- Follow the steps in either of these two READMEs:
- Run
npm install && npm run dev
.- React will report “Unexpected fiber popped” and “Unexpected pop” in the console.
- In the Material UI example, buttons will not demonstrate the ripple effect when clicked. In my application, the effects are more severe, leading to loss of interactivity.
- Deploy using
npx now
. Resulting application will report errors.- nextjs-with-typescript deployment
- hello-world deployment
Expected behavior
Given examples work when deployed and run.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
- OS
- Development: Ubuntu 18.04 LTS
- Deployment: Zeit Now platform
- Browser: Reproducible in Chrome and Firefox
- Version of Next.js: 9.0.6 (current
latest
)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:11 (7 by maintainers)
Top Results From Across the Web
"Unexpected fiber popped" / "An unexpected error has occurred"
Run npm install && npm run dev . React will report "Unexpected fiber popped" and "Unexpected pop" in the console. In the Material...
Read more >What is causing the warning "Unexpected Fiber popped" in my ...
1. This is a red herring warning which gets thrown when other errors occur. In my particular case, it was caused by passing...
Read more >What is error OR-RWE-30? Trying to pay my bill, but this error ...
If you had received an email from Google Fiber indicating that your service will be suspended unless you make a payment, please reach...
Read more >Error message when you open the properties of a network ...
An unexpected error occurred. Cause. This problem may occur if some registry settings are damaged. The damaged registry settings may prevent you from...
Read more >Unexpected error when trying to open workbench
Here's the Details from the Error message: An unexpected error has occurred: The type initializer for 'Ansys.Core.Expressions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is now fixed in v16.10.1.
However, it’s more like a workaround to fail gracefully because the behavior is not supported. It only accidentally worked in 16.9. We will warn in a future minor.
So we need to figure out how to address this in Next.
More context here: https://github.com/facebook/react/issues/16938#issuecomment-536207871
Hi everyone! Like the error message suggests, this may be a bug with React 16.10. I’ve opened an issue in the React project to track this: https://github.com/facebook/react/issues/16938.
Please downgrade to
react@16.9.0
andreact-dom@16.9.0
for the time being.Thanks!