When the user clears the cookies or disconnect the wallet, the server can't detect correctly if both wallets are connected, and jwt is present, so the server returns a different version than the clients (who can properly check if the wallet is connected)
This hydratation error happens on the navbar with the login button.
Example 1:
- User logins correctly (connect + sign)
- User deletes the cookies
- User refreshes the page > Hydratation issue because the server thinks that the user is not connected because there is no jwt
Example 2:
- User logins correctly (connect + sign)
- User disconnects the wallet
- User refreshes the page > Hydratation issue because the server thinks that the user is connected because the jwt is valid
When the user clears the cookies or disconnect the wallet, the server can't detect correctly if both wallets are connected, and jwt is present, so the server returns a different version than the clients (who can properly check if the wallet is connected)
This hydratation error happens on the navbar with the login button.
Example 1:
Example 2: