When I try to login I stuck on 2FA confirm page after using start 2FA login

:classical_building: Content from Web3Auth Community

This topic was originally posted by samuel on 10/19/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.


When I tried to login in my developing app, I stuck on 2FA confirm page after using start 2FA login.

When I tried to start 2FA login at first time, I used “openlogin” with google for the main account and twitter for the 2FA account after then I couldn’t received any response.
But after then I will try to login with “openlogin” with my main account then I stuck on 2FA confirm page. There was not displayed an recover email for an backup phrases but it is displayed when I try to login with another account that is already set a recover email at the “beta.openlogin.com”

How can I set a recover email at my main account that stuck on confirm page?

Screenshot
Screenshot882Ă—755 34 KB

If I got that options I wouldn’t stuck on 2FA confirm page,
but I just stuck on like a screenshot after first 2FA login,
it is just set 2FA on login popup,
it is not set on “beta.openlogin.com”.
I can’t do anything your suggestions.

Can you provide your Dapp URL to check? Are you using VPN or is there is any restriction from your ISP? Provide your implementation code.

I’m testing on localhost.
When I logged in with that account in my app, I got an error below.

{"name":"WalletLoginError","code":5111,"message":"Failed to connect with wallet. Failed to login with openlogin"}

Anyway when I logged in “beta.openlogin.com” I stuck on 2FA confirm page, not login at my app.

Please provide the below information to proceed:

  1. SDK & version
  2. Framework
  3. Web3Auth initialization code and login code

But this issue is that I can’t get the backup phrases because I can’t login “beta.openlogin.com” then I didn’t received any mails when I login 2FA at first time with below account.
My google account is “samuel@23labs.io”

  1. SDK & version
    "@web3auth/base": "^7.0.4",
    "@web3auth/base-provider": "^7.0.4",
    "@web3auth/no-modal": "^7.0.4",
    "@web3auth/openlogin-adapter": "^7.0.4",
  1. Framework
    Chrome V117.0.0.0 (macOS, Desktop)

  2. Web3Auth initialization code and login code

import { CHAIN_NAMESPACES, WALLET_ADAPTERS } from "@web3auth/base"
import { Web3AuthNoModal } from "@web3auth/no-modal"
import { OpenloginAdapter } from "@web3auth/openlogin-adapter"
import { CommonPrivateKeyProvider } from "@web3auth/base-provider"
import { WEB3AUTH_KEY, RPC_URL } from "../../../data/constants"

const chainConfig = {
chainNamespace: CHAIN_NAMESPACES.OTHER,
chainId: “0x2”,
rpcTarget: RPC_URL,
displayName: ,
blockExplorer: “”,
ticker: “MY”,
tickerName: “My”,
}

export async function requestUserInfo(loginProvider: string) {
const web3auth = new Web3AuthNoModal({
clientId: WEB3AUTH_KEY,
chainConfig,
web3AuthNetwork: “testnet”,
})

const privateKeyProvider = new CommonPrivateKeyProvider({ config: { chainConfig } })

const adapter = new OpenloginAdapter({
loginSettings: {
mfaLevel: “none”,
},
privateKeyProvider,
})

web3auth.configureAdapter(adapter)

await web3auth.init()
if (web3auth.status === “connected”) await adapter.disconnect()
const web3authProvider = await web3auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, { loginProvider })
if (!web3authProvider) throw new Error(“Web3Auth provider not found”)
const privateKey = (await web3authProvider.request({ method: “private_key” })) as string
const { name, email } = await web3auth.getUserInfo()
return { name, email, privateKey }
}

And when I try to login my app with “incognito” chrome, I got a twitter social login option and I could logged in my app.
But I still stuck on 2FA confirm page, I think there are needed to add “social login access”.

Screenshot 2023-10-19 at 5.04.47 PM
Screenshot 2023-10-19 at 5.04.47 PM683Ă—554 24.6 KB

@vjgee Don’t you have any plans to add twitter social login in beta.openlogin.com/tkey-input#[any options]?

It just need to use my account. I think it’s only solution of my problem.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

@samuel Are you still facing this issue ?