Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navigating away from not-found page via Links doesn't work #49812

Closed
1 task done
codinginflow opened this issue May 15, 2023 · 12 comments
Closed
1 task done

Navigating away from not-found page via Links doesn't work #49812

codinginflow opened this issue May 15, 2023 · 12 comments
Labels
bug Issue was opened via the bug report template. locked

Comments

@codinginflow
Copy link

codinginflow commented May 15, 2023

Verify canary release

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

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.2
      eslint-config-next: 13.4.2
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.2

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

No response

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/priceless-allen-nlrrrn?file=%2Fapp%2Fnot-found.tsx

To Reproduce

  1. Set up a custom not-found.jsx/tsx page that includes next/Links for navigation (e.g. a nav bar)
  2. Navigate to a route doesn't exist (inside the app directory)
  3. Try to navigate away from the not-found page by clicking a next/Link -> it doesn't work

Describe the Bug

We can't navigate away from the not-found (404) page. When we click a link, the URL in the browser bar changes, but the not-found page is still shown.

Expected Behavior

We should navigate to the correct page.

Which browser are you using? (if relevant)

Google Chrome

How are you deploying your application? (if relevant)

npm run build + start locally

@codinginflow codinginflow added the bug Issue was opened via the bug report template. label May 15, 2023
@masterkain
Copy link

same issue

@codinginflow
Copy link
Author

same issue

Good to hear that I'm not the only one. Please upvote the issue to get more attention on this 👍

@aapav01
Copy link

aapav01 commented May 15, 2023

Im also having the same issue even tried using normal a tag and its still not rendering the new page(the link page)

@valentingavran
Copy link

valentingavran commented May 15, 2023

I accidentally created an issue (#49823) about the same bug. You can find a more detailed description of the problem there, with an example repository that reproduces the problem.

@jetsstarplus
Copy link

I've also been experiencing the same issue, was forced to use normal anchor tags

@TheEdoRan
Copy link

Duplicate of #47862

@leonace924
Copy link

Link doesn't work on nextjs v13.4.3 even though I saw it's fixed...

It doesn't redirect to homepage, only slug is changed

@qpavy
Copy link

qpavy commented May 19, 2023

I think it is merge with canary version did you try with canary version ?

@RamFarid
Copy link

Link doesn't work on nextjs v13.4.3 even though I saw it's fixed...

It doesn't redirect to homepage, only slug is changed

The same happen with me!

@RyelBanfield
Copy link

Using a normal anchor tag until this works

@timneutkens
Copy link
Member

This issue was fixed in #49855. Thanks for the report!

Duplicate of #47862

@github-actions
Copy link
Contributor

github-actions bot commented Aug 3, 2023

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.

@github-actions github-actions bot added the locked label Aug 3, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked
Projects
None yet
Development

No branches or pull requests