@Gordon yeah, I have noticed some inconsistencies with the way notifications are sent to devices:
Notifications are handled in the NotificationListener - this includes both sending and handling the dismissals. The NotificationListener keeps a lookup queue that maps notifications by ID.
However, SMS are sent by the SMSReceiver. This gets the SMS event directly, which does not map to a notification on the phone. When trying to dismiss it from NotificationListener, it will fail.
Additionally to this, I don't think we're setting the notification ID correctly when creating the NotificationSpec, so it's always incrementing, even for updates of the same notification.
I did not have too much time to look into this yet, but it's definitely a bug on Gadgetbridge that's affecting all devices.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Gordon yeah, I have noticed some inconsistencies with the way notifications are sent to devices:
Additionally to this, I don't think we're setting the notification ID correctly when creating the NotificationSpec, so it's always incrementing, even for updates of the same notification.
I did not have too much time to look into this yet, but it's definitely a bug on Gadgetbridge that's affecting all devices.