Tab title not updating upon changing page

[sinclairnick]

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 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: 8.5.0
    Relevant packages:
      next: 13.4.7
      eslint-config-next: 13.0.3
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3

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

App directory (appDir: true), Metadata (metadata, generateMetadata, next/head, head.js)

Link to the code that reproduces this issue or a replay of the bug

NA

To Reproduce

Update project to 13.4.8. Visit page A, browser tab title ("Page A"). Visit page B, browser tab remains "Page A"

Describe the Bug

Since upgrading to 13.4.8 the metadata title (at least, probably all meta) does not update upon changing route.

Expected Behavior

Metadata should update when changing pages.

Which browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

Vercel

[sinclairnick]

Update: It actually seems that this might be a Vercel problem. Downgrading to 13.4.7 did not fix this issue. Moreover, the next docs website seems to be suffering the same issue mentioned.

[JesseKoldewijn]

I got a project that still runs 13.4.3.canary-0 that doesn't experience this issue oddly enough. Also deployed on vercel mind you, https://github.com/ShiftCodeEU/shiftcode.eu

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for pages, template for App Router), but you can also use these templates: CodeSandbox: pages or CodeSandbox: App Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[TheEdoRan]

This is a known Next.js bug: #49409, which is now closed, but should be reopened.
The issue will be fixed by a React update. A PR with the fix was merged yesterday, but then a later commit reverted the changes.

[sinclairnick]

Thank you for mentioning that @TheEdoRan! I'm not even sure I'm using server actions at the moment, so I might be able to just scrap that config. Cheers!

[sinclairnick]

Closed in favour of #49409,

[TheEdoRan]

From what I understand, the issue shows up if you enable any experimental flags in your next.config.js, because it switches the underlying React branch to "experimental".

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