Closed 0x3639 closed 2 months ago
I cannot seem to reproduce the issue. It works fine when I follow the steps described. I'm using the same setup with Brave and shields up. The address and balances are updated on the bridge when changing the selected address in Syrius.
OK - let me test again on a new VM with a fresh install of Chrome or Brave. This issue seemed like a caching issue that I've had in the past. I'll report back.
This turned out to be a caching issue. Closing issue.
Describe the bug I recently upgraded to syrius v0.2.0. I connected syrius to the bridge (https://bridge.mainnet.zenon.community/) without any issues. I realized I connected on the wrong wallet. I tried to change the wallet in syrius to a different wallet without disconnecting / reconnecting walletconnect. After doing that balances under bridge history were not accurate.
I then disconnected and tried to reconnect and got the following error in the console and walletconnnect timed out and never connected.
To Reproduce Steps to reproduce the behavior:
I tried this in Brave without shields up and chrome. I tried to clear cache in Chrome. In Chrome I tried to : Right click > Inspect Element > Application tab > Storage > Clear site data
Expected behavior Connect to syrius to the bridge
Actual behavior Walletconnect times out and does not connect syrius with the bridge.
Workaround None
Screenshots NA
Desktop (please complete the following information):
Additional context NA Add any other context about the problem here.
Bounty program