Online status issue

[MukeshSherawat61]

Online status not showing team members when they use rocket chat desktop app.

[Gummikavalier]

Has been fixed but not released yet according to #31705

[lovekyleman]

I updated RC instances from 6.6.0 to 6.6.1. The bug isn't fixed

[lovekyleman]

I updated RC instances from 6.6.0 to 6.6.1. The bug isn't fixed

Users online that shows offline and user offline that shows online

[Gummikavalier]

Works on our test RC instance.

Did you remember to do shift-reload on both web clients, and then try switching statuses again?

(That has become a norm for me every time we update RC. There usually is always something loaded into memory in the web client that causes issues.)

[lovekyleman]

It doesn't work on Rocket.Chat iOS app.

[sampaiodiego]

can you guys that are still having the issue describe more about your deployment pls?

• how many rocketchat instances?
• monolith or micro services?
• server specs
• mongodb deployment (3 node replica set? atlas?)
• using change streams? oplog? any special env var?
• what was your previous version where this was working?
• how are you testing it out?
• please fill out the bug report template

the more details the better..

the issue on 6.6.0 was only related to the Web UI (official mobile apps were not affected) not showing the updated status (the status circle was not getting updated), but on page the refresh the status were correct.. if the issue you guys are seeing is different than this, we need to understand what is going on in order to fix it too.

[lovekyleman]

Description:iOS app shows all users always online (6.6.0 and 6.6.1). And version 6.5.3 was good. users offline iOS app shows users offline in real time
Steps to reproduce:

Expected behavior:when user offline it should display offline

Actual behavior:users online forever

Server Setup Information:

Version of Rocket.Chat Server:6.6.1
Operating System:Debian 11
Deployment Method:manually
Number of Running Instances:3
DB Replicaset Oplog:yes
NodeJS Version:14.21.3
MongoDB Version:6.0.13
Client Setup Information

Desktop App or Browser Version:iOS app 4.46.1.57000 ( the latest)
Operating System:
Additional context

Relevant logs:no logs

[Gummikavalier]

I too can confirm presence issue in the iOS client 4.46.1.57000.

Restarting the app or clearing the cache app resets the correct presence information, until it is changed by the user, at which point the user's status goes offline in the app.

Regardless of the selected status by this user, for instance choosing Away changes this user's status into Offline status for the others.

Clearing the app cache under app settings (Clear local workspace cache) did not help with the issue.

[sampaiodiego]

@diegolmello there seems to be an issue with how the mobile app is handling the presence updates.

[diegolmello]

Restarting the app or clearing the cache app resets the correct presence information, until it is changed by the user, at which point the user's status goes offline in the app.

I was able to reproduce that. Going to take a look in a few.

[chotaire]

I'm still facing the same issue with people showing as online (green) even when their devices are turned off since version 6.6.0. I thought it was fixed in 6.6.1, but the problem just re-appeared over the weekend.

[pythys]

The problem is not resolved in 6.6.1, we're still suffering from the same issue

[TimmiORG]

This should be the fix for the issue: #31823
Hopefully there will be a 6.6.2 soon.

[sampaiodiego]

#31823 is actually already shipped on 6.6.1 ..

but there is a follow up fix #31833 that will be shipped on 6.6.2 soon..

[sampaiodiego]

I'm sorry, #31823 is not actually on 6.6.1 .. I'll include it in 6.6.2 along with #31833 today

[chotaire]

When is the docker release coming? And will this revert of changes to presence also fix the notifications issues that people are reporting or is that another basic issue? #31352 (comment)

Btw, also please note that there are currently 7 critical vulnerabilities in the 6.6.1 docker image. https://hub.docker.com/layers/library/rocket.chat/latest/images/sha256-bc953eb5adfd4b06f454b3aa1d7a0af2a7b98f9bdeb7e120b85af780ab5f5bb2?context=repo&tab=vulnerabilities

[sampaiodiego]

When is the docker release coming?

you can already use it from registry.rocket.chat/rocketchat/rocket.chat:6.6.2 .. the Docker official one is coming up today.

And will this revert of changes to presence also fix the notifications issues that people are reporting or is that another basic issue?

some of those notifications are dependent on user's presence, so maybe.. need to understand exactly what is going on to have a proper guess.

[Gummikavalier]

@diegolmello @sampaiodiego Other issues are fixed but there still is one more issue I was able to reproduce with RC 6.6.2:

On one of our RC setups I was not able to get my presence go to offline by closing down the browser that last the session to RC server.
I was checking with another account that it remained online/green.

Finally I did Logout from other logged in locations under my /account/profile. This fixed the status.

The status reacted ok to browser closing and starting until I logged back into the RC mobile client, and chose busy.

At this point the issue with the offline status begun again.

[Gummikavalier]

@diegolmello @sampaiodiego Other issues are fixed but there still is one more issue I was able to reproduce with RC 6.6.2:

On one of our RC setups I was not able to get my presence go to offline by closing down the browser anymore.
(I used another account to check and it remained online/green.)

Finally I did Logout from other logged in locations under my /account/profile, and then I logged out from this last browser session. This fixed the status operation.

After this the status reacted ok to browser closing and starting, until I logged back into the RC mobile client, and chose busy.

At this point the issue with the offline status begun again.

---

Edit: Possibly just having the mobile app open once while closing down the browser session makes the status sticky from there on.

Edit2: Naturally in all testing I closed down the mobile app by swiping it away from the memory of the device. (Even closed down the mobile completely.)

[chotaire]

some of those notifications are dependent on user's presence, so maybe.. need to understand exactly what is going on to have a proper guess.

Tested 6.6.2. -Presence- still broken in the way I can log myself out of the web session and out of the android app and I will still show online to everyone. I would make this guess that only those users continue to show as online who have the Rocket.Chat mobile app installed (Android & iOS).

@sampaiodiego -Notifications- are still entirely broken for my account on both Web and Android. I even deleted cache and relogged on both architectures, absolutely no change at all. Since 6.6.2 didn't fix the presence issue, I still can't know if this is related. I also never get any silent notifications on Android, nothing. On Android, I can't even seem to preview any sounds I would set for a channel or DM, nothing is ever playing, not sure if that is an additional app issue. This notifications problem, which I assume started happening when presence went broken, is soon becoming a 100% showstopper to me. I will be unable to travel with this issue. That's frustrating and I need to fix this asap. Question: On a docker deployment, if nothing else will help, is there a way I can delete my admin user, register with the same username and then link it to all previous conversations? Like change the new user's uuid in a database? As nobody else on that instance suffers from this notifications issue on both Web and Android, I'm guessing I could fix it with a new user, but losing all my conversations is the worst case scenario.

[xcpdq]

I confirm this issue still persists for us even with 6.6.2 version. During these hours it's impossible to have so many people online in our team.

[pythys]

Yup, I also confirm the bug persists in 6.6.2

[danel1]

Confirm, this is still an issue. @sampaiodiego That's some core functionality, which is quite essential. Any update?

[pythys]

We've bumped two releases and the issue still persists for something which should be considered fundamental behavior. I've learned a few lessons here:

• do not upgrade to a new minor / major version until it gets stabilized.
• test deployments as production releases might sometimes exhibit issues.
• keep an eye on critical bugs or issues before upgrading.

Is downgrade possible folks? Did anyone attempt it or are there changes that persisted in the database?

[sampaiodiego]

you can track #31903 to know when the fix for this is released.

[Gummikavalier]

I confirm that the fix is working in RC 6.6.3. Reacts really fast and well to RC mobile app state too now.

Teh huggeth! 🤗