null is not an object (evaluating 't.parallelRoutes.get') #67730
Labels
bug
Issue was opened via the bug report template.
Navigation
Related to Next.js linking (e.g., <Link>) and navigation.
Runtime
Related to Node.js or Edge Runtime with Next.js.
Link to the code that reproduces this issue
https://github.com/JClackett/next-reproduction-app
To Reproduce
So, I literally have no idea how to reproduce this consistently yet, but will keep trying.
I'm getting this error semi-often in production only and only sometimes for certain users, most of the time it's working.
Looking at the stack trace (which is limited), it's due to some call to a
<cache>.parallelRoutes.get
. Searching the next code base with https://github.com/search?q=repo%3Avercel%2Fnext.js%20parallelRoutes.get&type=codeshows all the times this method is called.
It seems that one of the cache objects is null for me? How would I go about creating a repro for that. Or does anyone have any idea why this cache object would be null in the first place. The page this is erroring on is nothing special, it's just a async server component that fetches data and renders few components, one being a client component, so I dont see (yet) how this is something strange with my setup. Only thing of note is that im using react suspense to handle the fallback because the loading.tsx pages dont work as id like (they dont trigger on search param changes).
Current vs. Expected behavior
Doesn't crash
Provide environment information
Which area(s) are affected? (Select all that apply)
Navigation, Runtime
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
Only in production on vercel
The text was updated successfully, but these errors were encountered: