iOS 26.2 (23C55): DeviceActivity eventDidReachThreshold fires with 0 Screen Time minutes

On iOS 26.2 (23C55), DeviceActivityMonitor.eventDidReachThreshold fires intermittently for a daily schedule (00:00–23:59) even when iOS Screen Time shows 0 minutes for the selected apps that day. This causes premature shielding via ManagedSettings.

Environment: iPhone 13 Pro Max, iOS 26.2 (23C55). Event selection: 2 apps. Threshold: 30 minutes. Multiple TestFlight users report the same behavior across various app selections and thresholds. Intermittent (~50% of days); sometimes multiple days in a row. Not observed in testing prior to iOS 26.2.

Evidence: sysdiagnose + Screen Time screenshots (with 0 screen time on selected apps) + unified logs show UsageTrackingAgent notifying the extension that “unproductive from activity daily reached its threshold,” followed immediately by ManagedSettings shield being applied (extension reacting to the callback).

Filed Feedback Assistant: FB21450954.

Questions: Are others seeing this on 26.2? Does it correlate with restarting monitoring at interval boundaries or includesPastActivity settings?

Update: Found a possible reproduction pattern correlated with plugging the device into power. Reproduced again on a device with no other Screen Time/blocker apps installed besides my own. Attached a second sysdiagnose in my feedback: FB21450954.

Observed behavior: DeviceActivityMonitor.eventDidReachThreshold fires even though iOS Screen Time shows 0 minutes for the selected app that day (verified in Settings > Screen Time), and my extension applies ManagedSettings shielding immediately after the callback.

Possible repro pattern:

  1. iOS 26.2 (23C55). Daily schedule 00:00–23:59. Threshold: 30 minutes. Selected app: NHL.
  2. Do not open the selected app(s); leave device idle/locked for hours (0 usage).
  3. Plug the device into power while it remains locked/idle.
  4. Within minutes, eventDidReachThreshold fires despite 0 Screen Time minutes.

Related thread that seems similar: https://developer.apple.com/forums/thread/809410

Hello,

we have reported this concerning bug with the first beta of iOS 26 in June 2025.

Apple has not yet addressed this bug, neither do they have acknowledged that anyone has taken a look at it.

I believe this is yet another confirmation that Apple is not interested in maintaining the Screen Time framework – it’s now in a state where it’s barely usable to build stable apps.

here are my feedback number for reference:

  • FB18927456
  • FB18061981

feel free to cross reference those in your feedback reports!

iOS 26.2 (23C55): DeviceActivity eventDidReachThreshold fires with 0 Screen Time minutes
 
 
Q