Example in Beyond Fireship video feature Server Actions does not run the loading state

[TranscendentalRide]

Verify canary release

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

Provide environment information

Working info
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.7.0
      npm: 9.6.0
      Yarn: N/A
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.1
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0


Not working
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.7.0
      npm: 9.6.0
      Yarn: N/A
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.4
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0

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

No response

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

https://fireship.io/courses/nextjs/adv-actions/

To Reproduce

Clicking the "save and continue" shown in the video works in 13.4.1 and not in 13.4.4

Describe the Bug

The example in this Beyond Fireship video featuring Server Actions

https://www.youtube.com/watch?v=O94ESaJtHtM

works in Next 13.4.1 but not any version after including the current Canary as of this writing.

Expected Behavior

To work as shown in video

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!