iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

App & System Services General Family Controls Device Activity Managed Settings Screen Time

Created Dec ’25

Replies 27

Boosts 8

Views 4.5k

Participants 11

Hi there,

Starting with iOS 26.2 RC, all my DeviceActivityMonitor.eventDidReachThreshold get activated immediately as I pick up my iPhone for the first time, two nights in a row.

Feedback: FB21267341

There's always a chance something odd is happening to my device in particular (although I can't recall making any changes here and the debug logs point to the issue), but just getting this out there ASAP in case others are seeing this (or haven't tried!), and it's critical as this is the RC.

DeviceActivityMonitor.eventDidReachThreshold issues also mentioned here: https://developer.apple.com/forums/thread/793747; but I believe they are different and were potentially fixed in iOS 26.1, but it points to this part of the technology having issues and maybe someone from Apple has been tweaking it.

Answered by DTS Engineer in 874099022

@nemecek_f

This is a known issue that is currently being investigated.

If you have already filed a bug report for this issue, thank you.

If you have not filed a bug report for this issue we encourage you to do so via Feedback Assistant (https://feedbackassistant.apple.com). For more information on Feedback Assistant, please visit https://developer.apple.com/bug-reporting.

By filing a bug report, you’ll be able to track the issue, update Apple Engineering with additional information, and get notified of problem resolution

Quappi OP

Apr ’26

How are people doing on iOS 26.5?

So far so good, but this happened with the first 26.4 release too: it seemed to be fixed, but then (maybe) something got reverted.

Same: so far so good.

But I’m hesitant to confirm the bug fix haha. As we all know the Screen Time frameworks are quite flaky and bugs come back all the time after a couple of weeks. Or even worse: new regressions.

This time I’m hopeful though because my radar FB18061981 has been updated by Apple indicating that there has been a bug fix attempt for iOS 26.5 beta 1.

So all in all, I think we can be carefully optimistic that this issue has been addressed on 26.5 🤞

Quappi OP

Apr ’26

that's iOS 26.2, iOS 26.3 and iOS 26.4 (3-4 months) of limits automatically activating most mornings without reaching the limit, and this also affects the default Apple Screen Time

Just for the record: it’s been one year almost. The regression was introduced with iOS 26.0 beta 1 in June 2025. I filed a radar about this serious regression the very same week…but did not get any response from Apple until now. Apparently now in iOS 26.5 it’s addressed, but that still takes a month or so to ship to customers.

So 11 months in total to have the bug fix shipped that shouldn't have made it into the public release of iOS 26 at all.

I hope some internal investigation will follow at Apple to prevent a horrible scenario like this from happening again!