Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Server socket id doesn't match client's socket id

See original GitHub issue

For some reason, after upgrading to 1.4.4, the sockets on the server return the socket.id property as /#BA0yIQhFb5R55OnvAAAC but in the client as BA0yIQhFb5R55OnvAAAC.

This inconsistency has broken one of my apps. Am I doing something wrong?

Issue Analytics

State:
Created 8 years ago
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

lucasbiel7commented, Feb 24, 2021

ty @nkzawa @stgogm

0reactions

darrachequesnecommented, Jan 12, 2017

That issue was closed automatically. Please check if your issue is fixed with the latest release, and reopen if needed (with a fiddle reproducing the issue if possible).

Top Results From Across the Web

Socket io not giving the same id in client and in server

The problem is that the id are not the same (you can also see I tried to check the socket.client.id but it doesn't...

Server API - Socket.IO

server.close([callback]) Closes the Socket.IO server and disconnect all clients. The callback argument is optional and will be called when all ...

socket.io emit to specific socket ids : r/node - Reddit

I'm creating a social network site, I want to emit only to all of my friends when I login. user: { friends: User[]...

Create a Secure Chat Application with Socket.IO and React

Create a Chat Server with Express and Socket. ... In this code, {yourClientID} is the client ID that you obtained from the Okta...

SCServerSocket (server, worker) - SocketCluster

The server-side SCSocket object allows you to interact with a matching client-side socket in real-time. It also allows you to subscribe and publish...