You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the suggestion! Unfortunately, not quite — WebSocketChannel.ready is helpful during the connection phase, but in my case, I need to check the state of an already established connection before calling _channel!.ready. Previously, I used _channel?.innerWebSocket?.readyState to determine whether the socket was still connected or not, especially in situations where the connection might have been dropped silently.
Is there an equivalent way to get the current readyState in 3.0.1? Here's a quick example of how I was using it:
I want to upgrade the package from
2.4.0
to3.0.1
, any idea how can I accessreadyState
anymore?earlier I was doing
The text was updated successfully, but these errors were encountered: