Navigating to the same page in a different locale with a hash does not update props

[destruc7i0n]

What version of Next.js are you using?

10.0.9

What version of Node.js are you using?

14.16.0

What browser are you using?

Chromium Edge

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

For a language switcher, I only change the locale for the page and nothing in the url. Using router.push with the Url object representing the current page and setting hash to the hash of the current page, there is only a hashChangeStart and subsequent hashChangeComplete event and not a props update.

Expected Behavior

There should be a page update (for fetching new translations etc.) while keeping the hash in the url.

To Reproduce

https://codesandbox.io/s/heuristic-blackburn-jpu7g

In the demo, go the "About Page" or the "Post Page". Click on the "Change Language" button. The value of the locale in useRouter updates while the props do not. There are also the hashChange events in the console.
Setting router.push to not set the hash (in components/demo) causes a props update as expected but removes the hash.

[sashakrauzer]

I have a same problem.

[gurkerl83]

@destruc7i0n The changes made in the merge request for this issue prevent the firing of the hashChangeStart event when the hash changes, please reopen for further investigation. See #26853

[gurkerl83]

@destruc7i0n It seems a few issues got reported the last couple of days that props are not being updated correctly.

With dynamic routes like you described in your reproduction.

#26944
#26508
#26602

I certainly have a proper i18n setup in my project, so locale should not be undefined, as you replied
#26853 (comment)

My project uses dynamic routes. I set the hash using the NextJs Link component like here.

https://github.com/project-millipede/millipede-docs/blob/c864e75926f1ef2ab7400dc91e931eab3224f751/packages/page/layout/src/components/toc/TocLink.tsx#L54-L59

Thx!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.