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
One thing that’s been frustrating in testing is that, if a dApp fires off the association URL to open fakewallet, but then for whatever reason fails to connect to the websocket it opens, then fires off a second association URL with a different port, then fakewallet reopens to the screen with a spinner – still trying to respond to that first session request.
Is it a simple change to make fakewallet abandon the last and start the next session establishment, whenever receiving the session establishment intent?
The text was updated successfully, but these errors were encountered:
One thing that’s been frustrating in testing is that, if a dApp fires off the association URL to open fakewallet, but then for whatever reason fails to connect to the websocket it opens, then fires off a second association URL with a different port, then fakewallet reopens to the screen with a spinner – still trying to respond to that first session request.
Is it a simple change to make fakewallet abandon the last and start the next session establishment, whenever receiving the session establishment intent?
The text was updated successfully, but these errors were encountered: