iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

Question

Created 3w

Replies 5

Boosts 1

Participants 3

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.

Boost

Answer 1

kgaidis OP

3w

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.

0

Answer 2

Quappi OP

3w

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

0

Answer 3

kgaidis OP

1w

got it again:

today it was all the limits once more
few days ago it was just some of the limits

the behavior is the same:

first device pick up of the day (didn't even open the app), and immediately limits get activated

I'm not sure if this is any different than the bug here: https://developer.apple.com/forums/thread/793747

BUT I only started getting THIS specific behavior in 26.2 RC...so maybe it is new?

0

Answer 4

kgaidis OP

1w

Just got a user email from iOS 26.2 that looks like this bug

(Again, I'm not sure if this is any different than the bug here but sounds different due to the explicit start on iOS 26.2 and that its strictly a beginning-of-the-day-thing: https://developer.apple.com/forums/thread/793747)

0

Answer 5

SaulD18 OP

4d

Confirming a very similar issue on iOS 26.2 (23C55).

In my case, DeviceActivityMonitor.eventDidReachThreshold fires when iOS Screen Time shows 0 minutes for the selected apps for that day, and ManagedSettings shielding applies immediately after the callback. It’s intermittent (some days no occurrence; other times multiple days in a row) and often happens after the device has been idle/locked for hours. However, I haven’t personally seen it specifically on first device pickup / first unlock yet.

I filed Feedback Assistant with sysdiagnose + Screen Time screenshots + log excerpt showing UsageTrackingAgent notifying the extension that the event reached threshold: FB21450954.

Quick questions to help narrow this:

Do you also see this on a device with no other Screen Time/blocker apps installed?

Are you restarting monitoring at interval boundaries (e.g., midnight) or setting includesPastActivity explicitly?

Hopefully Apple can correlate FBs and confirm a 26.2 regression.

1