Web3Auth
Replies: 17 comments 22 replies
-
|
video of issue i am seeing any input would be much appreciated thank you! @shahbaz17 |
Beta Was this translation helpful? Give feedback.
-
|
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.
|
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
CW suggested looking at interoperability and turning that on. double checked and interoperability was turned on for evm chains, i turned on for all other chains. still getting an issue where a login with gmail account in demo app vs torus app result in completely different sets of wallet addresses. another loom with audio discussing the issue i'm seeing. Is no one else seeing this issue? |
Beta Was this translation helpful? Give feedback.
-
thx for response oh interesting @ieow , this is promising, but when i log into testing.tor.us, still seeing my original wallets and not the newly generated one. is there another way to toggle between "testnet" and "mainnet"?
|
Beta Was this translation helpful? Give feedback.
-
|
Dapp are only able to access dapp specific wallet. (which is the only one shown) login to app.tor.us will show all wallets ( include dapp that allow interoperability ) that run live on mainnet *note: wallet created on testnet are not migrate able to mainnet and vice versa |
Beta Was this translation helpful? Give feedback.
-
|
ok i can see that that makes sense, but then how do i get app.torus to display that wallet? Logging with same gmail to app.torus does not display any wallets generated when logging in with the new sdk for some reason. thx! |
Beta Was this translation helpful? Give feedback.
-
|
I don't get what you mean.
|
Beta Was this translation helpful? Give feedback.
-
|
so in the screenshot below, I logged in via gmail with one2all.test@gmail.com into the web3auth demo app. it created a wallet starting with 0x178d. I separately logged into both app.tor.us and testing.tor.us with the same method (gmail with one2all.test@gmail.com) and was not able to find the wallet 0x178d in the list. This occurs even with my own app where i have checked off interoperability (which i do for every client id i generate) and the app is properly configured to be on mainnet. |
Beta Was this translation helpful? Give feedback.
-
|
the observed issue in one screenshot. How can same login methodology in torus app result in two different and discrete sets of wallets?
|
Beta Was this translation helpful? Give feedback.
-
|
I speculate that the small window is login on the site demo-app.web3auth.io while the full window is login on app.tor.us refer this |
Beta Was this translation helpful? Give feedback.
-
|
ok even weirder, i ask a question in support and it shows up in both places. so the account is def the same account. so why are the sets of wallets completely different? I'm completely thrown for a loop. please help!
|
Beta Was this translation helpful? Give feedback.
-
|
In the video, Select |
Beta Was this translation helpful? Give feedback.
-
|
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.
|
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
ok, messing with url's further. looks like there is one parameter that is making a big difference and it is "namespace" if i include "namespace=demo-app.web3auth.io" in app.tor.us url i can access the generated wallet. but if i do not include it i see my old wallets. so question now is what is namespace and why is it so important? https://www.loom.com/share/4d66b48a688b49af912a2207a1f87fe2
|
Beta Was this translation helpful? Give feedback.
-
|
For the dapp that host at localhost, *.web3auth.io and *.tor.us, the wallet generated will not show on the app.tor.us |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the response @ieow is this a new behavior with new SDK? Because as far as i understand previously wallets weren't silo'ed like this, at least i never encountered an issue where new wallets were being generated and then not accessible/visible via app.tor.us. For example, i created a custom dapp which is hosted by a third party (bubble.io) and mapped to my personal domain for instance at demo.one2all.io. I whitelisted this domain in plug and play for that client id. But it is still not visible in app.tor.us. Is this expected behavior? |
Beta Was this translation helpful? Give feedback.
-
|
@ieow i think i might have seen you or someone from team log in, please use this link as it is the one set to latest SDK: https://demo.one2all.io/version-web3auth-sdk/ Thanks! it can connect but is generating a new wallet for me relative to prior SDK. |
Beta Was this translation helpful? Give feedback.
-
|
or this branch, i just pointed this branch to latest SDK as well: https://demo.one2all.io/version-test/. This branch is using testnet client ID whereas prior link "version-web3auth-sdk" is using my mainnet client ID. So what i'm seeing here is that a new wallet is generated when connecting to https://demo.one2all.io/version-test/ with address: 0x91f6339d2d2d8ebb37a423203abacfbc6a19caab. this is for gmail login one2all.test@gmail.com but when i log into app.tor.us or testing.tor.us that address is not visible or selectable in dropdown.
|
Beta Was this translation helpful? Give feedback.
-
It show up on my app.tor.us either for https://demo.one2all.io/version-web3auth-sdk/ |
Beta Was this translation helpful? Give feedback.
-
|
just connected with my personal gmail account and had same result, a wallet was generated in testnet but was not visible in app.tor.us. Is it because app,tor.us is only showing mainnet wallets? testing.tor.us doesn't seem to be pointing at testnet wallets is there a way to force app.tor.us to show testnet wallets? |
Beta Was this translation helpful? Give feedback.
-
|
testing.tor.us is not pointing to testnet for now. Will be fixed soon. |
Beta Was this translation helpful? Give feedback.
-
|
testing.tor.us is intended to point to mainnet for testing now. |
Beta Was this translation helpful? Give feedback.
-
|
Ah that makes more sense now I thought I was going insane!! I just tried the second site looks like it's not exactly syncing there either maybe the test cluster is not actually testnet not seeing my testnet wallet there either. Is there timing as to when testing.tor.us will actually point to testnet? Knowing it will eventually is def comforting but timing would be much better so I can communicate to my clients. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
there seems to be a precedent for this where certain wallets that are visible in current app.tor.us aren't visible if manually reverted back to like v1.21.0 or earlier via url. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, due to requirement changes, we change the wallet account visibility in app.tor.us |
Beta Was this translation helpful? Give feedback.
-
|
Ahhhhh I think mystery solved. Yes if testing.tor.us pointed we should be
good! Thank you!
…On Wed, Feb 22, 2023, 3:59 PM ieow ***@***.***> wrote:
Yes, due to requirement changes, we change the wallet account visibility
in app.tor.us
—
Reply to this email directly, view it on GitHub
<#1249 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVOW7R4FRG3B5BF37JUNXF3WY3ABDANCNFSM6AAAAAAUIEMS5U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @ieow do you have any timing as to when testing.tor.us will reflect testnet environment wallets? It's still critical for testing purposes to have full range of functionality including ability to export private key via torus dashboard for example. Thx! |
Beta Was this translation helpful? Give feedback.
-
|
Did you figure out how to get the correct account to show on app.tor.us? We have a production deployment with 'cyan' but when users log into app.tor.us, the address is not the same that is used with our modal. |
Beta Was this translation helpful? Give feedback.
-
|
Have you figured this out? |
Beta Was this translation helpful? Give feedback.
-
|
hmm they said at some point testing.tor.us would point to testnet wallet addresses but i haven't seen it yet. |
Beta Was this translation helpful? Give feedback.
-
|
But I am talking about production setup now, which should work? |
Beta Was this translation helpful? Give feedback.
-
|
Production is ok yes. It seems like a one time thing since they changed their backend environment framework. Going forward shouldn't change wallets in production from what I understand |
Beta Was this translation helpful? Give feedback.
-
|
Well at least I try it in production and I still get different wallets and no option to choose my project in the accounts dropdown list :/ |
Beta Was this translation helpful? Give feedback.
-
|
Right now |
Beta Was this translation helpful? Give feedback.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions