Couldn't find all resumable slots by key/index during replaying.

[jahirfiquitiva]

Link to the code that reproduces this issue

jahirfiquitiva/jahir.dev#81

To Reproduce

1. Deploy on Vercel.
2. Visit the deployment URL
3. Visit a blog post (example: https://website-bmqg5pjuv-jahirfiquitiva.vercel.app/blog/how-tailwind-grew-on-me)
4. Refresh/reload the page (cmd+R)

Current vs. Expected behavior

Current:

The website shows not found after reloading, and this error is logged in Vercel

Error: Couldn't find all resumable slots by key/index during replaying. The tree doesn't match so React will fallback to client rendering.
    at nW (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:70706)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:69570)
    at nG (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:73218)
    at nW (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:71383)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:69570)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:63588)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:67383)
    at nB (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:51051)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:51758)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:66179) {
  digest: '4172697567'
}

Shot.2024-03-12.at.15.55.54.mp4

Expected:

The website keeps loading the site normally

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 4.1.0
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.0-canary.19 // Latest available version is detected (14.2.0-canary.19).
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A

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

Not sure

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

Vercel (Deployed)

Additional context

I tested my reproduction against different canary releases, and the first one that introduced the bug was 14.2.0-canary.14, since reverting to 14.2.0-canary.13 works.

[wyattjoh]

This should get resolved by an upcoming fix over here vercel/vercel#11259, once this is merged and we release a new version, I'll update here for you to try a redeploy!

[jahirfiquitiva]

@wyattjoh Thanks for letting me know ... looking forward to it! 🙌

[mwskwong]

This should get resolved by an upcoming fix over here vercel/vercel#11259, once this is merged and we release a new version, I'll update here for you to try a redeploy!

@wyattjoh Just wanna follow up on this. May I know if there is an ETA for this?

[jahirfiquitiva]

@mwskwong I think Vercel is now using v 33.6.1 which seems to include the fix, give it a try. It is working for me now

Double check this on Vercel 👇

[mwskwong]

@mwskwong I think Vercel is now using v 33.6.1 which seems to include the fix, give it a try. It is working for me now

Double check this on Vercel 👇

Noticed. Thanks.