T
TanStack•9mo ago
xenial-black

HTML didn't match the client

Hi guys. Have you experienced this error before? A tree hydrated but some attributes of the server rendered HTML didn't match the client properties. This won't be patched up. This can happen if a SSR-ed Client Component used:
4 Replies
genetic-orange
genetic-orange•9mo ago
can be a lot of things we need more details, ideally a minimal complete example
xenial-black
xenial-blackOP•9mo ago
I fixed it now. This is a usual meta-framework error caused by the Apple password manager Chrome extension. Haha.
genetic-orange
genetic-orange•9mo ago
oh wow
xenial-black
xenial-blackOP•9mo ago
Go incognito. It will disappear. Error looks like this: 
A tree hydrated but some attributes of the server rendered HTML didn't match the client properties. This won't be patched up. This can happen if a SSR-ed Client Component used:

- A server/client branch `if (typeof window !== 'undefined')`.
- Variable input such as `Date.now()` or `Math.random()` which changes each time it's called.
- Date formatting in a user's locale which doesn't match the server.
- External changing data without sending a snapshot of it along with the HTML.
- Invalid HTML tag nesting.
A tree hydrated but some attributes of the server rendered HTML didn't match the client properties. This won't be patched up. This can happen if a SSR-ed Client Component used:

- A server/client branch `if (typeof window !== 'undefined')`.
- Variable input such as `Date.now()` or `Math.random()` which changes each time it's called.
- Date formatting in a user's locale which doesn't match the server.
- External changing data without sending a snapshot of it along with the HTML.
- Invalid HTML tag nesting.

Did you find this page helpful?