-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
ClientDisconnectedError #76
Comments
Hello, it seems that this error is thrown when client tries to send pong to closed connection. Does the connection stops working (not reconnecting) after that? |
No. It works because I can still get messages even though the error occurs. |
I see, in general it's normal that connection errors happen. And if SDK successfully reconnected - then it's an expected normal behaviour. Probably we should handle and suppress this error in the SDK when sending pong 🤔 |
It seems to be ok as the message transmission is not interrupted but it is a bit sad to see this in Firebase. I will be happy if improvement is made. thanks |
I am also getting the error. Though I get the following information:- Client Connecting |
Its something we see very often in our Sentry logging. A bit frustrating as these errors take up a lot of our Sentry allowance (50k per month) and I think we're using the Dart SDK correctly 😕 I can see this being a bit confusing to users of the SDK as when you Google this error, all results point to the SDK being used incorrectly (i.e. not connecting/reconnecting between Foreground) |
Trying to address this in #79 |
Please let me know whether v0.9.4 fixes this. |
@FZambia We've pulled this into our app and are pushing to production soon. Will let you know if we see an improvement. We've not forgotten about it 😃 |
Significantly reduced log records. We can say the problem is solved. |
@TomBeckett hello, still waiting for the feedback about your use case, do you have any updates? |
While the application was in the foreground, the following error occurred in the log records. It wasn't in the background.
The text was updated successfully, but these errors were encountered: