Thanks — I’m on the MetaMask / Web3Auth team. This is an SMS OTP delivery problem (not a new feature request). Your agent’s summary is accurate — most likely causes are carrier/provider routing, rate-limiting, or number-format/verification mismatch.
Quick checklist to try right now
- Wait 15–30 minutes to clear any rate-limit suppression and try again once.
- Ensure the phone is entered in E.164 format (+).
- Try a different phone number (different carrier if possible).
- Disable any SMS spam/blocking apps on the device.
- Retry from the same device/IP you previously used (may skip device verification).
What I need from you to investigate (keep it short):
- Embedded Wallets SDK version you’re using
- Platform (Web / Mobile — iOS or Android) and browser + version if Web
- Confirm whether the phone was entered in E.164 and whether you tried another number
- Approx timestamps of a few failed OTP attempts (UTC is fine)
If those steps don’t work, I can escalate to our team to check SMS provider logs and rate-limit/abuse flags. Please share the short details above (if you don’t want to post the full phone number publicly, DM or open a private ticket with the number and timestamps) and I’ll have someone from the team pick this up.
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