-
Notifications
You must be signed in to change notification settings - Fork 650
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
Wallet on connection error: "Failed to publish payload, please try again." #4337
Comments
hey @kvnschlndt thank you for the report. |
@ganchoradkov after the update we can see a slightly better performance. And also we now get notifications about possible memory leaks: Also it tries to reach the the relayer socket, but the wallet is disconnected from the dApp: |
Hey thanks for the response! Do you have any VPNs running while experiencing the issues? About the event leak, do you have steps to reproduce? Just leaving the app open for a while? |
Seems like you are subscribing to the "disconnect" event more than once, could be a loop or something. |
Hey, to better understand our use case: The memory leak appears when a lot of wallets are connected. |
Thank you for the overview, it seems like it might be a case of improper cleanup of failed connection attempts
this means there is an active connection and the error is logged by a past attempt |
So comparing the two versions: |
@ganchoradkov do you have any news? Still seeing this web socket problems, tho network connection is perfectly good. Is it possible that we are getting blocked because of producing to much requests? Updated in the meantime to: |
Hey @kvnschlndt unfortunately I don't have yet any conrete tips at the moment.
this shouldn't be the case unless you're sending +10 messages per second |
@ganchoradkov |
@ganchoradkov do you plan to fix the issue? |
Describe the bug
On the connection of the wallet this unhandled error is thrown.
Some connections are working some are not.
What is the reason? How to avoid this?
Expected behavior
No unhandled error thrown
Screenshots
The text was updated successfully, but these errors were encountered: