Hi Wilfred — thanks for the clear question. This sounds like an exploration (not an error report), so you don’t need to share SDK/init code right now — just wanted to confirm that first.
Short answer
- MetaMask doesn’t control Web3Auth access; Web3Auth is a third‑party service. Whether it works in Syria depends on Web3Auth’s own geographic/restriction rules and applicable sanctions.
- Many SaaS/Auth providers restrict access to sanctioned or restricted jurisdictions (and Syria is commonly on such lists), so it’s possible Web3Auth blocks some functionality there — but I can’t confirm that for you from MetaMask’s side.
What to check / next steps
- Web3Auth docs & legal pages — they’re the authoritative source for supported/unsupported countries and sanctions policy: https://docs.web3auth.io and https://web3auth.io
- Contact Web3Auth support or community (GitHub/Discord) to ask for a definitive list of unsupported countries and whether Syria is blocked:
- If you want to test directly from Syria, try a simple create-wallet / sign-transaction flow and collect any error messages. If you run into errors you can share them (error text, screenshots, or browser console logs) and I can help interpret what’s happening.
If you’d like, I can also:
- Help you draft a short message to Web3Auth support asking whether Syria is supported, or
- Walk through a quick test flow and tell you what logs to capture if you hit an error.
Which would you prefer?
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