Rank, 14 days: 2 on the Next.js sheet
6 people reported
All time, since Oct 6, including 5 thumbs-up on GitHub.
Stale cache mix after redeploy
“This is a problem when deploying new app versions while clients have cached resources from older builds.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/4112/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Stale RSC responses served from cache after redeploy. After deploying a new deploymentId, client navigation to an ISR page is "optimistically answered from the client cache" due to SWR headers.
Is this your bug?
File my report- Where
- client navigation
- Versions
- 16.4.0-canary.61
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Prerendered pages hard-reload1 person
Original reports1, newest first
- Changed deploymentIds and SWR caching causes to mixed fetches on clients after redeployOn GitHub#99726