Users who dismissed their alarm can cause the alarm to ring again if they accidentally launch the AlarmActivity from recent apps long after the alarm was supposed to trigger.
Solution
Add android:excludeFromRecents="true" to me.jfenn.alarmio.activities.AlarmActivity in AndroidManifest.xml
I have modified AndroidManifest.xml locally to include the solution and indeed AlarmActivity won't show in recents anymore. This is also the behavior of AOSP Clock.
Steps to Reproduce
Users who dismissed their alarm can cause the alarm to ring again if they accidentally launch the AlarmActivity from recent apps long after the alarm was supposed to trigger.
Solution
Add
android:excludeFromRecents="true"
tome.jfenn.alarmio.activities.AlarmActivity
inAndroidManifest.xml
Video of what I mean (no audio in this video but it does ring in real life): https://drive.google.com/open?id=11mPhdivZFsaRylrYeRdrjijL6yewFD-s
I have modified
AndroidManifest.xml
locally to include the solution and indeed AlarmActivity won't show in recents anymore. This is also the behavior of AOSP Clock.