Loading state never finishes with nested dynamic layout using PPR

[kevva]

Link to the code that reproduces this issue

https://github.com/kevva/next-bugs/tree/routing-back

To Reproduce

1. Build and start the application (npm run build && npm run start)
2. Click the "Foo" link
3. The loading UI never finishes and thus the route is never rendered

Current vs. Expected behavior

Current behaviour

Currently, if you have a loading.js and something dynamic in a nested layout.js (like a headers() call), the loading state will never finish if you navigate to the route with the nested layout using PPR.

Expected behaviour

The route renders correctly.

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 21.4.0
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.36
  eslint-config-next: 14.0.5-canary.36
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

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

App Router

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

next start (local)

Additional context

The latest working canary release I could test this is in was 14.0.5-canary.19 due to issues introduced in #59569. However, it works in that release so this must've been introduced after that.

[JoeyKhd]

Experiencing this as well at the moment

[MattJustMatt]

Another variant of this issue (maybe the same root cause).

• If I navigate from a dynamic route to another dynamic route with PPR enabled loading never finishes
• If I navigate from a PPR route to a dynamic route, the dynamic route does load but the loading state is never displayed (feels clunky)

[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!

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.