[GH-ISSUE #1591] Android: Notifications may be missed in certain (rare cases) #1119

New issue

Closed

opened 2026-05-07 00:30:23 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:30:23 +02:00

Owner

Originally created by @binwiederhier on GitHub (Feb 3, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1591

🐞 Describe the bug

The since= parameter is kept in memory only as AtomicBool, and so after an app restart or after a new subscription is added, the parameter is reset to null/none. We should use the lastNotificationId instead.

💻 Components impacted
Android

💡 Screenshots and/or logs


2026-02-03 18:22:17.468  4499-4499  NtfyWsConnection        io.heckel.ntfy.debug                 D  10.0.2.2:2586/bla,dasdasdasd (gid=2): Opening http://10.0.2.2:2586/bla,dasdasdasd/ws?since=none with listener ID 4 ...

Originally created by @binwiederhier on GitHub (Feb 3, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1591 :lady_beetle: **Describe the bug** The `since=` parameter is kept in memory only as AtomicBool, and so after an app restart or after a new subscription is added, the parameter is reset to null/none. We should use the `lastNotificationId` instead. :computer: **Components impacted** Android :bulb: **Screenshots and/or logs** ``` 2026-02-03 18:22:17.468 4499-4499 NtfyWsConnection io.heckel.ntfy.debug D 10.0.2.2:2586/bla,dasdasdasd (gid=2): Opening http://10.0.2.2:2586/bla,dasdasdasd/ws?since=none with listener ID 4 ... ```