Unable to stop automatic reconnection attempts

[solofx]

I've got some code that establishes a connection to my socket.IO server, which works perfectly well and allows messages to transit back and forth. The connection is established with auto-reconnection enabled for fault tolerance.

void connectToSocket() {
  IO.Socket socket = IO.io(socketUrl,
    IO.OptionBuilder()
      .setTransports(['websocket'])
      .enableAutoConnect()
      .enableReconnection()
      .build()
  );

}

I have functionality within my application for the user to change the connection URL to switch servers. When this happens, I need to disconnect the existing connection, prevent any re-connection attempts and establish a replacement connection.

I've tried calling various methods to terminate the existing connection, however the reconnection attempts persist in the background, even once the replacement connection has been established. For example:

socket.disconnect();
socket.close();
socket.clearListeners();

connectToSocket();

So far the only way to effectively stop the connection attempts is to terminate the application, which seems a little extreme. Am I missing something or is this expected functionality? If so, does an approach exist to stop an automatically reconnecting socket instance?

My version of the socket.io client is "2.0.3"

[Priyantha-Kingslake]

use dispose to clear all listeners.

Disposes the socket manually which will destroy, close, disconnect the socket connection and clear all the event listeners. Unlike [close] or [disconnect] which won't clear all the event listeners

@ since 0.9.11

[solofx]

Thanks for the reply. I've tried calling the dispose method in place of my existing close/disconnect usage but the behaviour remains unchanged.

In my test I have set the socket.io server URL to be purposely incorrect which results in repeated connection timeout debug messaged - as expected. Now, when changing the URL from within the app and triggering a new connection, the correct connection is established and everything works fine, however I can still see the connection timeout attempts occurring in the background which suggests that the previous socket object has indeed not been destroyed.

[zjianpeng]

Thanks for the reply. I've tried calling the dispose method in place of my existing close/disconnect usage but the behaviour remains unchanged.

In my test I have set the socket.io server URL to be purposely incorrect which results in repeated connection timeout debug messaged - as expected. Now, when changing the URL from within the app and triggering a new connection, the correct connection is established and everything works fine, however I can still see the connection timeout attempts occurring in the background which suggests that the previous socket object has indeed not been destroyed.

I have encountered the same problem as you, and I think the reason is that every time a new connectoSocket is called, a new instance is created, while enableMultiplex is enabled by default. I have looked at other issues and found that using enableForceNew can solve the problem by creating a new instance every time, or a better solution is to ensure that the instance is only created once

[xiaxinqing]

@solofx 我也有类似的需求，在用户切换账号时，需要断开连接，然后根据登录用户重新连接。经过尝试 我找到了一种行之有效的方法，并且已经应用到APP中，它很有效。希望你能看懂中文，并帮到你。
首先断开连接 --> 然后延迟根据token重新连接 （这只是一个例子）
断开连接代码：
void disconnect() { if (socket != null) { socket!.dispose(); socket!.destroy(); isConnected = false; _stopHeartbeat(); socket = null; print("Socket已完全清理"); } }
链接代码：
Future.delayed(const Duration(milliseconds: 100), () { initSocket(token); });

void initSocket(String token) { this.token = token; connectionManager.initConnection(token); messageSender = SocketMessageSender(connectionManager.socket!); _setupSocketListeners(); }

void initConnection(String token) { isShowLoading = true; socket = IO.io( EnvConfig.instance.socketConfig.socketServerUrl, IO.OptionBuilder() .setTransports(['websocket']) .enableAutoConnect() .setReconnectionDelay(EnvConfig.instance.socketConfig.reconnectionDelay) .setReconnectionAttempts(EnvConfig.instance.socketConfig.reconnectionAttempts) .setPath(EnvConfig.instance.socketConfig.socketPath) .setAuth({'token': token}) .build(), ); _setupConnectionListeners(); socketStatusEventHandler .notifySocketStates(currentSocketState = SocketState.connecting()); socket!.io.autoConnect = true; socket!.io.reconnection = true; socket!.connect(); }