When connecting and sending a transaction we have a confirmation window, but if it is left unanswered - after a certain time it loses connection with the bridge. And if there is no problem for the connect, then when sending a transaction there is an unpleasant bug. The flow is as follows:
transaction preparation (not with native tokens ccd) - click on transfer - click sign&submit first window but totally ignore second
after a while the error comes:
A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
But while the window has lost connection with bridge, it still remains active. And if you will confirm the transaction - the tokens go nowhere, the user simply loses them.
I have not found any information to fix this, so could you please tell me if there is a solution to this?