[NEXT-834] Regression in 13.2: 404 on pages with dynamic routes and i18n enabled

[jleclanche]

Verify canary release

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

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 16.19.1
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.4-canary.4
      eslint-config-next: 13.2.3
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

Link to the code that reproduces this issue

To Reproduce

Use dynamic routing for URLs such as /test/[uuid]/page.tsx

Describe the Bug

This broke specifically in next@13.1.7-canary.14, as it was still working in next@13.1.7-canary.13. Currently reviewing all the commits between the two versions to see what might be causing it.

I get nothing in the logs, very mysterious.

Expected Behavior

No 404

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-834

[jleclanche]

• Removing use of params in the function doesn't fix it
• Even a simple <div>Test</div> reproduces it

const Page = async () => {
	return <div>Test</div>;
};

export default Page;

[jleclanche]

Suspicious commits:

• 74ca99c @wyattjoh @ijjk
• cdf1d52 (changes in packages/next/src/client/components/navigation.ts) @wyattjoh

[mdrayer]

Hmm, I am using the latest 13.2.4-canary.4 and my dynamic pages (/app/foo/[slug]/page.tsx) are responding just fine (200 status). Any other instructions here to get the unwanted 404 behavior to happen?

[jleclanche]

Currently trying to reduce my use case, because yeah I suspect there's more to it.

[jleclanche]

The following is needed in next.config.js to trigger it

	i18n: {
		locales: ["en"],
		defaultLocale: "en",
	},

[jleclanche]

Minimal reproduction case.

nextjs-issue-46841.zip

Access /test/123. It should not be a 404.

• npm install next@13.1.7-canary.13 will not reproduce
• npm install next@13.1.7-canary.14 will reproduce
• Removing the i18n block from the config will not reproduce in either case

[pveyes]

this is probably duplicate of #46814

[kulikov92]

I have the same problem, dynamic routes do not work with non-default locale

[jleclanche]

@pveyes yeah seems like it is.

[kespinola]

Confirming route segments don't work when have i18n enabled in next.config. for next@13.2.x

[github-actions]

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