1 person reported
All time, since Sep 22.
router.refresh() never updates streamed pages in production builds
After router.refresh(), no _rsc fetch is initiated and the stale cached payload stays, triggered by a query string in the URL.
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/4215/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
router.refresh() never updates streamed pages in production builds.
Is this your bug?
File my report- Where
- App Router client router
- Versions
- 16.1.7 to 16.2.12
- Platforms
- Windows
- How bad
- Breaks a normal workflow. Most reports say it used to work.
Not quite your bug?
Original reports3, newest first
- router.refresh() silently no-ops on streamed pages — query string in URL triggers it on 16.2.12; all streamed pages on 16.3.5+ (production builds)On GitHub#99028
- router.refresh() silently no-ops on streamed pages — query string in URL triggers it on 16.2.12; all streamed pages on 16.3.5+ (production builds)On GitHub#99027
- router.refresh() never commits fresh RSC payload when current URL has a query string (16.1.7–16.4.0-canary.37, production builds)On GitHub#99026