Open ElegantSoft opened 2 years ago
which version are you using?
@jumperchen The latest version After debugging I found the issue was I create the connection 2 times so when I close connection it closes 1 connection. you must handle that.
Any updates i faces the same in version 2.0.0
For anyone looking at this, there is a flaw in the design of the baseline io command. See the comment below.
When logging out, even when you clear and dispose of the listeners and socket, the underlying library keeps a cache of the instance you connected to. So the other parts of your query are pretty much ignored.
You need to use the .enableForceNew()
on the connect, as you can see below in my code, or clear the cache upon logout.
or
For anyone looking at this, there is a flaw in the design of the baseline io command. See the comment below.
When logging out, even when you clear and dispose of the listeners and socket, the underlying library keeps a cache of the instance you connected to. So the other parts of your query are pretty much ignored.
You need to use the
.enableForceNew()
on the connect, as you can see below in my code, or clear the cache upon logout.or
You are a life saver, thank you for this response. My backend was getting same query params again and again on each connection causing weird behaviour. This fixes the issue
Hello, I am using socket.io and when user logout I call
I use websocketService class and use it with getIt
after calling logout function the app keeps handle sockets and doesn't clear listeners