Trying to login to app.tea.xyz with my Google account. I have access to Device, Recovery Factor, as well as Recovery Password. Each tells me it’s incorrect.
I can access dashboard.web3auth.io though. Looking to see how I can log back in.
Hey Nathan! Thanks for writing in, and sorry you’re stuck. I see you’re using the Plug and Play setup, and you can log into dashboard.web3auth.io but not app.tea.xyz with your Google account. You’ve also tried your device, recovery factor, and recovery password without success.
I’ve noted these details for our support team so they can look into it. Meanwhile, could you share if you’re using the same email/Google account for both the Web3Auth dashboard and the Tea app? If possible, any screenshots or error messages from your browser console would help us narrow down the issue.
We appreciate your patience and will keep you posted once we’ve got more clarity!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours
Hello @nathanu.boeing,
Due to the use of custom authentication with Web3Auth by tea.xyz, the Google account linked to your account is different from the one used for tea. This is why you were able to access the dashboard.web3auth.io.
Web3Auth provides a non-custodial account by default, which means we are unable to recover your account from our end. To regain access to your account, please attempt to log in using your correct password and recovery factor through the same portal.
For any further assistance, I recommend reaching out to the tea team. This portal, operated by web3auth, is specifically designed for integration support and is intended to facilitate the integration of developers. Customer support is primarily handled by the respective dapps.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.