Calling up device notifications ends alarm signal

[WebworkrNet]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 14, One UI 6.1

Affected device model

Samsung Galaxy A13 5G (SM-A136B)

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. An alarm is set.
2. The alarm time is reached.
3. The app triggers an acoustic alarm.

Expected behavior

The alarm signal should only be changed using the "Snooze" and "Cancel" buttons.

Actual behavior

Calling up the device notifications by swiping from top to bottom immediately ends the audible alarm.

Screenshots/Screen recordings

No response

Additional information

No response

[naveensingh]

It seems this bug/feature can also be reproduced by rotating the device.

[jankusanagi]

I wonder if this is the same issue, but in my case the alarm gets completely dismissed if I press the "back arrow" button on the phone, which is very easy to do accidentally.

[naveensingh]

I wonder if this is the same issue, but in my case the alarm gets completely dismissed if I press the "back arrow" button on the phone, which is very easy to do accidentally.

Is the alarm ringing in full screen when you do this? In any case, it'll be fixed by #133

[jankusanagi]

Is the alarm ringing in full screen when you do this?

It is.

In any case, it'll be fixed by #133

That's very cool, thank you!