Bug: Hydration issue involving __gchrome_uniqueid on iPad Chrome/Edge browser

[danvim]

Recreating this issue from https://github.com/vercel/next.js/issues/77710 as Next team mentioned this relates more to React's hydration behavior.

React version: 19.1.0 iPad Chrome: 135.0.7049.53 iPad Edge: 134.3124.95 iPad Safari tested without issues.

Steps To Reproduce

See reproduction

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

Link to code example: https://github.com/danvim/next-gchrome-hydration-reproduction

The current behavior

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

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

The expected behavior

Expected no error.

[preeti17x]

Hi! 👋 I'd love to take a look into this issue. I'll try to reproduce the bug and investigate further.

[santiagocento]

Hi, I'm having the same issue on chrome both from iPad and iPhone. Has anyone solved this in any way?

[shleeable]

I believe this issue is the same as https://github.com/vercel/next.js/issues/77710 I am having this issue but it only alerts on chrome... according to this issue resolution, it's a "false alarm in prod"

[github-actions[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[danvim]

bump