OTP Login Fails – Validation Error in Web3Auth Popup

Embedded Wallets (Web3Auth)
1

:classical_building: Content from Web3Auth Community

This topic was originally posted by accounts1 on 8/26/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.

Hi team,

I’ve been testing the Web3Auth OTP service and noticed an issue.
When attempting to log in, the Web3Auth popup appears but the flow fails with the error:

Validation failed – “There was an error during your login attempt. Please try logging in again”

This happens randomly and is reproducible multiple times.

Flow:

  1. Trigger login with OTP.
  2. Web3Auth popup opens.
  3. Error message displayed (validation failed).

Impact: Login cannot be completed using OTP.

See Attachment

Screenshot 2025-08-26 at 4.39.22 PM
Screenshot 2025-08-26 at 4.39.22 PM760×1268 57.4 KB

2

Thank you for your detailed report, Arun! Here’s a summary of your issue for the support team:

Issue Summary

  • SDK/Product: Web3Auth Plug n Play (Single Factor Auth JS SDK, OTP Login)
  • Platform: Not explicitly mentioned (please specify if Web, Mobile, or other)
  • Issue: OTP login consistently fails. The Web3Auth popup opens, but the flow fails with the error:

    Validation failed – “There was an error during your login attempt. Please try logging in again”

  • Reproducibility: Happens every time, multiple attempts.
  • Impact: OTP login is completely blocked.

Additional Details Needed

To help the support team investigate further, could you please provide:

  1. SDK Version Number you are using.
  2. Code Snippet of your Web3Auth initialization and the OTP login trigger (if possible).
  3. Verifier Name (as set in your Web3Auth Dashboard).
  4. Method of Login: Are you using a custom backend to generate OTP and JWT, or only Web3Auth’s built-in OTP flow?
  5. Browser Console Screenshot (if you’re using the Web SDK) showing any errors or warnings when the failure occurs.

If you are using your own authentication (custom JWT), please also share:

  • JWKS Endpoint
  • Sample idToken (JWT) (with any sensitive info redacted)

Possible Next Steps

  • Double-check that your verifier is correctly configured in the Web3Auth Dashboard and matches what you’re passing in the code.
  • Ensure the JWT token used for login is valid, not expired, and hasn’t been reused (Web3Auth requires a fresh token for each login attempt).
  • Review the OTP Login documentation for any missing configuration steps.

Once you provide the requested details, the support team can assist you more efficiently. Thank you for your patience!

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

3

Where have you been testing it?
on our demo or an example dapp?

4

SDK Version Number: “@web3auth/react-native-sdk”: “^8.1.0” Code Snippet:

const web3auth = new Web3Auth(WebBrowser, EncryptedStorage, {
      clientId: Config.WEB3AUTH_CLIENT_ID,
      redirectUrl: Config.LOGIN_REDIRECT_URL,
      network: WEB3AUTH_NETWORK.SAPPHIRE_DEVNET,
      loginConfig: {
        google: googleLoginConfig,
        discord: discordLoginConfig,
        apple: appleLoginConfig
      },
      privateKeyProvider
    })
    await web3auth.init()
await web3auth.login({
        loginProvider: provider,
        redirectUrl: Config.LOGIN_REDIRECT_URL,
        mfaLevel: 'none',
        curve: 'secp256k1',
        extraLoginOptions
      })

Method of Login: Web3Auth’s built-in OTP flow

5

Via our chess app (React Native iOS app)