Few users are facing infinite loader on web3auth login mostly on mobile chrome browser and sometimes on desktop browser too. This issue is quite random.
Hi Rahul — thanks for the report. I can see this is an issue report (users hitting an infinite loader when logging in with Web3Auth via MetaMask Embedded), mostly on mobile Chrome and sometimes desktop. I’ve captured the key details you provided and listed what will help our support team investigate quickly plus a few troubleshooting steps you can try right away.
Summary (from your report)
- SDK: MetaMask Embedded Wallets with Web3Auth
- Issue: Random infinite loader during Web3Auth login
- Platforms: Mostly mobile Chrome, sometimes desktop
- Screenshot: Provided (shows infinite loader)
What would help our team (please provide if possible)
- MetaMask Embedded SDK version (e.g., @metamask/embedded version)
- Web3Auth SDK version (web3auth/web3auth-modal or similar)
- Exact platforms & browser versions where this occurs (e.g., Android 14 / Chrome 121)
- Code snippets: initialization and login call (the minimal code used to init Embedded + Web3Auth and the login flow)
- Reproduction steps: does it happen every time for some users or randomly? Any patterns (network, region, cellular vs wifi, incognito)?
- Full browser console logs and Network tab capture during the failed login (the screenshot helps but console/network logs often show the root error)
- Any relevant config: Web3Auth clientId, redirectUri/origins registered in Web3Auth dashboard (no need to share secret keys)
- Whether browser settings (pop-up blocking, third-party cookies disabled) or extensions are present for affected users
Quick troubleshooting you can try now
- Check console/network logs for CORS, blocked popups, or cookie errors when the loader hangs — these are common causes
- Confirm Web3Auth client origin/redirect URIs are correctly registered in the Web3Auth dashboard for your app
- Try login in an incognito window or with extensions disabled (to rule out adblockers/privacy extensions)
- Ask affected users to enable third-party cookies or allow pop-ups temporarily (mobile Chrome often blocks some flows)
- Ensure you’re using the latest versions of MetaMask Embedded and Web3Auth SDKs — update if not
- Wrap the login call in try/catch and log any thrown errors or promise timeouts so we can see failures
Useful links
- MetaMask docs: https://docs.metamask.io
- MetaMask Builder Hub: https://builder.metamask.io
- Web3Auth docs (for config checks): Introduction | Documentation | Web3Auth
Next steps
If you can paste the missing version numbers and the init/login snippets and attach a captured browser console + network HAR (or screenshots showing console errors), I’ll add those to the ticket so the support team can start troubleshooting immediately.
Thanks — I know random, intermittent bugs are frustrating. Share the items above when you can and I’ll escalate this with as much detail as possible.
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 biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours
Hi, does this issue still persist with your users? Please let us know.