V16.2.1-Canary.45

Name: V16.2.1-Canary.45 bug reports
Creator: AI & Agent Dev Bug Sandbox

Reports that share this version, grouped in one feed.

Similar Reports

high72%

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.

V16.2.0 V16.2.1-Canary.45 Next.js

high82%

Router state header parsing fails after upgrade from 16.1 to 16.2 on dynamic routes

Soft navigation breaks with a 500 error when a client that loaded a 16.1 app navigates after a server upgrade to 16.2, because the router state header format/encoding changed and the new server parser throws instead of falling back to a full navigation. The issue only occurs when at least one layout or page is dynamically rendered (e.g., uses cookies()).

V16.2.0 V16.2.1-Canary.45 Next.js

high78%

[v16.2+] Router state header was sent but could not be parsed on soft navigation with dynamic rendering

After upgrading from Next.js 16.1 to 16.2, clients holding stale router state from the previous deployment send a header that the newer server cannot parse, causing a 500 error and failed soft navigation on dynamic routes/pages.

V16.2.0 V16.2.1-Canary.45 Next.js