iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

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.

Some other details:

  • this looks to happen right when I open my device for the first time (after not using my phone for like 6+ hours)...theoretically there could be a chance that because "iOS is just waking up" (not 100% the case since the phone is on and charging) there's some odd bug where things go wrong
  • using iOS 26.2 before RC seemed to be OK

My hope is that this is just some odd side-effect due to my device state, but if it's not, it's critical for all Screen Time apps to test this & report.

I’m curious what you mean with that. im also sometimes under the impression that my device is cursed when it comes to screen time, because there are so so many bugs. But then again, it’s not just me: we get user reports every day with complaints about bugs related to the Screen Time API.

odd side-effect due to my device state

iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?
 
 
Q