The presence of a warning and error in the console in the App Routing example.

[AnastasiiaRamona]

Description

The problem was found in the App Routing example.

When you go to the not-found page, you may see a warning: "No default component was found for a parallel route rendered on this page. Falling back to nearest Not Found boundary" and also an error: "GET http://localhost:3000/en/shshf 404 (Not Found)" in the console.

Screenshots:

The problems are not removed with the proposed default.js file. I have the same issue with my App Router project.

Verifications

• [X] I've verified that the problem I'm experiencing isn't covered in the docs.
• [X] I've searched for similar, existing issues on GitHub and Stack Overflow.
• [X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL

App Router

Reproduction description

Steps to reproduce:

1. Open a working example (npm run dev)
2. Type in the URL of the browser the URL of the page that does not exist
3. See error: GET http://localhost:3000/en/shshf 404 (Not Found)
4. See warning: No default component was found for a parallel route rendered on this page. Falling back to nearest NotFound boundary.

Expected behaviour

No warnings or errors in the console.

[amannn]

Thanks for the report! This appears to be a bug on the Next.js side as the example doesn't use parallel routes at all.

I haven't traced this further, as the 404 page seems to be working as expected. If you like, you can raise an issue on the Next.js issue tracker—I'd be happy to follow along!