Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

warn - client not handshaken client should reconnect #69

Closed
sefasenturk95 opened this issue Jan 12, 2013 · 11 comments
Closed

warn - client not handshaken client should reconnect #69

sefasenturk95 opened this issue Jan 12, 2013 · 11 comments

Comments

@sefasenturk95
Copy link

When i disconnect from my socket i get this error warn - client not handshaken client should reconnect in the socket, i don't know why and where that error comes from? Can someone explain to me how i can solve it? Thanks in advance.

@pkyeck
Copy link
Owner

pkyeck commented Jan 13, 2013

when does this warning come exactly?
at first glance, it sounds maybe like a warning from SocketRocket ... but I've never seen this before.

@sefasenturk95
Copy link
Author

The warning comes when i call in [socketIO disconnect]

On 13 jan. 2013, at 09:08, Philipp Kyeck [email protected] wrote:

when does this warning come exactly?
at first glance, it sounds maybe like a warning from SocketRocket ... but I've never seen this before.


Reply to this email directly or view it on GitHub.

@sefasenturk95
Copy link
Author

Well i think i know a solution but i do not know how to apply it in my code, what i'm thinking about is this:

I have multiple views where i need a socket IO connection, what i do now is when the user changs from a view in the void view will disappear i call in the function [socketIO disconnect]; and when the other view appears i call in the void view will appear and establish a new connection.

Isn't it possible to connect to the socketIO once but have the variable available in all your view's? I think that will solve my problem. Thanks in advance.

@sefasenturk95
Copy link
Author

No One?

@funkyboy
Copy link

I think a singleton is what you want

@heiko-s
Copy link

heiko-s commented Jun 8, 2013

This warning appears on the server and not on the client. Whenever I call socket.disconnect() in iOS, the disconnect-event on the server is raised correctly, but the iOS app still keeps polling - thus causing the warnings.

As long as the iOS app keeps running after that, the server log gets flooded with warnings (client not handshaken client should reconnect & transport end (error)). Seems like XHR-Polling keeps running forever.

Node 0.10.5
Socket.io 1.2.18
Transports: XHR-Polling only

@ngzhongcai-zz
Copy link

Hi Helko,

I ran into the same error "warn - client not handshaken client should reconnect" upon issuing [socketIO disconnect] command on iOS.

But I am unable to detect disconnect-event on the server, as in below is not triggered.
socket.on("disconnect", function() {
console.log(socket.id + " DISCONNECTED");

Im on the latest node and socket.io with XHR polling

@alexleutgoeb
Copy link

Experiencing the same problems with xhr-polling, anyone got a fix for this?

Thanks,
Alex

@alexleutgoeb
Copy link

Ok, got to fix this with changes from #109, hopefully this one gets merged in near future. 👍

Alex

@heiko-s
Copy link

heiko-s commented Jul 16, 2013

Excellent, works for me too. Thanks Alex.

@pkyeck
Copy link
Owner

pkyeck commented Jul 18, 2013

merged in v0.4.0

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

No branches or pull requests

6 participants