Replies: 1 comment
-
Additionally: it is very clear that the extra reprompting with Login with Google gets re run due to the Refreshing the page with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm trying to make re-connecting a wallet seamless on refresh using web3auth in React, but I'm reprompted to login via a social login upon refresh. I think the root cause is something to do with "taurus-evm" as an adapter. Here's how I know this:
I have the metamask and the torus-evm adapter set up:
When I run the following:
After having logged in before, the provider is cached in some way and I'm not reprompted to connect via metamask.
However, when I run the following:
After having logged into Google before, the provider is NOT cached, and I have to log back into Google every single time. Clearly the session is still active-- going to app.tor.us between and after refreshes shows that the user is still logged into Torus via Google. It's only that my React app isn't able to pick it up.
The Web3Modal's of the world have a
web3Modal.cachedProvider
to recover providers. Is there an equivalent?tl;dr for social logins via @web3auth/modal & torus-evm's Google login (or any other social login), how do I recover the web3 provider without having to reprompt the user to login again?
Beta Was this translation helpful? Give feedback.
All reactions