AI & Agent Dev Bug Sandbox Back to Radar

Router State Header Parse Failure On Soft Navigation After Upgrade To V16.2 With Dynamic Rendering

When a client that has loaded a page from Next.js 16.1 performs a soft navigation (Link click) after the server is upgraded to 16.2, the old-format router state header sent by the client cannot be parsed by the new server, causing a 500 error. The issue only occurs when dynamic rendering is involved (e.g., using cookies()) because such requests always hit the server for RSC payload validation.

highConfidence 72%Next.js Affected V16.2.0 Affected V16.2.1-Canary.45

Origin Analysis

The encoding or serialization format of the `x-nextjs-router-state-tree` header changed between Next.js 16.1 and 16.2. The server-side parser in 16.2 attempts to parse the header using the new format and throws `The router state header was sent but could not be parsed` when it receives a stale 16.1 header. The parser lacks a fallback for older clients, so a soft navigation during a deployment window triggers a server error instead of degrading gracefully.

1. Clone https://github.com/abdonrd/nextjs-header-could-not-be-parsed 2. Install dependencies with Next.js 16.1.x, run `npm run build && npm start` 3. Open http://localhost:3000 in a browser 4. Upgrade to Next.js 16.2.x (`npm install next@canary`), rebuild, and restart the server 5. Without refreshing the browser, click the 'About' navigation link 6. Observe the 500 error: 'The router state header was sent but could not be parsed.'

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This fix degrades soft navigation to a full page reload for clients with a stale router state header, which may lose client-side UI state and cause a visible page refresh. It masks any underlying corruption in the header rather than fixing the format mismatch. Backward-compatible parsing should be implemented for true soft navigation support. Rollback: if this patch causes unexpected full reloads, revert to a server version matching the client's header format or force clients to reload once via a version bump.