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

Metadata does not work after one page move when the serverActions option is true. #49679

Closed
1 task done
woo3145 opened this issue May 11, 2023 · 5 comments
Closed
1 task done
Labels
bug Issue was opened via the bug report template.

Comments

@woo3145
Copy link

woo3145 commented May 11, 2023

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.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.6.0
      npm: 8.15.0
      Yarn: N/A
      pnpm: 8.5.0
    Relevant packages:
      next: 13.4.2-canary.5
      eslint-config-next: 13.4.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

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

https://github.com/woo3145/bug-next-server-actions-metadata-not-working

To Reproduce

2023-05-12.4.41.14-1.mov

Describe the Bug

same as title

Expected Behavior

Metadata should work properly.

Which browser are you using? (if relevant)

chrome 113.0.5672.92(arm64)

How are you deploying your application? (if relevant)

No response

@woo3145 woo3145 added the bug Issue was opened via the bug report template. label May 11, 2023
@JesseKoldewijn
Copy link
Contributor

JesseKoldewijn commented May 11, 2023

I ended up being able to reproduce this issue on the latest canary release funny enough. Not sure which release was the last where this worked as expected but it seems like sort of a related issue to the next-i18n issue where softroutes break curtain flows like the metadata and the i18n instance.

i18n issue: #49655
Current behavior: i18n instance gets killed on softroutes.

Metadata issue: data isn't consistently read on softroutes but do get updated on hard routes and refreshes.

@woo3145
Copy link
Author

woo3145 commented May 11, 2023

I ended up being able to reproduce this issue on the latest canary release funny enough. Not sure which release was the last where this worked as expected but it seems like sort of a related issue to the next-i18n issue where softroutes break curtain flows like the metadata and the i18n instance.

i18n issue: #49655 Current behavior: i18n instance gets killed on softroutes.

Metadata issue: data isn't consistently read on softroutes but do get updated on hard routes and refreshes.

Thanks I tested the hard router based on your comments. Hard routers seem to have the same problem. Updated my github and vercel distros.

@TheEdoRan
Copy link

Duplicate of #49409

@shuding
Copy link
Member

shuding commented May 19, 2023

Going to closing this one and track in #49409, thanks!

@shuding shuding closed this as completed May 19, 2023
@github-actions
Copy link
Contributor

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 locked as resolved and limited conversation to collaborators Jun 19, 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.
Projects
None yet
Development

No branches or pull requests

4 participants