Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two different socket instances share same "path" event when setPath() is defined #365

Open
thapliyal128 opened this issue Feb 23, 2024 · 2 comments

Comments

@thapliyal128
Copy link

 _socket = SO.io(
      SocketConstants.baseUrl,
      SO.OptionBuilder()
          .setTransports(['websocket'])
          .setPath(SocketConstants.path)
          .disableAutoConnect()
          .disableMultiplex()
          .setReconnectionAttempts(999999)
          .setReconnectionDelayMax(5)
          .setReconnectionDelay(1)
          .build(),
    );

    _customerChatSocket = SO.io(
      SocketConstants.baseUrl,
      SO.OptionBuilder()
          .setTransports(['websocket'])
          .setPath(SocketConstants.path2)
          .disableAutoConnect()
          .disableMultiplex()
          .setReconnectionAttempts(999999)
          .setReconnectionDelayMax(5)
          .setReconnectionDelay(1)
          .build(),
    );

Here in the opts of _customerChatSocket the path remains the same as the first one , i cannot connect to a different socket please help .
The paths of the both of the sockets remain the same

@thapliyal128
Copy link
Author

Also , when i added forcenew connection , upon connecting to the second socket I cannot send or recieve data from the first socket , please help , Thank you

@jumperchen
Copy link
Member

Please provide the following information:
• The version information of the Client and the Server
• The test environment information for Flutter Android, IOS, Web, or Dart Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants