You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Aptos team. I was using @aptos-labs/[email protected] and there's no way how can I understand whether user authorized within the wallet or not. It's needed to restore the connection after page reload.
Basically my strategy is:
IF account() returns authorized account
CALL .connect()
ELSE
Don't do anything and not bother the user with wallet UI requests
Hey @0xmaayan . We're not using react adapter here, we primarily using your core entity @aptos-labs/wallet-adapter-core. Because we have our own connection adapter library since we're multichain (evm and others)
And autoConnect couldn't work as to me, it just simply calls connect in useEffect which should lead to triggering the wallet UI and it bothers users since we should call connect only when we're know it's authorized within the website
the analogue technique is in EVM when you calling eth_getAccounts before you restoring your connection
Hey Aptos team. I was using
@aptos-labs/[email protected]
and there's no way how can I understand whether user authorized within the wallet or not. It's needed to restore the connection after page reload.Basically my strategy is:
account()
taken from docs: https://aptos.dev/standards/wallets#get-accountI was trying to extend your
WalletCore
class but all needed fields are private so I can't make it externallyThe text was updated successfully, but these errors were encountered: