You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the details. It seems there is a difference between stopAll (which relies on persistent storage for alarm info) and isRinging (which checks if an audio player with a specific ID is ringing).
When isRinging returns true but getAlarms returns nothing, is your alarm actually playing audio?
Could you please test this scenario a few more times and share the results? More data will help us identify the issue.
@gdelataillade
The notification is not actually playing audio.
My audio is a very short ding- sound, less than a second.
I wait a long time and then debug and isRinging comes out as true.
Alarm plugin version
3.1.4
Describe the bug
Is it correct behavior that calling Alarm.stopAll() makes the notification disappear from the status bar?
Sometimes calling stopAll() doesn't make the notification disappear from the status bar.
So, after debugging, I found a few things.
The isRinging variable appears to be true.
However, all notifications have already ended.
Is this a bug?
The AlarmSettings currently in use.
**DeviceInfo
This only happens on Android.
Does not occur on IOS.
On Android, stopAll() doesn't seem to stop notifications properly.
**Additional
After further testing,
stop(1) correctly removes notification 1.
But stopAll() doesn't work.
The text was updated successfully, but these errors were encountered: