You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the title has been changed once, the title does not change any more even if the page is changed again. It works fine if you don't enable the exeperimental.serverAction flag in the next.config setting.
Expected Behavior
Even if the executive.serverAction flag is enabled, metadata title should be reflected normally.
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered:
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.
Verify canary release
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:53:44 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T8103 Binaries: Node: 18.15.0 npm: 9.5.0 Yarn: 1.22.19 pnpm: 8.5.1 Relevant packages: next: 13.4.6-canary.3 eslint-config-next: 13.4.5 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
https://github.com/zenato/test-next-metadata-with-server-action
To Reproduce
Describe the Bug
After the title has been changed once, the title does not change any more even if the page is changed again. It works fine if you don't enable the
exeperimental.serverAction
flag in the next.config setting.Expected Behavior
Even if the
executive.serverAction
flag is enabled, metadata title should be reflected normally.Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: