In some situations the socket is unidentified when registering, there seems to be a timing issue that does not allow for the token to be registered via the handshake on the socket io remote protocol.
It can be easily replicated by forcefully making the identify request wait for 3 seconds before replying, the client still sends the registering requests despite not having received confirmation from the server that is allowed to do so, causing an error.
In some situations the socket is unidentified when registering, there seems to be a timing issue that does not allow for the token to be registered via the handshake on the socket io remote protocol.
It can be easily replicated by forcefully making the identify request wait for 3 seconds before replying, the client still sends the registering requests despite not having received confirmation from the server that is allowed to do so, causing an error.