Intercepting + Dynamic Routes, Jumping the page causes a forced refresh

[zhengzhu-1m]

Description

• Intercepting + Dynamic Routes, Jumping the page causes a forced refresh vercel/next.js#62207
  When accessing dynamic interception routes, the page will be forced to refresh.

Note:

1. The bug will only be triggered in the vercel deployment environment
2. The local development environment works normally
3. If you don't use the next-intl library, it works fine

Mandatory reproduction URL

https://github.com/bosinc/next-bug

Reproduction description

Steps to reproduce:

1. https://next-bug-vert.vercel.app
2. click Page any button

Expected behaviour

Retain the multi-language mode, intercept routes will work normally, and will not force a refresh of the page

[amannn]

Possibly another instance of #255, it's unclear to me if there's anything next-intl can do here. This might be something that needs to be addressed upstream in Next.js.

[huyitan]

I have same issues on the production build.
Development work fine.

[tquann286]

Same, interception routes work fine in development mode, but it causes hard navigation on production

[huyitan]

i think this bug is caused by nextJS config build. It's rewrite route " /:locale/signal/:id" to "/NEXT_EMPTY_PARAM/(.)signal/:id", missing "locale" param. Then we use 

unstable_setRequestLocale, which throws an error when nextjs prefetch Intercepting routes.

Rewrites

┌ source: /:locale/signal/:id
└ destination: /__NEXT_EMPTY_PARAM__/(.)signal/:id

Workaround for me: remove unstable_setRequestLocale (pages will opt into dynamic rendering)

[sayandedotcom]

any update??

[github-actions]

This issue has been automatically closed because there was no recent activity and it was marked as unconfirmed. Note that issues are regularly checked and if they remain in unconfirmed state, they might miss information required to be actionable or are potentially out-of-scope. If you'd like to discuss this topic further, feel free to open a discussion instead.