iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

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

Created Dec ’25

Replies 20

Boosts 6

Views 2k

Participants 8

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

Boost

kgaidis OP

Yes, same here. iOS 26.4 looking stable so far. Thank you for the fixes Apple devs 🙏

kgaidis OP

Unfortunately, just got the latest 26.4 beta 3(?) that released yesterday and am again getting the problem.

iOS 26.4 (23E5223f)

ksoma OP

I've also confirmed that the same issue occurs on 26.4 beta 2 and beta 3.

hydro_yolask OP

11h

Thanks for the updates, we’re seeing the same kind of “misfire / immediate threshold reach” behavior reported by our users as well (blocked even when they haven’t used the app yet), so it’s helpful to know it’s still reproducible on the latest 26.4 betas.

Could you share how you reproduce it reliably?

What schedule / threshold configuration are you using?
Does it happen right after starting monitoring, after a reboot, or after an OS update?
Any pattern around downtime / always-allowed / exempt lists?
Device model + exact iOS build (e.g., 23E5223f) when it reproduces?

Any concrete steps would be greatly appreciated.

ksoma OP

Unfortunately, I don't have a way to reproduce this 100% reliably, but here are the steps that most often trigger it:

Set up the usage limit first — configure a usage time limit of 1 minute or more before connecting the charger.
Then plug the iPhone into a charger — the issue tends to appear shortly after charging begins.

That said, it seems to only trigger once per day — I haven't been able to get it to fire a second time on the same day.

Device model: iPhone 16
iOS build: 23E5223f