Bad Private Key error on Google Auth

[jeremymoore]

We're getting a spinning blue wheel on the "Constructing your key on..." open login popup.

While debugging we see Error: Bad private key.

We're implementing on cyan using Web3AuthCore with social auth providers like google.

[shahbaz17]

Hey @jeremymoore

Could you share the web3auth initialization and login code here? Also, please share the SDK version here.

[shahbaz17]

If you're to use google verifier for custom authentication then please follow https://web3auth.io/docs/custom-authentication/social-providers/google and pass the created verifier name.

But before moving forward. May I know what are you trying to use?

A google login by web3auth or google login with your config without Modal?

[yashovardhan]

Also can you remove the package @web3auth/web3auth - it has been deprecated.

[jeremymoore]

google login with your config without Modal

[jeremymoore]

We do have the implementation following your link, I think we're good there unless there's something specific you see a problem with.

[shahbaz17]

Please use the below config, it will work:

const openloginAdapter = new OpenloginAdapter({
  adapterSettings: {
    loginConfig: {
      google: {
        verifier: "tronic-google",
        typeOfLogin: "google",
        clientId: "GOOGLE_CLIENT_ID", //use your app client id you got from google
      },
    },
  },
});

[chaitanyapotti]

Thanks for reporting this. I've fixed the issue and pushed a new build.
Although, this should not occur frequently.! It's for a rare case where a generated sessionId is not padded

[jeremymoore]

@chaitanyapotti once you made this update we no longer see the Bad Private Key error, however we immediately began seeing the following:

Failed to connect with wallet. Wallet adapter is not ready yet, Please wait for init function to resolve before calling connect/connectTo function

On further investigation, this is not an issue in Testnet.

We ran the sample app, and are seeing the same success in the testnet, and failure in mainnet.

[jeremymoore]

We create new verifiers and the issue is resolved. Can you help us understand why the previous verifiers suddenly stopped working?

[chaitanyapotti]

Old verifiers should also be working as intended. Pls check again