Conversation
|
@olorin99, could you try testing this on your computer and see if you can reproduce the issue? You'll want to set up kunifiedpush if you haven't already. |
|
Could reproduce. This commit seemed to fix it for me. Hopefully it fixes on your end too. |
|
It sort of works, but unfortunately, the notification displays for about half a second before disappearing (while most notifications display for 10 seconds). I'll ask in the UnifiedPush matrix just to see if they have any ideas. |
|
After testing again, it seems like the issue is present, even if Interstellar is open in the foreground. That being, where the first notification will go through, but not subsequent. |
|
Huh that's weird. The application closing shouldn't cut the notification display time. I would think that notification appearance and timing would be controlled by whatever desktop environment/notification daemon you use. Also just tested again and with that change neither the problem with cutoff time or the subsequent notifications not going through are present on my computer. For reference I'm using niri as window manager with the dms shell displaying notifications. |
|
I just disabled all the notification displaying code and replaced it with logs, and everything with UnifiedPush was working correctly, so it must be related to |
|
The logs are coming in consistently every single time, but the actual displaying of the notification is extremely hit or miss. It seems like the app is fine staying open in the background for a little bit after a UP message is received because it still logs subsequent messages just fine. I can even see the "Initializing interstellar" line displayed only once with multiple "UnifiedPush message" lines afterwards. Although, we certainly don't want it running in the background forever, as that ruins the point of UnifiedPush. So anyway, it is definitely an issue with |
|
I was able to reproduce the issue by directly adding |
The Flutter
unifiedpushpackage added support for Linux a few months ago, so now we can finally support push notifications on Linux. I have the UnifiedPush storage using our database instead of the default shared preferences storage.I have things mostly working, but unfortunately, there is an issue where once a notification is received in the background the first time, it will display correctly, but on subsequent notifications, it will no longer work. It seems like the app is staying open in the background and not closing properly after handling the notification.