It sounds like the user is getting automatically redirected to the second email account when trying to log in via the initial email. This might be caused by session cookies or cached data from the previous login.
To better assist you, could you please provide the following additional details:
Platform: Are you using Web, iOS, or Android?
Web3Auth Initialisation & Login Code Snippets: This helps us understand the exact flow and possibly identify any issues.
In the meantime, a quick solution might be to clear the browser’s cache and cookies or try logging in using an incognito/private window. This often helps reset any cached sessions or cookies.
This response was generated by the Web3Auth Bot. A member of the Web3Auth team will follow up with a detailed response to help with your query.
This is expected behaviour of our SDKs, different login providers and verifiers give different keys. Users are expected to login using the same method they logged in for the first time in order to get the same keys. You can read more about this here: https://web3auth.io/docs/troubleshooting/different-private-key
When the user logs in using his Mail, he’s incorrectly redirected to another account that is associated with a different email address. Despite using the correct email during login, the system seems to authenticate them with the credentials or session of a previously logged-in account done via Google Connect and a different mail than the previous one
What We’ve Tried:
Clearing browser cache, cookies, and OAuth sessions.
Attempting the login on different devices and browsers, with the same issue occurring.
Hey, can you please share the SDK you are using. If you are using any custom verifier, please share the details. We’ll also be requiring the login code snippet, and user’s two different email address along with the address they are getting.
Hey @JulienD we checked in the metadata, we can’t find any address associated with bubulio23@gmail.com. Please check if the session is not cached. Also, please share the Web3Auth configuration, and login code snippets to verify.
After reviewing the code, I couldn’t find any major issues except for uxMode being set as an empty string. Please make sure to set it to either “popup” or “redirect”. This is the first time we’ve come across this problem, and we were unable to replicate it locally. Here are a few steps that might help resolve it:
If the issue persists after updating the SDK, could you provide us with a jam.dev recording of the issue? If you prefer not to share it here, I can give you my Telegram so you can send it there. With the logs and network calls, we’ll be able to diagnose the issue more effectively.