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
For example, sending a successful wallet_switchEthereumChain request to the web3 provider object does not trigger a chainChanged event (or even the depcreated networkChanged one).
If I disconnect (sign out) of the sequence wallet, I also don't get a disconnected event, although I'm not sure that's by design as the client in the page may still be connected?
The text was updated successfully, but these errors were encountered:
Ditto from #324 (comment), we've had to rewrite our code to not follow blindly web3js events and be able to listen from other sources, aka Sequence's methods. Could be a blocker for projects looking to integrate Sequence into their already existing ethers/web3js-compatible code.
Listening to events (https://docs.metamask.io/guide/ethereum-provider.html#events), via
sequenceProvider.transport.provider.on(eventName, eventHandler)
does not seem to work.For example, sending a successful
wallet_switchEthereumChain
request to the web3 provider object does not trigger achainChanged
event (or even the depcreatednetworkChanged
one).If I disconnect (sign out) of the sequence wallet, I also don't get a
disconnected
event, although I'm not sure that's by design as the client in the page may still be connected?The text was updated successfully, but these errors were encountered: