You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting "Unable to detect device share." error when using connectTo("openlogin", loginParams) but not when using connect()
If I use web3auth/modal and I'm able to successfully connect with openlogin as long as I use the connect() method. However, if I want to use web3auth/core (ie. connectTo) I get the Unable to detect device share screen
call web3auth.connect() --> this should show the modal and the flow should succeed
swap the call from web3auth.connect to something like web3auth.connectTo("openlogin", loginParams: {loginProvider: "google"}) (use the same method as you did in 2 and the same account)
going through the flow will work on first attempt (ie. account has never been registered to web3auth before). Logout of web3auth or use a different chrome profile and connect again. See the error screen below
4a. I noticed that the public address is also different between the two methods when connectTo succeeds the first time.
Expected behavior
I would expect:
connectTo to work successfully across devices, profiles, and sessions the same as connect
the resulting public keys to be the same regardless of whether I'm using connect or connectTo
Screenshots
Device Info (please complete the following information):
constweb3auth=newWeb3Auth({clientId: "<MY_CLIENT_ID>",chainConfig: {chainNamespace: "eip155",},enableLogging: true,web3AuthNetwork: "testnet",storageKey: "local",});constopenloginAdapter=newOpenloginAdapter({adapterSettings: {uxMode: "popup",network: "testnet",storageKey: "local",},loginSettings: {mfaLevel: "mandatory",},});web3auth.configureAdapter(openloginAdapter);useEffect(()=>{if(web3auth.status==="not_ready"){web3auth.initModal({modalConfig: {"torus-evm": {label: "Torus Wallet",showOnModal: false,},metamask: {label: "Metamask",showOnModal: false,},"wallet-connect-v1": {label: "Wallet Connect",showOnModal: false,},},});},[])constlogin=(loginProvider: LoginProvider)=>{awaitweb3auth.logout().catch(()=>null);// this is here to just to repro the issue// comment out one of these to test independentlyawaitweb3auth.connect();// this works consistentlyawaitweb3auth.connectTo("openlogin",loginParams: { loginProvider });// this does not work after first time logging in}
The text was updated successfully, but these errors were encountered:
Getting "Unable to detect device share." error when using
connectTo("openlogin", loginParams)
but not when usingconnect()
If I use web3auth/modal and I'm able to successfully connect with openlogin as long as I use the
connect()
method. However, if I want to use web3auth/core (ie.connectTo
) I get the Unable to detect device share screenTo Reproduce
Steps to reproduce the behavior:
web3auth.connect()
--> this should show the modal and the flow should succeedweb3auth.connect
to something likeweb3auth.connectTo("openlogin", loginParams: {loginProvider: "google"})
(use the same method as you did in 2 and the same account)4a. I noticed that the public address is also different between the two methods when
connectTo
succeeds the first time.Expected behavior
I would expect:
connectTo
to work successfully across devices, profiles, and sessions the same asconnect
connect
orconnectTo
Screenshots
Device Info (please complete the following information):
Additional context
My setup:
The text was updated successfully, but these errors were encountered: