Skip to content

[bug] Notification queue perpetually pings user after reconnecting

Fixed @0xd0.cc opened this issue 2 replies Locked
  1. @0xd0.cc Bluesky reported

    Type
    Bug report
    Area
    Reroute app
    Platform
    Linux
    Version
    0.3.0-rc.8

    Notification system issues a "ping" sound and pushes a notification to the system notification tray per message, however, starting from T2, it also queues every message that was not able to be retrieved during a period where the user was offline (such as during a system sleep state, or after losing internet access for a period of time) while the app process itself is running, this causes the notification system to start pinging every single message that is retrieved and proceedurally queued, causing in my case a 4 hour nap to turn into around 100+ pings to summon out of nowhere. Steps to reproduce: - have friends who talk often without you (first part hard, second easier actually) - leave reroute running in the background/or simply minimised - put system to sleep or disconnect from the internet for a period of around >5 minutes - wake/reconnect system - messages will begin to be retrieved and as they are retrieved, they will be queued to be pushed to the system's notification tray alongside playing a sound on every push - if your friends talk enough this is terrible Expected: + using the methodology used by Discord, app should solely push missed messages onto the notification tray without any application-side sound being played and/or system-side notification sound (ie, silent notification). + using the Telegram methodology, app should cut off the amount of notification sounds it will use (Telegram uses around 4) before silencing any further message in the queue Actual: ear hurt

  2. @nocarrier.fail changed the status to Confirmed

  3. @nocarrier.fail set the labels to notifications, bug

  4. can confirm this is the case on macOS too, and most likely Windows. This will be fixed in the next release.

  5. @nocarrier.fail changed the status to Fixed

  6. @nocarrier.fail locked this issue; only admins can reply

Sign in with a Bluesky or fediverse account to reply. To confirm that you can reproduce this issue, reply with your platform and version.