[Archive] What could be causing "Session Likely Expired" error?

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by githubdiscussions on 10/25/2022.
This content has been migrated from our previous community forum to preserve valuable discussions.

I'm seeing this error that says "Session likely expired" and not sure why. This seems to appear as soon as web3auth.init is completed. I'm still able to call await web3auth?.connectTo() and login successfully even when the error does appear. Any concerns here? This is happening on testnet haven't tested on cyan or mainnet yet.

    "@web3auth/openlogin-adapter": "^2.1.3",
    "@web3auth/web3auth": "^2.1.3",

image



Originally posted by: tantommy

Check the discussion at: https://github.com/orgs/Web3Auth/discussions/760
2

Hello, this is just a warning, you can ignore it. SDK first creates a new session using a random session id and then checks if the same sessionId already exists, if it doesn't exist it shows a warning which can be ignored. It should not block user's login.



Originally posted by: himanshuchawla009