No Desktop Notification on Win10/11 prior to starting once

Troubleshooting
1

Summary
No new message notification on Windows 10/11 using Desktop Client until the client is opened once

Steps to reproduce

  • Install and configure Desktop Client 5.9.0 on Windows 11 x64 (fully patched), make sure the client is started on user login
  • reboot PC, login, but do not open Mattermost
  • have a collegue to send a message

Expected behavior
a popup should be displayed that a new message has arrived

Observed behavior
no new message message is displayed. This issue is reproducable on all systems here.

Once the desktop client has been started and minimized again, the notification arrive.

How can I troubleshoot this issue?

2

Hi @SigPam, the MM client needs to be open/logged in for notifications.

Is it your expectations that the client runs as a service in the background (system tray icon showing running) and then notifications would come through even if the app was not opened?

Is this behaviour different to earlier versions on your systems?

1 Like
3

The Desktop client already runs in the background, with the icon showing in the task bar.

My expectation is that I always get a New Message notification when a new message arrives. At the moment, the New Message notification is only shown if I have opened the Desktop client once after the automatic startup during windows login.

In other Words:

  • boot machine, log in → Autostarts Desktop client (with auto-login) → no notification
  • open client once, close it (back to task bar, keeps running in background) → New Message notification ok.

To me, it looks as if the client startup is not complete until I first open the client software once.

reproducable on all my office PCs, worked once in the very far past, cannot reproduce old versions.

I’m willing to invest my time in this issue by

  • collecting logs and traces
  • doing network packet captures
  • installing debug versions.

But I cannot compile source code myself.

4

Thanks for the follow up.

So this is new behaviour on 5.9? (i.e. you saw the expected behaviour on 5.8 or older?)

1 Like
5

No.

I’ve seen this in the most recent version (5.5.3? 5.8.3?) as well

Oh, got you. I meant: I cannot recreate the old client version, because I always keep current. But I have seen the issue in older versions as well. I’m living with the issue for at least a year now.

6

Thank you!

I will discuss with the team and feedback.

1 Like
7

Thank you very much.

8

Hey @SigPam wanted to let you know the result of an internal chat. So indeed expected behaviour is that until you open the client notifications are not enabled.

Would you be willing to open a feature request on GitHub so we can review and add to the backlog (I think its a good change you raise).

Thx