-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throwing exceptions when after few minutes with no interaction #79
Comments
Similar here. I've the stack trace from the Godot Debugger. This seems to happen regardless of whether the QR code is scanned or ignored (
|
I have the same issue too. Though I'm attempting with Blazor WASM... EDIT: Disregard this. I'm trying to scan with the Loopring Wallet which only supports Sign V1... |
This has been fixed in 2.0.5 can you confirm? |
Hi @gigajuwels! But something is happening behind the scenes (every minute there are some exceptions happening) What I can see is that these exceptions behind the scenes are affecting the requests/events _client.On(SESSION_DELETE, delegate ()
{
OnSessionDeleteEvent?.Invoke(this, EventArgs.Empty);
}); also if I use |
Still have the same issue. As written in the referenced posts above. |
Cannot reproduce after Release 2.1.1 #129 |
@skibitsky the issue is not really resolved for me on version 2.1.1 Look at these steps to reproduce the broken connection It has been almost 8 months since I posted this issue and is still not resolved. Please let me know if you need any more info. |
Thanks, @axenteoctavian! This issue was caused by I've opened a PR #141 with a potential fix. Could you please check if it resolves the issue for you? |
Hi @skibitsky! This PR got something right. |
Thanks, @axenteoctavian! I was able to reproduce and fix the issue in the same PR. WebSocket reconnection logic was broken. |
Hi @skibitsky! I'm trying to use WalletConnectUnity and I think this issue still persists. If I understand correctly after the socket is closed the Relayer should attempt to reconnect and all the commutication should return to normal. I've added this to WCWebSocket to reproduce the issue
After the the socket disconnects though it shows a log from JsonRpcProvider that the connection is opening no further communication is possible. New calls to SignClient.Connect() don't work. I'm testing this because the disconnect still happens automatically after some time. Maybe I'm doing somthing wrong and you can help with this. Thanks! |
Hi @vorberohus, Your are right, and sorry for that. WalletConnectUnity and WalletConnectSharp aren't in full sync, I wanted to push one more PR before making release and merging it into WalletConnectUnity. I've just merged v2.1.2 into WalletConnectUnity, it will fix the issue for you. |
Hi @skibitsky! After 5 mins without interaction, the request is received in my wallet, but the response is not coming back. |
I am connecting to my wallet with something like this:
There are 2 errors that happen after some time of inactivity doing nothing:
1.
Thank you! 🙏
The text was updated successfully, but these errors were encountered: