user leave action not dispatched in presence when socket disconnect

[rohittailor]

Hi,

I am trying to get channel users and getting it but when user close browser and socket disconnect from server, user leave event is not coming in trackPresence callback and also getPresenceList is returning all users (even when the socket disconnect).

I am tracking channel presence in all clients.

Please let me know if I am missing anything here.

[jondubois]

@rohittailor Is this in a production or testing environment?

Note that if you have two tabs open in the same browser, by default they will share the same session and if you close one, then the user will still be online because they will still have one tab open.

Could you give more specific steps/instructions so that I can reproduce the issue?

Also note that in some edge cases where there is network failure, it's possible that there can be a delay of several seconds before the presence list is updated.

[jondubois]

You can provide an optional presenceInterval option so that it can detect these edge cases sooner; the default interval is 10000 (10 seconds) https://github.com/SocketCluster/sc-stateless-presence/blob/master/index.js#L5 but note that making the interval shorter will use up more bandwidth.

So you can trade efficiency/performance for accuracy.

[rohittailor]

Hi @jondubois ,

Its in my local DEV environment. I have not provided any presenceInterval option so its taking default one.

Two client apps are connected to same server. One is the admin app and another is customer facing. From admin app I am trying to fetch presence of channel (subscribed from customer facing app).

I opened apps in different browsers to make sure session is not shared, but still when I close the browser or refresh it , presence list is not getting updated and trackPresence callback is not getting dispatch. When I try getPresenceList its returning all users.

From socket I can see socket disconnect event when I close the browser but presence is not getting updated.

[rohittailor]

Hi @jondubois ,

Please let me know if you are able to reproduce the issue.

Thanks, Rohit

[jondubois]

@rohittailor I tried to reproduce the issue but couldn't. I found a separate issue which caused an error to be thrown if the client wasn't tracking a specific channel but it worked apart from that.

On the server in worker.js, I add my stateless logic:

scStatelessPresence.attach(this);

Then inside the 'connection' handler, I have this dummy code:

scServer.on('connection', (socket) => {
      socket.on('login', (data) => {
        socket.setAuthToken({
          username: data.username
        });
      });
});

On the front end, I have this:

var presence = scStatelessPresenceClient.create(socket);

var sampleChannel = socket.subscribe('sample');

presence.trackPresence('sample', function (action) {
        console.log('PRESENCE:', action);
});

Then from one tab, I log in with (inside the developer console):

socket.emit('login', {username: 'bob123'});

and in another tab, I log in with:

socket.emit('login', {username: 'alice456'});

Then in the dev console, I also check with:

presence.getPresenceList('sample');

[jondubois]

@rohittailor Let me know if you're doing something different which might be causing the issue.

[rohittailor]

@jondubois Sorry for delay in response. I am currently using SocketCluster version "4.3.2". I sm upgrading to latest version. Will get back if that resolve the issue.

[jondubois]

@rohittailor Could it be that a socket authenticated a second time using a different username? There was an issue there. Fixed in v1.0.7.