[Archive] Login fails after setting the 2 factor authentication using social recovery method

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by khemraj on 7/16/2024.
This content has been migrated from our previous community forum to preserve valuable discussions.

Whenever user tries a new device, login window asks to use the recovery method. After selecting the google as social recovery method and after successful google login - user is getting redirected with empty idToken - so login fails. On 2nd attempt it works fine. What is the issue here?

  • SDK Version(package.json):
    “@web3auth/base”: “^5.1.0”,
    “@web3auth/ethereum-provider”: “^6.1.1”,
    “@web3auth/modal”: “^5.1.1”,
    “@web3auth/no-modal”: “^7.3.2”,
    “@web3auth/openlogin-adapter”: “^6.1.1”,
    “@web3modal/ethereum”: “2.1.1”,
    “@web3modal/react”: “2.1.1”,
  • Platform: Chrome
2

Hey, I see you are using very old versions of the Web3Auth SDKs. The first step would be to upgrade the SDKs to the latest version, and check if it resolves the issue. Also, the version you are using are going to be deprecated by 31st July. Please read the full announcement.