@aliencoder not sure if this is already mentioned somewhere else, but I used s y r i u s v0.0.7 to create a pair using the WalletConnect button on the mainnet bridge website. I cannot connect after removing the pair from s y r i u s.
When trying to connect using the WalletConnect button it just waits for approval from the wallet. The wallet does not have a pair and does nothing.
Basically you disconnect and you try to reconnect again? Did you refresh the browser window? Feel free to dm me so we can fix this bug. We have persistent logs now (in the syrius folder), we should check them.
I’ve updated the walletconnect_flutter_v2 to latest version v2.0.12 and now I’m handling the onSessionProposalError callback by refreshing the WalletConnectSessionsBloc.
I was unable to reproduce the bug.
You mentioned that “typing in localStorage.clear() in the console solved the issue”.
It is caused by the onRelayClientDisconnect callback that gets called every millisecond. The wallet tries to establish a connection, but without success.
It also triggers the logger, which involves writing on disk (keeping the disk busy and freezing the wallet).
@mehowbrainz experienced this earlier. He couldn’t add a node, an action that requires writing on disk.
I’ve added support for QR scanning using the MacOS built-in camera (it works with Android and iOS out-of-the-box, @DrBlaze_21 please look at the source code). For Windows I’ll wait for the official camera implementation.
I’m successfully connected to both the bridge and the demo dApp.
When you see relay: Instance of 'Relay', active: false in the logs, it means that Syrius cannot establish a connection to the relay server operated by the WalletConnect team.
Can someone help us debug the issue? I think the relay server is causing this issue.
(looks like the entire history of the wallet). Also can’t mass clear, have to press ‘x’ on each one individually?
Also took a while (30-40 seconds) to initialize the embedded node and continue synching on first launch (overwriting previous version of 0.0.7). Subsequent launches were normal and quick.