Occasional notification timing or reliability issues
ferdnyc opened this issue · 0 comments
I've noticed the occasional weirdness with mirrored notifications. Particularly when one occasionally gets delayed, for... any of the various reasons that can happen, given the transient nature of the KDE Connect protocol connection.
For instance, I've had GSConnect mute/pause my media player in response to an incoming call notification... for a phone call that happened half an hour previous.
We may need to consider adding some timestamp checking, in the plugins that react to notifications. (Assuming the timestamps in older notifications will actually show that they're out of date.) If a notification is older than a few... well, seconds, actually, then displaying it may still be appropriate, but there's no point in taking other actions based on it.
(I've also had "Ongoing call" notifications stick around indefinitely — as in, I spotted it in the notification list literally days after the actual call. You'd think the notification would be removed when the call ends, but apparently that's not reliable. So, there may be some ways that can be improved.)
Originally posted by @ferdnyc in #1855 (comment)
These issues occurred with a post-#1860 build of GSConnect, which is the same notification code that's in the just-released v58. So, this report can be considered to cover v58 as well, when run in GNOME 46 (as I haven't yet upgraded to 47).