Desktop: App name in windows notification system is broken

[nickvergessen]

Running 2.3.3 on WIndows 10
Same issue on my wife's mashine:

The Microsoft.Explorer.Notification.... should say Nextcloud

[arnowelzel]

Happens here too (NC 2.3.3, Windows 10 Pro).

The exact title is:
"Microsoft.Explorer.Notification.{D1E77EBE-CB15-2CF6-9056-49C4D2FAE98F}"

It seems like the client did not register itself properly, so Windows will just generate a title automatically.

[arnowelzel]

Update: it seems only to happen, when the client is started automatically during boot. When I stop it and restart it manually, the notification is labeled properly.

[DominiqueFuchs]

Hey @arnowelzel and @nickvergessen , thanks for reporting this and sorry that this went unnoticed for so long. I just tried to reproduce this issue with the latest stable client (2.6.0) on Windows 10 with autostart enabled and everything displayed as expected when triggering some notifications server-side.

There haas been a bunch of improvements and changes regarding the notification system and logic over the past month. Are you still there, could you report back if this issue is solved for you, too?

[nickvergessen]

Yes, I'm still here (and still employed at Nextcloud :smile: )

Works fine with 2.6 and also I didn't notice it anymore lately, so let's close this and in worst case reopen it, when it happens again.

[arnowelzel]

Yes, I'm still a happy user of Nextcloud :-) and I can confirm that notifications in the current version works correct.