AI & Agent Dev Bug Sandbox Back to Radar

GetInitialProps Not Re-Called When Router.Replace/Push Href Contains Query And Hash With As Also Containing Hash

When using Router.replace or Router.push with a href that includes query parameters followed by a hash (e.g. /page?test=1#hash) and an as path that also includes the same hash, the getInitialProps method is not re-invoked on subsequent query changes. This breaks data fetching for masked-query patterns where query is hidden from the browser URL but hash must remain visible.

highConfidence 75%Next.js

Origin Analysis

The router's change detection parses the href without stripping the hash correctly before extracting the query. When the href contains a trailing hash, the query parsing either returns an empty object or the hash interferes with the comparison, causing the early return condition (route unchanged and query equal) to be truthy. Consequently, Router.set is never called, so getInitialProps is skipped.

1. Add the provided component to any page.\n2. Enable Test2 (href with query and #hash, as with #hash) and run the interval.\n3. Observe that the displayed query.test does not increment and getInitialProps console.log is not printed.\n4. Enable Test1 (href with query only, no #hash) and note that getInitialProps is called on each interval and the number increments.

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 change alters URL parsing for hash-containing hrefs. Ensure that routes using hash-based navigation (e.g. /page#section) are not affected, and that dynamic routes with both query and hash still resolve correctly. Test with router.push, router.replace, and shallow routing. If issues arise, revert this block and rely on the original parseRelativeUrl implementation. Do not apply if the codebase already has a fixed parseRelativeUrl that strips hash before query parsing.

Ecosystem Topology

Latest critical and high reports

GetInitialProps Not Re-Called When Router.Replace/Push Href Contains Query And Hash With As Also Containing Hash

Origin Analysis

Fixing Code Block

Edge Case Audit

Ecosystem Topology

Agent Frameworks

Vector Databases

Toolchains

GetInitialProps Not Re-Called When Router.Replace/Push Href Contains Query And Hash With As Also Containing Hash

Origin Analysis

Fixing Code Block

Edge Case Audit

Related Intelligence

Ecosystem Topology

Agent Frameworks

Vector Databases

Toolchains