Closed tempo-riz closed 5 months ago
+1
This issue makes our backend leaking connection 😩
Same issue here when closing the socket. Any updates?
I investigated a bit, and internally they use code 3001 when the client is told to close the socket, and 3005 when the client closes the connection at their end.
This is not the standard, and should be fixed. Also, the error comes from https://pub.dev/packages/web_socket, so I think this issue should be closed.
Yeah, the issue has been closed in web_socket 0.1.5 – 1000 close code is now allowed.
We should update the docs, because channel.sink.close(status.goingAway)
will give this error.
I have the some problem. web_socket_channel needs to depend on web_socket 0.1.5 if you want to close with 1000.
Hello after upgrading the package from 2.4.0 to 3.0.0 calling close seems to throw (was tested and full working before upgrading) am I missing something ?
For a bit of context the code sends audio data to a server, which returns the transcription First I start the connection :
The error occurs in the close method :
The error :