Connecting using Metamask without authenticating and refreshing the page results in a rehydrated state #1283
shayg-grappa
announced in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hiya, We are using the core sdk with wallet & social login (all are
v.4.3.0
)We noticed yesterday that when using wallet login the metamask the adapter is rehydrated after refreshing the page but when calling
authenticateUser
prompts the user with the SIWE message.This was working fine a few days ago.
Steps to reproduce:
connectTo
, without invokingauthenticateUser
, default configurations with testnet)connected
event is emitted with thereconnected
property set to trueIn the past the
reconnected
property was the only indication the call toauthenticateUser
can be made without prompting the user. IfauthenticateUser
is invoked between steps 1 & 2 this doesn't occurBeta Was this translation helpful? Give feedback.
All reactions