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
We are currently investigating an issue where users of our Dapp occasionally run into the problem that if they change their wallet in Rabby, it does not update in the connected Dapp. The connected wallet in the Dapp remains the previous one, not reflecting the currently selected one.
This is problematic because when people sign their transactions, they do so with the new wallet address but could unknowingly send it to the previous wallet address.
We are using Web3-onboard as our injected wallet connection provider and initially thought this issue was related to their package. However, we noticed that when trying this with other Dapps, the issue is the same, leading us to believe it is either related to Rabby or Brave.
I do not have exact steps to reproduce this issue as there seems to be no visible pattern so far, but the way I was able to reproduce it a few times is as follows:
Connect to the Dapp with the Rabby wallet.
Open a new tab and switch to another wallet in Rabby.
Return to the Dapp tab and see that it is still connected to the previous wallet address.
When this happens, it gets stuck with that wallet, and no matter how often we try, it won’t change. The reason for this is that the accountsChanged event is not triggered on the EIP1193Provider.
Rabby wallet: 0.92.90
Brave: 1.70.117
This is a big issue, so I’d appreciate any assistance with this.
The text was updated successfully, but these errors were encountered:
We are currently investigating an issue where users of our Dapp occasionally run into the problem that if they change their wallet in Rabby, it does not update in the connected Dapp. The connected wallet in the Dapp remains the previous one, not reflecting the currently selected one.
This is problematic because when people sign their transactions, they do so with the new wallet address but could unknowingly send it to the previous wallet address.
We are using Web3-onboard as our injected wallet connection provider and initially thought this issue was related to their package. However, we noticed that when trying this with other Dapps, the issue is the same, leading us to believe it is either related to Rabby or Brave.
I do not have exact steps to reproduce this issue as there seems to be no visible pattern so far, but the way I was able to reproduce it a few times is as follows:
When this happens, it gets stuck with that wallet, and no matter how often we try, it won’t change. The reason for this is that the
accountsChanged
event is not triggered on theEIP1193Provider
.Rabby wallet:
0.92.90
Brave:
1.70.117
This is a big issue, so I’d appreciate any assistance with this.
The text was updated successfully, but these errors were encountered: