Openlogin adapter not ready after initialization

Help - Plug n Play PnP Web SDKs
1

Please provide the following details too when asking for help in this category:

Please provide the Web3Auth initialization and login code snippet below:

export class Web3AuthSingleton {
  private static web3Auth: Web3AuthNoModal;

  private static init() {
    const auth = new Web3AuthNoModal(web3AuthConfig as any);

    const openloginAdapter = new OpenloginAdapter({
      adapterSettings: {
        uxMode: 'popup',
        loginConfig: {
          jwt: {
            verifier: 'verifier,
            typeOfLogin: 'jwt',
            clientId: web3AuthConfig.clientId,
          },
        },
      },
      loginSettings: {
        mfaLevel: 'none',
      },
    });

    const metamaskAdapter = new MetamaskAdapter({});

    Web3AuthSingleton.web3Auth = auth
      .configureAdapter(metamaskAdapter)
      .configureAdapter(openloginAdapter);
  }

  public static get instance() {
    if (!Web3AuthSingleton.web3Auth) {
      Web3AuthSingleton.init();
    }

    return Web3AuthSingleton.web3Auth;
  }
}

    const auth = Web3AuthSingleton.instance;

    await auth.init();

    this.vueApp = this.createVueApp();

    await auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, {
     loginProvider: 'google'
    });

The open login adapter status is indeed not ready, but the metamask adapter is (so metamask connection works). I don’t know what’s wrong because this code works in other projects.

2

Coming back with some extra information:
On apps where this works the following is printed tot he console:

loglevelSentry.esm.js:64 registering module [module-hash]

but in this case it isn’t.

Also, there’s this call taking place

https://broadcast-server.tor.us/store/get?key=[some-key]

but in the current app there is no such call.

Does anyone have any ideea what’s wrong and why the openlogin module does not seem to initialize properly?

3

Update: My hunch is that this is somehow because the web3auth initialization, login etc. is taking place inside an iframe

4

in order for the metamask provider to work i had to do the following in the iframe:

window.ethereum = parent.window.ethereum

so it would have access to metamask.
Is there something similar that i have to do for the Openlogin adapter?

5

@denisa.halmaghi Thanks for your patience.

Your issue has been submitted to our team. We will get back with further updates.

6

Hi @denisa.halmaghi,

Could you please update the web3auth SDKs to version 6? We have recently removed the dependency on iframes. For detailed instructions on how to migrate from version 5 to version 6, please refer to the migration guide available at here. Additionally, you can find useful examples in the pnp-examples repository.

Thanks

7