Multizones (with async rewrites()) not working as expected

[ezeamin]

Link to the code that reproduces this issue

https://github.com/ezeamin/next-multizones-test

To Reproduce

1. Install dependencies on global scope and inside each app folder with pnpm or npm
2. Run pnpm dev on the root folder
3. Go to http://localhost:3000
4. Click on "To App 3001" link
5. This will compile the app on port 3001 (see console log), but won't render it until the page gets refreshed
6. The same happens when travelling back to home

Current vs. Expected behavior

Current:
The app recognizes the rewrite rule and redirects the route to the correct destination, but won't update the content of the page until it's refreshed. The same happens when travelling back to home.

Expected:
To show the content of the other app when changing the path.

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 21.2.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.10
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

pnpm is 8.10.5

Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

Additional context

This is not a new issue. From version 13 onwards it's been happening. I have not used NextJs before, so I can't tell if this is something recent or not.

This has been tested locally only, no deployed version. Running on Windows 11 and Chrome, latest version. Firefox behaves the same.

This has been tested with and without the --turbo flag. I've tried removing node_modules and .next folders from both apps, but no change.

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!