"Unexpected fiber popped" / "An unexpected error has occurred"

[ryaninvents]

Bug report

Describe the bug

At least two of the NextJS examples do not work when run "out of the box".

To Reproduce

1. Follow the steps in either of these two READMEs:
   • nextjs-with-typescript
   • hello-world
2. 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.
3. 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)

[martindavid]

I got this error as well. Did some debugging, and found out it's happening on latest NextJS and React 16.10.0. If you're using 16.9.0 it works fine.

[willtrking]

Same issue here, and same resolution as @martindavid

[coolsoftwaretyler]

Same issue here. Just going through the getting started tutorial and the index page isn't clearing, rendering itself twice, and throwing errors in console.

Switching to 16.9.0 worked as well.

[Timer]

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: facebook/react#16938.

Please downgrade to react@16.9.0 and react-dom@16.9.0 for the time being.

Thanks!

[timneutkens]

Keeping this open until the PR is on stable.

[timneutkens]

Just released a new canary (will be on npm soon) https://github.com/zeit/next.js/releases/tag/v9.0.7-canary.9

[timneutkens]

Released on stable too: https://github.com/zeit/next.js/releases/tag/v9.0.7.

Note that in general we do not ship stable versions on weekends but this issue affects basically everyone getting started with Next.js / React and everyone upgrading.

[timneutkens]

I'm going to close this issue as the patch has been merged on both canary/stable and this is an upstream issue raised by @Timer here: facebook/react#16938

[acdlite]

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: facebook/react#16938 (comment)

[ryaninvents]

Thanks so much for your help identifying and fixing this! Sorry I didn't recognize that it was an upstream error; I made some incorrect assumptions based on the error message.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.