AlarmKit - Behaviors when dismissing alarms

Question

Created 1w

Replies 2

Boosts 0

Participants 2

Hi Team,

We've been developing our application with the fairly new AlarmKit. We are using the stopIntent to run some quick logic when the user stops the alarms.

The stopIntent is a LiveActivityIntent and works well when the user presses the button the dismiss button on the alarm.

But unfortunately we've realized some interesting behavior in the following two cases:

In case the alarm fires while the user has unlocked their screen and they do things on the screen, the alarm is dismissed (and stopped), but the stopIntent is not executed.
In case the alarm fires while the user has unlocked their screen and they swipe up the Live Activity banner, the alarm is also dismissed (and stopped), but again the stopIntent is not executed.

I've tried to look up for some information, but could not find anything meaningful for this specific case. We're wondering if that is something that is planned to get fixed in the future, or maybe there's a workaround.

We've tried also alternative - listening to alarm updates via the AlarmManager, but we are not very eager to create listener task for it, also the alarm state does not provide updates for dismissed.

Thanks!

Boost

Answer 1

bgeorgiev122 OP

1w

PS: According to the AlarmKit FAQ (https://developer.apple.com/forums/thread/797158) the stop intent should work also when the user is swiping or pressing the power button, but it seems it doesn't. So this is an issue and is reproducible in iOS 26.2.1.

0

Answer 2

DTS Engineer OP

Apple

1w

Thanks so much for the post, very interesting on those 2 points:

In case the alarm fires while the user has unlocked their screen and they do things on the screen, the alarm is dismissed (and stopped), but the stopIntent is not executed. In case the alarm fires while the user has unlocked their screen and they swipe up the Live Activity banner, the alarm is also dismissed (and stopped), but again the stopIntent is not executed.

I never seen that issue on AlarmKit. Very interested to see if you can reproduce that in a simple focused sample you can share here?

Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project.

Albert Pascual   Worldwide Developer Relations.

0