[Archive] Connecting using Metamask without authenticating and refreshing the page results in a rehydrated state

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by githubdiscussions on 2/5/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

Hiya, We are using the core sdk with wallet & social login (all arev.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:

  1. Connect an external wallet using Metamask adapter (using connectTo, without invoking authenticateUser, default configurations with testnet)
  2. Refresh the page
  3. The connected event is emitted with the reconnected property set to true

In the past the reconnected property was the only indication the call to authenticateUser can be made without prompting the user. If authenticateUser is invoked between steps 1 & 2 this doesn't occur



Originally posted by: shayg-grappa

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