Error on the console: Cross-Origin-Opener-Policy policy would block the window.closed call

[u.h.ugwu]

Please provide the following details too when asking for help in this category:
When users try to sign in with web3auth using any method, this error: “Cross-Origin-Opener-Policy policy would block the window.closed call.” is logged to the console. Please how can this be resolved? so we don’t have this in the console any more when users try to log in?

• SDK Version:
• Platform:
• Browser Console Screenshots:
• Related to Custom Authentication? Please provide the following info too: (Optional)
  • Verifier Name:
  • JWKS Endpoint:
  • Sample idToken(JWT)

Please provide the Web3Auth initialization and login code snippet below:

[vjgee]

@u.h.ugwu Can you share a screenshot of the complete console logs? Is it affecting your users from logging in? Share you Dapp URL to check

[u.h.ugwu]

Yes. It’s affecting them from logging in

[u.h.ugwu]

The DAPP is still on internal testing and isn’t available to the public at the moment

[chai]

The issue is something different.
having window.closed error is safe. we already account for it in our login process.
I think your sky.trade api requires a valid email. Not all login types return email address.
You might need to prompt the user to collect their email address if not returned by web3auth (eg: sms login, facebook login don’t return email).

[u.h.ugwu]

But I was using Facebook to log into the platform at some point. What changed? Was any new change made of recent?