iOS 26 regression: `DeviceActivityEvent`: `eventDidReachThreshold` called immediately (instead of waiting till threshold is reached)

Accessibility & Inclusion General Accessibility

Created Nov ’25

Replies 17

Boosts 4

Views 5.0k

Participants 4

Hello Albert!

I am experiencing some strange bugs around DeviceActivityEvents (part of the DeviceActivity framework) on iOS 26 / iOS 26.1 / iOS 26.2 beta:

When creating a DeviceActivityEvent we can assign a threshold and applicationTokens.

The idea is, that after the user has spent said threshold on said apps, eventDidReachThreshold() is called.

The property includesPastActivity is set to false.

On iOS 26 however, it happens (quite reliably after updating to a new beta seed) quite often that eventDidReachThreshold() is called immediately (after a couple of seconds) instead of waiting for the threshold to be met.

Is anyone else seeing similar issues on iOS 26 / iOS 26.1 / iOS 26.2 beta?

Only workaround I have found is to ask users to revoke and re-grant Screen Time permissions. This only holds for about two weeks though or at most until the next iOS 26 beta update is installed, so it is not a permanent solution unfortunately.

Feedback (incl. sysdiagnoses and sample project) is filed under:

FB18061981
FB18927456

One of our users has filed their own feedback request as well:

FB20817853

Thanks a lot for any help on this!

Boost

DTS Engineer OP

Apple

@tsusa Thanks for the post.

Unfortunately we do not provide estimates for our releases, however you can see that iOS 26.5 is now a release candidate since May 4. with Build 23F75.

Hope this is helpful to you.

Albert   Worldwide Developer Relations.

Quappi OP

10h

Can confirm as well that for the past two weeks, it seems to be behaving well.

Would you happen to know when the newest iOS shipping to users?

That’s great to hear!

Historically, after a Release Candidate of a beta has been released, it only takes one or two weeks till the final release.

So could be something like Monday the 11th or 18th…