Custom Error pages are rendered instead of passing 404 or 500 as params to page with dynamic path

[akshitkrnagpal]

Link to the code that reproduces this issue

https://github.com/akshitkrnagpal/nextjs-custom-errors-bug

To Reproduce

1. Create file [id]/page.tsx in app directory.

const Page = ({ params }: { params: { id: string } }) => {
  return <div>Page {params.id}</div>;
};

export default Page;

2. Visit /500 or /404

Current vs. Expected behavior

Current Behaviour

When running locally

1. Visting /404 renders "Page 404".

2. Visting /500 renders "Page 500".

When deployed to Vercel

1. Visting /404 renders 404 page.

2. Visting /500 renders 500 page.

Expected Behaviour

When deployed to Vercel also page should be rendered. (like local)

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.0.0: Thu Aug 17 21:23:05 PDT 2023; root:xnu-10002.1.11~3/RELEASE_ARM64_T6000
Binaries:
  Node: 18.16.1
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 8.7.5
Relevant Packages:
  next: 13.5.3-canary.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

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

App Router

Additional context

I have a deployed version to https://nextjs-custom-errors-bug.vercel.app.

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

[akshitkrnagpal]

Issue still exists in next@15.3.0-canary.19.