Web3auth for new SDK seems to be generating wallets that no longer show up in torus

Hello, i am transitioning to the new SDK and noticed something odd. I am logging in to the same app with my test gmail account and it is 1) generating a new wallet address with nothing else changed apart from SDK version and 2) the new wallet generated doesn't show up when logging into torus with same sign in methodology (same gmail account).

Does the new SDK generate new wallets for every user using social media and/or email? If so, is there something special that needs to be done so these are visible in Torus wallet?



Originally posted by: chusla

Check the discussion at: https://github.com/orgs/Web3Auth/discussions/1249

video of issue i am seeing any input would be much appreciated thank you! @shahbaz17
@himanshuchawla009
https://www.loom.com/share/c6225c444ef146d9b9af490e5160601f



Originally posted by: chusla

the observed issue in one screenshot. How can same login methodology in torus app result in two different and discrete sets of wallets?

image



Originally posted by: chusla

Here is a video exhibiting the behavior on the w3a demo app. I log in with social media, click torus it shows one distinct wallet. if i log out and then log back in with same gmail it shows me a whole other set of wallets and the generated one no longer retrievable. So question is why are the separate and how can i actually retrieve the one generated by new SDK? thanks!

https://www.loom.com/share/c6ea348145c14c009db4ae8877afcf6e



Originally posted by: chusla
Will try thanks!
On Wed, Feb 22, 2023, 4:21 PM ieow ***@***.***> wrote: testing.tor.us is intended to point to mainnet for internal testing now. Please use https://lrc.tor.us/ for testnet


Reply to this email directly, view it on GitHub
<#1249 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVOW7RZQISOWG7SUEL7URLDWY3CT5ANCNFSM6AAAAAAUIEMS5U>
.
You are receiving this because you authored the thread.Message ID:
@.***>



Originally posted by: chusla

@ieow loom with another walk through. playing around i'm able to get my old wallets if i eliminate all external wallets besides torus-evm.

however if i use "openlogin" to log in this is where i start to get the separate wallet that was generated and the only way i can currently see that within torus is through the pop up window embedded in the demo app. logging into testing.tor.us or app.tor.us both show my other older wallets.

https://www.loom.com/share/64c8fecb94b9492f985bfe75488389c3



Originally posted by: chusla

hmm thanks @ieow this is a promising suggestion but trying it out and still getting same issue. so switching to "mainnet" i still see the single generated wallet.

Whereas in testing.tor.us still seeing the other original wallets.

image
image



Originally posted by: chusla

seems like official demo app exhibiting same behavior where login with social generates a wallet but then using that same social to log into torus app directly, we are no longer able to see the generated wallet. Previously on prior SDK you would see whatever wallet's been generated for that social account.

image
image



Originally posted by: chusla

Did you figure out a solution? Our production mainnet deployment is generating a different address for email login than app.tor.us

@web3auth-team hello following up on this. testing.tor.us still does not show testnet wallets. How can we interact with testnet wallets via torus? Thanks!

Web3Auth does not give you access to torus. The keys are NOT the same as web3auth is a key management solution and Torus is a separate wallet.

hi @zhen bit of a misunderstanding so let me clarify. on mainnet, if i log into an app with web3auth it generates a wallet.

Previously if i then logged into app.tor.us with the same credential i could see that wallet and interact with it and export my private key for both mainnet and testnet. Now, i only see mainnet wallets. So question is, how/where can i export my private keys for testnet wallets?

Thx!

hello @zhen or anyone else from @web3auth-team team? gotta say, once the move was made to community boards, it’s been a lot tougher to get an answer…

hello @zhen @web3auth-team can you please provide any add’l insight or workarounds for this? Have multiple clients asking how to retrieve their private keys for testnet wallets. Thanks!

Hey there @web3auth-team

I am having the same issue, as @andrew mentioned. Logging in with the same email/google(Mumbai testnet) creates different wallets on the dApp and the Torus web app.