next.js: Failed to fetch RSC payload for Falling back to browser navigation. TypeError: Failed to fetch
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/github/vercel/next.js/tree/canary/examples/reproduction-template
To Reproduce
Seems like this can be reproduced on any nextjs site but used nextjs.org as an example: 1 Go to https://nextjs.org/docs 2 Open console and click “preserve log” 3 Spam cmd+shift+r 4 Look at error messages
Current vs. Expected behavior
This issue seem to exist in all nextjs sites and it’s causing cpu spikes in the server (at least for us)
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:59:33 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8112
Binaries:
Node: 20.1.0
npm: 9.6.4
Yarn: 1.22.19
pnpm: N/A
Relevant Packages:
next: 14.0.4
eslint-config-next: 13.0.0
react: 18.2.0
react-dom: 18.2.0
typescript: N/A
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
Other (Deployed)
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 15
- Comments: 18 (2 by maintainers)
Commits related to this issue
- Ignore fetch errors after hard navigation When the user reloads the page or navigates away while RSC fetch requests are still in flight – most notably background prefetches – we currently log the fol... — committed to vercel/next.js by unstubbable 2 years ago
- Ignore RSC fetch errors after hard navigation (#73975) When the user reloads the page or navigates away while RSC fetch requests are still in flight – most notably background prefetches – we curren... — committed to eps1lon/next.js by unstubbable 2 years ago
Any other solutions other then clearing cache does anyone found yet ? Thank you.
We’re seeing a lot of these issues in Sentry, this console message is always followed by an error saying:
TypeError: Cannot read properties of undefined (reading 'call')Getting this error with Next 15 Canary 190 (may have been prior too, but I’ve just started building the project for prod). I am using the custom
CacheHandlerfrom@neshca/cache-handler. However this was an intermittent issue when using next’s built-in caching too. Setting every use of<Link prefetch={false} ...has made the effect less pronounced, but there are still pages where the page enters a loading loop withFailed to fetch RSC payload for http://localhost:3002/<some-pathname> Falling back to browser navigation. TypeError: Failed to fetchprinted to the console repeatedly.Getting thousands of these errors from iOS users. Is this an RSC thing? NextJS thing?