Verification of "Recover Password" problem of PROTOCOL TEA


When I log in with my email in TEA PROTOCOL, I only get 3 options and I am missing the “Recover Password” option
Please help me to solve this problem.

Hi Tecno Rex! :star2:

Thank you for reaching out. It seems like you’re using the Plug and Play SDK and are facing a missing “Recover Password” option in the TEA PROTOCOL login.

To better assist you, could you please provide:

  • The version number of the Plug and Play SDK you’re using.
  • Any relevant code snippets related to your Web3Auth initialization and login.
  • Mention if this is related to custom authentication or providers.

The issue might be related to how the Web3Auth modal is configured. You can explore the Web3Auth Documentation for more details on customizing the authentication options.

Let me know if there’s anything else you’d like to discuss! :blush:

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

It’s same problem brother … you understand how to solve this problem

Hello brother, I still haven’t got it fixed. Let’s wait to see what answer we get :C

Hey @tecnorexpro03,

As far as we understand, TEA Protocol integrated Web3Auth and made password-based recovery (Recovery Password) available only in a later phase of their integration. If you had created your account or enabled MFA before this feature was made mandatory, your account may not have set up the recovery password at that time — which is why you’re not seeing that option now.

Unfortunately, if none of the MFA methods (Device, Recovery Phrase, or Recovery Password) are working or available to you, and you’ve lost access to the device where the key share was stored, there’s no way for us or the dApp team to reset or recover it — this is by design, since Web3Auth is non-custodial and never stores your keys or recovery factors.

The only path forward in this case would be to create a new wallet account.