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
There is an issue related to the usage of pingInterval in OkHttpClient. When the WebSocket is closed and this parameter is set, a new socket is promptly opened to perform the next ping. IMHO the ping mechanism should adhere to the lifecycle specified in the Scarlet builder.
To replicate this issue, you can refer to the code provided in the following link and add a lifecycle to the scarlet builder: #70 (comment)
The text was updated successfully, but these errors were encountered:
Hi,
There is an issue related to the usage of
pingInterval
in OkHttpClient. When the WebSocket is closed and this parameter is set, a new socket is promptly opened to perform the next ping. IMHO the ping mechanism should adhere to the lifecycle specified in the Scarlet builder.To replicate this issue, you can refer to the code provided in the following link and add a lifecycle to the scarlet builder:
#70 (comment)
The text was updated successfully, but these errors were encountered: