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
Hello, I have the forcenew set to true, however, each time I swap connection from wifi to cell and vice versa, it creates a new socket but without deprecating the previous one. This is on an iOS device. Here is an example of the duplicate. I have tried to call dispose, disconnect, etc on the connectivitity state change but that does not clean up all the duplicates. The list keeps growing on each connectivity change when ssocketio reconnects.
flutter: FINE: 2023-12-28 11:51:54.971210:
socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
The text was updated successfully, but these errors were encountered:
Hello, I have the forcenew set to true, however, each time I swap connection from wifi to cell and vice versa, it creates a new socket but without deprecating the previous one. This is on an iOS device. Here is an example of the duplicate. I have tried to call dispose, disconnect, etc on the connectivitity state change but that does not clean up all the duplicates. The list keeps growing on each connectivity change when ssocketio reconnects.
flutter: FINE: 2023-12-28 11:51:54.971210:
socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
flutter: FINE: 2023-12-28 11:51:54.971210: socket receive: type "ping", data "null"
The text was updated successfully, but these errors were encountered: