-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
Wasteful .json file requested while middleware is enabled causes WSOD #40611
Comments
we're observing the same issue after upgrading to v12.3 on our app |
Hi, this should be resolved by #41243 which eliminated the additional |
I'm evaluating this right now. |
I've verified that I do not see any wasteful .json requests anymore! Thanks! |
Awesome, glad to here that resolved this, will close this out then! |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 16.15.1
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 12.3.1-canary.2
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0
What browser are you using? (if relevant)
not relevant
How are you deploying your application? (if relevant)
vercel
Describe the Bug
This is somewhat related to this issue #40583
But if the application is deployed, the .json files will 404 in the event of navigation or use of the back button.
If enough of them 404, you'll get a white screen of death.
When we see this happen to our customers (via log rocket), we see this error message
next.js/packages/next/shared/lib/router/router.ts
Line 715 in 545ea5e
Expected Behavior
No white screen of death, but preferably if the wasteful .json files can go away that'd be nice too (which relates back to my first report).
Link to reproduction
https://next-json-repro.vercel.app/ and https://github.com/mlstubblefield/next-json-repro
To Reproduce
To simulate a deployment you have to be a little clever, but using Chrome developer tools you can block the two files that would normally be requested.
This is happening us when we deploy our app to real customers. They're getting WSODs when the utilize the back button or return on a somewhat stale session.This is happening us when we deploy our app to real customers. They're getting WSODs when the utilize the back button or return on a somewhat stale session.
The text was updated successfully, but these errors were encountered: