Skip to content

update 1.3.7 to 1.4.5 stop sending messages to roms #2451

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

Closed
diegoug opened this issue Feb 18, 2016 · 6 comments
Closed

update 1.3.7 to 1.4.5 stop sending messages to roms #2451

diegoug opened this issue Feb 18, 2016 · 6 comments

Comments

@diegoug
Copy link

diegoug commented Feb 18, 2016

Hello, I have a problem with socket.io update version 1.3.7 to 1.4.5 and stop sending messages to the rooms, you know what might have happened?

My code is very simple, it is only that:

// socket to room, using roomKey
socket.join(roomKey);
// room emmit
this.io.to(roomKey).emit(channel, message);

But when I want to send a message by a room in particular nothing happens, and if I go back to version 1.3.7 works again, you know it can be?

@CharGomez
Copy link

Same happens to me, any clue ? Thx.

@svarunan
Copy link

I too have this issue after new update.
on server side socket.id gives me /#LF6L4-bVXD4u3fT9AAAA
on client side its LF6L4-bVXD4u3fT9AAAA
'/#' creates all new problem now.
only io.emit works bit io.sockets.connected returns ["/#LpjTrYgEzpl2wbi2AAAB"]

Team, Please help us get a workaround or give a solution to this.

@oliversalzburg
Copy link
Contributor

We had a similar issue that was primarily caused by this change: #1956

@jcsla
Copy link

jcsla commented Mar 5, 2016

I had same issue.. plz help.

@dottodot
Copy link

Same here with 1.4.6, not used socket.io in a while and thought I was doing something wrong, turns out rooms don't work at all as downgrading to 1.3.7 works as documented.

@darrachequesne
Copy link
Member

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).

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

No branches or pull requests

7 participants