Open muratbayan opened 1 year ago
JIRA ticket: https://mattermost.atlassian.net/browse/MM-54736
I would like to add that I have recently had the same problem with multiple installations of the Mac app. App version 5.9.0, server version 9.10.1. No improvement with new installation, update, clear cache. The status is correctly determined/displayed in the browser. In the app, the user is always shown as offline after a reload.
@laborb-sb As a sanity check, the user isn't set to Offline manually are they? If you manually set them to Online and refresh does the same issue occur?
Correct.
@laborb-sb Is it only one user that's affected? Or is this happening to multiple users?
To multiple user, but not every user. Let me try to get a more systematic overview.
I am observing the same problem as @laborb-sb but on two different Windows 10 machines, since the upgrade to version 5.9.0. After starting the desktop client the user is offline. When setting it manually to online, then restarting the client the users presence will again be set to offline.
Looks a bit like this issue (github) to me. I can also reproduce it in Firefox and Chrome. Sometimes the presence is online after login, but after one or two page reloads the user appears offline again.
Looks a bit like this issue (github) to me. I can also reproduce it in Firefox and Chrome. Sometimes the presence is online after login, but after one or two page reloads the user appears offline again.
This is likely the case, that issue we'll be looking at in the coming months as part of an overview of the status system
Before you file a bug report
Mattermost Desktop Version
5.4.0
Operating System
Windows 10
Mattermost Server Version
7.10
Steps to reproduce
Expected behavior
Observed behavior
Log Output
Additional Information
Discussion thread on the Community Server here
Skype for Business clients on the same workstations have the expected behaviour of switching the status to away/offline. Issue does not occur via the webapp (Chrome)
Trying on personal Windows workstations does not reproduce the issue.