Issues when re-enabling alarms for current day

[ascpial]

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

GrapheneOS 2024123000 (Android 15)

Affected device model

Pixel 6a

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Create an alarm for tomorrow (e.g. 8AM when setting it after 8AM)
2. Wait for the alarm to fire and dismiss it (the alarm is now disabled) (e.g. next day at 8AM)
3. Wait until next day, before the time set on the alarm and enable the alarm (e.g. enable it after midnight)

(I'm aware this issues spans over multiple days)

Expected behavior

The alarm is set to sound the next time the schedule is reached, in this example 8am the same day when setting it up after midnight and before 8am.

Actual behavior

The alarm is set to sound the next day, since it was initially set to sound the next day.

However, that's not what I wanted to do: I wanted the alarm to sound as usual the “next day” (after I slept), i.e. the next time it's 8am. This is what usually happens when I set my alarm before midnight, but not when enabling it after midnight.

What's strange is that clicking on the alarm to set it and validate activates the alarm for the correct time.

Screenshots/Screen recordings

No response

Additional information

This problem may seem insignificant, but it appears as soon as you reactivate an alarm, sometimes before, sometimes after midnight. I must have missed 4 or 5 alarms in the last two weeks because of this problem: when I go to bed after midnight, I don't pay attention to the toast displayed by the application to indicate the time remaining. (In these cases, it wasn't dramatic because I didn't need to get up early, but it has been more problematic).

Interestingly, this problem is linked to the fact that non-recurring alarms have an attached day, which is not the case in other clock apps I've used in the past, notably Apple's app for iOS. For this app, alarms that activate once only indicate an hour, not a day.

Please don't hesitate to ask for clarification, as I may have been unclear.

[ascpial]

I found a related issue in the old simple clock repository: SimpleMobileTools/Simple-Clock#459

[rafael-alcantara]

I have experienced the same problem with the same app version from f-droid.

I enabled an alarm I use only from time to time, but I did it after midnight. The info box appeared stating that it would fire in one day plus, and I thought that would be a bug in the displayed info. The alarm did not go off in yhe morning.