SES_UNHANDLED_REJECTION: WalletLoginError: Wallet popup has been closed by the user

Embedded Wallets (Web3Auth)
1

Hi, i recently migrated to web3auth v 10. Login via social media was working well, but just recently, when i tried using the login, now im getting:

SES_UNHANDLED_REJECTION: WalletLoginError: Wallet popup has been closed by the user.

Both in firefox / chrome, tried incognito as well. i’m on a growth plan. What can be the issue? again, when i release a few weeks back, this same flow was working well.

2

Thanks — I’m sorry you’re seeing that error after migrating. I’ll help get this to the support team quickly. First, I pulled the details you already gave and a short checklist of what we still need.

Collected details (from your message)

  • Error: SES_UNHANDLED_REJECTION: WalletLoginError: Wallet popup has been closed by the user
  • SDK: web3auth
  • SDK version: v10 (you mentioned migrated to web3auth v10)
  • Platform / browsers tested: Chrome and Firefox (also tried incognito)
  • Account plan: Growth
  • Behavior: Flow was working a few weeks ago and now suddenly shows this error

Quick troubleshooting notes / likely causes

  • Popup was actually blocked by the browser or an extension (adblock/privacy extensions often block OAuth popups).
  • Third-party cookies / storage blocked (OAuth flows sometimes fail if cookies/storage are blocked in the popup).
  • redirectUri / allowedOrigins mismatch or OAuth client config changed on Web3Auth dashboard (popup may open then redirect to an unexpected URI and close).
  • Recent browser update or extension update that changed popup/cookie policy.
  • A runtime exception inside the popup (network/CORS error) causing the popup to close early.

What I recommend you try now (quick checks)

  1. Try in a clean browser profile with no extensions (or disable extensions) to rule out blockers.
  2. Ensure popups are allowed for your site and that third‑party cookies/storage are enabled for the test.
  3. Confirm redirectUri and allowed origins in your Web3Auth dashboard match exactly what your app is using (including trailing slashes and http/https).
  4. Check the browser console and Network tab in the parent window for any CORS or network errors when you start the login — and capture the popup’s console/network if possible.
  5. Try a minimal reproduction page (only Web3Auth init + login call) to see if the problem is in surrounding app code.
  6. If possible, test on another machine/ISP to rule out environment-specific blocking.

What I need from you to escalate to the support team

  • Code snippets for initialization and login (your Web3Auth init and the function that triggers login). If you think you’ve provided these already, no need to resend.
  • Browser console logs or screenshots from the parent page and (if you can) the popup window when it opens / when the error occurs.
  • A URL or reproducible minimal repo/example (if you can share). If this is private, a minimal snippet that reproduces the issue is fine.

Relevant resources

If you’d like, paste your Web3Auth init + login code here and I’ll scan for common misconfigurations (redirectUri/clientId/allowedOrigins, popup vs redirect mode, etc.). Once you send those and any console output/screenshots, I’ll add them to the ticket for the support team and suggest next steps tailored to your code.

You’re not being spammed — I only asked for items we still need. I know this was working recently, so we’ll focus on blockers (extensions/popup/cookie/redirect) first. Happy to review your snippets now.

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

3

Hi @danieljao As you mentioned on Discord, the suggestions above could not resolve the issue. Would you please provide the information mentioned above? Then we will escalate it to our team.

6

Hey @danieljao
Great to meet again !
I see one error for WalletServices gating, if somewhere you’re passing useWalletServices as true, it might be causing this error. But I see I can move past that, its just seen on the homepage.
Later I move ahead and I am able to log in successfully.

image
image1920×1067 552 KB

Let me know if this error occurs in any other flow.
Thanks

1 Like
7

Hi @maharshi i dont use “useWalletServices”, also, did you see the console logs the “SES_UNHANDLED_REJECTION: WalletLoginError: Wallet popup has been closed by the user.” so this is happening, and the socialmedia login is not continuing due to that

8

HI @maharshi any updates on the above?

9

Can you check it on an incognito window of the browser? I suspect an extension could be hindering the login.