Failed to connect with openlogin provider LoginError: login popup has been closed by the user

[vaibhavsinha619]

"I encountered an issue while attempting to log in with web3Auth, resulting in the following error message:

{
"name": "WalletLoginError",
"code": 5111,
"message": "Connection with the wallet failed. Login with openlogin was unsuccessful."
}

package version:

"@toruslabs/openlogin-utils": "^4.7.0",
"@web3auth/base": "^6.1.3",
"@web3auth/ethereum-provider": "^6.1.1",
"@web3auth/no-modal": "^6.1.3",
"@web3auth/openlogin-adapter": "^6.1.1",
"@web3modal/react": "^2.7.0",

Implementation:

const web3Provider = async ({ chain }) => {
  const { chainNamespace, chainId, rpcTarget } = chain;

  const chainConfig = { chainNamespace, chainId, rpcTarget };

  try {
    const web3authProvider = new Web3AuthNoModal({
      clientId: WEB3AUTH_CLIENT_ID,
      chainConfig,
      web3AuthNetwork: WEB3AUTH_NETWORK,
    });

    const privateKeyProvider = new EthereumPrivateKeyProvider({
      config: { chainConfig },
    });

    const openloginAdapter = new OpenloginAdapter({
      privateKeyProvider,
    });

    web3authProvider.configureAdapter(openloginAdapter);

    await web3authProvider.init();

    return web3authProvider;
  } catch (e) {
    console.log(e);
  }
};


const web3AuthProvider = await web3Provider.connectTo(
        WALLET_ADAPTERS.OPENLOGIN,
        {
          loginProvider,
          extraLoginOptions: {
            login_hint: email,
          },
        }
      );

The user did not manually close the popup; it closed automatically after the redirection

[u.h.ugwu]

I am experiencing same issue. Please can anyone address this?

[tkchaw80]

I also having same issue

[vjgee]

@u.h.ugwu @vaibhavsinha619 @tkchaw80 Thanks for reporting.

Your issue has been forwarded to our team and we will get back to you with further updates on the progress.

[alexander]

Same error for the last couple hours

[maharshi]

@here Please try it now, team has pushed a build which should solve the issue. Also we do a phased roll out for different regions and it is causing the issue on a few regions where this update was rolled out.
New users won’t be affected at all, this is only affecting existing issues.
The fix is rolled out now. It will take some time to propagate across regions.
Apologizing for the inconvenience.

[alexander]

Still getting this error, you can check at - https://app.rivo.xyz/

How long might it take for fix to propagate across regions?

[maharshi]

Could you please try once after performing a hard refresh?

[vaibhavsinha619]

still getting the same error

[alexander]

Hard refresh didn’t help

[tkchaw80]

Now is working for me
Just FYI, Control + refresh not working, you have to clear cache from chrome:

[maharshi]

If you are on chrome, hold down the control button and press refresh and you’ll see this. Here, press Empty cache and hard reload.

[jg1]

Same here. Have cleared cookies, cache, application, everything is cleared.
Was working fine just a couple of hours ago, now each time on devnet am getting the errors above.

I’m using Firebase for auth, no-modal SDK and the wagmi connector. It’s been stable for days.

[jg1]

The web3auth popup correctly sometimes asks me if I want to enable 2FA, I press skip for now. Then there’s a delay, the popup closes. Then there is a delay before the open login adapter produces the error.

[jg1]

Web3AuthConnector’s connect() is throwing, but on the line before I can successfully get an instance of the provider via getProvider().

[alexander]

Resolved with

Empty cache and hard reload

.
Thank you.

[jg1]

I suspect this might be a browser issue. Was using Arc. Switched to Chrome - all fine. Will reach out to the Arc browser people about their cache-clearing.

[jg1]

Can you give us more detail about why clearing cache should work if we’re using locally built npm packages?

[maharshi]

Yeah sure, the packages might be built locally but if you notice carefully, you’re redirected to Web3Auth for login purposes. In order to give you the seemingly fastest experience, the browser would attempt to cache external sites.