- 
                Notifications
    You must be signed in to change notification settings 
- Fork 5.4k
Closed
Labels
Sev2-normalNormal severity; minor loss of service or inconvenience.Normal severity; minor loss of service or inconvenience.regression-mainRegression bug that was found on main branch, but not yet present in productionRegression bug that was found on main branch, but not yet present in productionteam-web3authWeb3Auth teamWeb3Auth teamtype-bugSomething isn't workingSomething isn't working
Description
Describe the bug
When the user closes the browser application and reopens it, the system incorrectly shows an “Invalid token” error during the Rehydration process. This occurs even though the session should still be valid and restored automatically.
Expected behavior
The session should rehydrate successfully without showing any error. The user should remain logged in if the token is still valid.
Screenshots/Recordings
Screen_Recording_2025-10-29_at_12.05.29_PM.mov
Steps to reproduce
See the video
Error messages or log output
Detection stage
On main branch
Version
13.7.0
Build type
Beta
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
Metadata
Metadata
Assignees
Labels
Sev2-normalNormal severity; minor loss of service or inconvenience.Normal severity; minor loss of service or inconvenience.regression-mainRegression bug that was found on main branch, but not yet present in productionRegression bug that was found on main branch, but not yet present in productionteam-web3authWeb3Auth teamWeb3Auth teamtype-bugSomething isn't workingSomething isn't working
Type
Projects
Status
To be triaged