Session breaks with multiple tabs open #387
Comments
|
We completely agree with @sentx-io . This issue has been reported multiple times by Kabila, including directly to the WalletConnect team. Unfortunately, the response has consistently been:
This limitation is causing significant challenges within our Dapps. The behavior severely impacts usability, especially when users rely on multiple tabs or devices for seamless interactions. To be honest, we’re uncertain about the best path forward to address this limitation, but it’s a critical issue that warrants further discussion and potential resolution.
|
|
interesting that a merge into a fork closes the issue, re-opening |
|
Can you provide feedback on this pr? #412 |
Wallet Connect will fail to return a transaction result to the source window as soon as a new tab is opened. It will actually return it to the wrong one instead, and the window that initially sent the transaction to be executed will never receive the acknowledgement from the wallet.
To reproduce:
Connect to a Dapp using Wallet Connect
Open a new tab in the same url
Execute a transaction on tab A and simply hit reject on the wallet
Execute a transaction on tab B and reject
One of the tabs will never get the ping back from the wallet. Instead, all of them will go to the same source window, whether or not it was the one that sent the transaction to be executed.
This is a big limitation and makes Wallet Connect very unreliable on any DApp where users often have multiple windows or tabs open (stats, analytics, feeds, market trades).
Any native connectors before Wallet Connect (hashconnect) work fine and do not have this issue.
The text was updated successfully, but these errors were encountered: