Can you reproduce this bug on the Microsoft Teams web app (https://teams.microsoft.com)?

No

Describe the bug

I've noticed inconsistent and redundant notification behavior in teams-for-linux on GNOME. Compared to the Teams web version (which works perfectly), the app's notification logic seems to mismanage the message payload after the initial trigger.

What package are you using?

deb

Version

2.7.8

Reproduction steps

1. Launch teams-for-linux.
2. Receive the first message from a contact.
3. Receive subsequent messages from the same or different contacts.

Actual behavior

1. On the first message: The system triggers two separate notifications simultaneously: one showing the unread count/sender (e.g., (1) Name) and another showing the actual message content.
2. On subsequent messages: The notifications no longer show the message content. They only display the unread count/sender (e.g., (2) Name).
3. Group Chats: The notification title incorrectly defaults to the window title currently "active" or "focused" within the teams-for-linux internal state, rather than the actual Group/Sender name.

Expected Behavior

First message: Only one clear notification containing the sender's name and the message snippet should appear.

Subsequent messages: Each new message should still trigger a notification with the actual message content, not just the unread count.

Context: Notification titles should accurately reflect the source (Group Name or Sender) regardless of which tab is active in the app.

Debug

ELECTRON_ENABLE_LOGGING=true teams-for-linux --logConfig='{"transports":{"console":{"level":"debug"}}}'

Additional context

This issue occurs while using the electron notification method on GNOME/Wayland. It seems like the app is failing to update the notification body for any message following the first one, or it's incorrectly prioritizing the window title over the message metadata.