Wasteful .json file requested while middleware is enabled causes WSOD

[mlstubblefield]

Verify canary release

• I verified that the issue exists in the latest Next.js 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

const error = new Error(`Failed to load static props`)

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.

1. Browse to https://next-json-repro.vercel.app/
2. Open chrome dev tools
3. Block the "first" .json file https://next-json-repro.vercel.app/_next/data/{buildId}/index.json?something=1
4. Refresh the page
5. Block the "second" .json file https://next-json-repro.vercel.app/_next/data/{buildId}/1.json?something=1
6. Refresh
7. Get WSOD

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.

[voronianski]

we're observing the same issue after upgrading to v12.3 on our app

[ijjk]

Hi, this should be resolved by #41243 which eliminated the additional _next/data request during query hydration which is available in v12.3.2-canary.24 of Next.js. Please update and give it a try!

[mlstubblefield]

I'm evaluating this right now.

[mlstubblefield]

I've verified that I do not see any wasteful .json requests anymore! Thanks!

[ijjk]

Awesome, glad to here that resolved this, will close this out then!

[github-actions]

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.