Hi @hasty lake. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Error: Failed to fetch RSC payload. Falling back to browser navigation
tender fieldBOT
The error "Failed to fetch RSC payload. Falling back to browser navigation" is a known issue in Next.js and has been reported in several open GitHub issues. This error typically occurs when Next.js tries to fetch a page using the fetch API and fails, causing it to fall back to using browser navigation.
There are several potential causes for this issue:
-
It could be related to the handling of external links. In this case, Next.js should either automatically identify external links or provide a way for them to be identified/handled differently, which would then not attempt to fetch and just allow the server to respond with a redirect header (source (https://github.com/vercel/next.js/issues/53813)).
-
It could be related to search parameters with Unicode characters, causing the fetching of RSC payload to fail (source (https://github.com/vercel/next.js/issues/48728)).
-
It could be related to prefetching, where the prefetching of a page fails to fetch the RSC payload (source (https://github.com/vercel/next.js/issues/48677)).
-
It could be related to navigating back to a page using the browser's back button, after the page has been revalidated (source (https://github.com/vercel/next.js/issues/61336)).
-
It could be related to the handling of blob URLs, where passing a blob URL to
Linkfromnext/Linkwas causing the error (source (https://github.com/vercel/next.js/issues/48677)).
Unfortunately, there isn't a one-size-fits-all solution to this issue as it depends on the specific circumstances of your application. However, some users have reported temporary workarounds such as clearing the cache or disabling the prefetch flag of the Link component (source (https://github.com/vercel/next.js/issues/60549), source (https://github.com/vercel/next.js/issues/48677)).