No notification on connect for highlights/PMs received while disconnected
Steps
- Connect to core
- Disconnect from core
- Not automatic reconnect, but manual disconnect
- Receive highlight/PM that'd usually trigger a notification
- Connect to core, observe results
- Disconnect from core
- Connect to core, observe results
Expected
Quasseldroid shows all pending notifications when connecting after a manual disconnect.
(Optionally, Quasseldroid could show them silently since they existed before connect, but that doesn't really matter. Reconnect notification handling already works well.)
Actual
The first time Quasseldroid receives existing notifications when connecting to the core, those notifications are not shown.
Without making any changes, any subsequent time Quasseldroid connects to the core (e.g. after manually disconnecting then connecting), the old pending notifications are now shown.
Additional
I suspect this has something to do with some unexpected issue inserting notifications into the local notification cache (for tracking if shown or not), since in the past Quasseldroid behaved correctly.
I'd personally vote for showing existing notifications silently on first connect, but I can see a use case for having the first show of existing (already on core, not newly received) notifications be noisy.
Either way, they should be shown in some fashion instead of ignored until a second connect.
Normal priority since this can lead to missing messages if one has a long buffer list and fails to check every one. Can be moved to low priority if desired.