Thanks — sorry you’re hitting this, Daniel. I pulled the key details from your message and summarized them below so our support team can triage quickly.
Extracted details
- SDK: Web3Auth
- Version: v10 (recently upgraded)
- Platform: iPhone (iOS)
- Auth method: Google login
- Symptom: After entering the recovery phrase the popup hangs and doesn’t continue
A few quick checks & possible causes (things that often affect iOS popup flows)
- iOS/safari popup or third‑party cookie restrictions can block popup/redirect continuations. Try in Safari (not an in‑app browser) and make sure popups/content blockers are disabled.
- Redirect vs popup flow: iOS sometimes behaves better with redirect flows rather than popups. If you’re using popup mode, try a redirect flow to test.
- Ensure any v10 migration steps and redirectUri settings required by Web3Auth were applied (mismatched redirect URIs can cause hangs).
- Check for any console/network errors — Web3Auth usually logs helpful errors when continuation fails.
To help the support team reproduce and fix this, please share the following (only what you have — we don’t want to spam you):
- Code snippets for initialization & login (the Web3Auth init and the call that triggers the Google login/recovery flow).
- Exact reproduction steps you used on the iPhone (browser/app, sequence of clicks, whether you choose recovery phrase from the same device, etc.).
- iPhone model and iOS version, and whether this is Safari or an in‑app browser (Gmail/WhatsApp/etc.).
- Is this happening for all users or only that one user? Did it work before the v10 upgrade?
- Browser console logs or screenshots of the popup hang and any JS errors (for iOS, a screenshot is fine if remote debugging isn’t available). Network logs are helpful if you can capture them.
If you want to try a quick workaround while we investigate:
- Test the same flow on desktop to confirm the issue is iOS‑specific.
- Try switching to a redirect flow instead of a popup (if feasible).
- Temporarily disable content blockers / cross‑site cookie restrictions on the phone and retry.
- Enable debug logging in Web3Auth (if available) to capture more details.
Once you share the code snippets and any logs/screenshots you have, I’ll pass them along to the support team and we’ll take it from there. I appreciate the details you’ve already provided — we’ll work to get this resolved.
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