Can't log in after entering OTP

Embedded Wallets (Web3Auth)
2

Hi Felix — I’m on the MetaMask / Web3Auth team. Thanks for the detailed report — you’ve given the key info (React/Next.js, @web3auth/modal v10.9.1, @web3auth/auth v10.8.0). This is a known symptom (OTP validates but loops back) — quick checklist and next steps so we can isolate it fast:

  1. Environment: try Incognito / another browser and clear site data for your app domain (cookies/localStorage). Adblockers or strict cookie settings can break device detection.
  2. Clock: confirm the client device time is auto‑synced (TOTP codes are time‑sensitive).
  3. Network: open DevTools → Network and look for requests to Web3Auth endpoints during the OTP flow. Any non-200/4xx/5xx or CORS failures? Save a HAR if possible.
  4. SDK versions: ensure all @web3auth/* packages are compatible. modal pulls no-modal v10.9.0 — try aligning/upgrading @web3auth/auth/modal/no-modal to the same latest patch if possible.
  5. SSR/Next.js: confirm your Web3Auth init runs only client-side (if (typeof window !== ‘undefined’) { … }).
  6. Enable verbose SDK logs and retry to capture more console detail:
    const web3auth = new Web3Auth({ clientId: “…”, chainConfig: {…}, enableLogging: true });

If you’ve tried those and it still fails, please attach: (a) full console logs (not just screenshot), (b) Network HAR around the OTP validation, and (c) confirm whether this reproduces on another device/browser. If you can’t share those now, say so and we’ll escalate — engineering will investigate further once we have the HAR + logs.

I searched our Embedded Wallets docs and troubleshooting guides while preparing this — nothing shows a one-line fix beyond the checks above, so if the problem persists we’ll pass it to the backend/engineering team to debug the OTP/device-detection flow. Thanks — we’ll get this sorted.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours