8000 Hydration issue involving __gchrome_uniqueid on iPad Chrome/Edge browser · Issue #77710 · vercel/next.js · GitHub
[go: up one dir, main page]

Skip to content
Hydration issue involving __gchrome_uniqueid on iPad Chrome/Edge browser #77710
@danvim

Description

@danvim

Link to the code that reproduces this issue

https://github.com/danvim/next-gchrome-hydration-reproduction

To Reproduce

  1. Start development server
  2. Visit development server via iPad Chrome/Edge browser app.

Current vs. Expected behavior

Expected no error.

Current error message:

Hydration failed because the server rendered HTML didn't match the client...

    <Home>
      <input
-      __gchrome_uniqueid="1"
      >
    ...

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.3.0: Thu Jan  2 20:24:24 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 11
Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.3.0-canary.29 // Latest available version is detected (15.3.0-canary.29).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Output

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

iPad Chrome: 135.0.7049.53
iPad Edge: 134.3124.95
iPad Safari tested without issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    OutputRelated to the the output configuration option.linear: nextConfirmed issue that is tracked by the Next.js team.locked

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0