Bug: An alarm - that is not set by user - rings after device is powered on (and unlocked).

[Detective-Khalifah]

Description

Whenever the device is restarted or powered on, an alarm that has not been set by the user rings. This ringing occurs even when there are 0 active alarms on the app. It seems to happen due to AlarmReceiver.kt being triggered - after boot is complete - by the BroadcastReceiver in the AndroidManifext.xml file.

Further testing needed to verify this behaviour on devices that do not support direct boot.

Further read:

• https://developer.android.com/develop/background-work/background-tasks/broadcasts
• https://developer.android.com/reference/android/content/BroadcastReceiver

Screenshots

https://github.com/CCExtractor/ultimate_alarm_clock/assets/58272349/aaf8ac5c-cbc3-4f85-973f-3c0670e5cfb9

[AryanSarafDev]

I have fixed the issue in Issue number #562 @Detective-Khalifah @MarkisDev

[Detective-Khalifah]

I will check it and give you feedback

[Detective-Khalifah]

I think the issue is resolved -- unset alarm no longer rings after boot, @AryanSarafDev.

cc: @MarkisDev