What are you doing in the DeviceActivityMonitor callback functions?

Maybe some more relevant information: all DeviceActivityEvents are defined by tracking categories, not apps or websites. Here is an example of one of the events: DeviceActivityEvent(categories: categories, threshold: DateComponents(hour: 2, minute: 30), includesPastActivity: true)

Update: I've noticed that part of the issue is it seems to be "double counting" usage from Safari. As stated in the previous comment, the events target only category tokens, and not specific app or website tokens. Using the website x.com on Safari for 10 minutes caused the event threshold to fire 10 minutes early - so my hunch is it is counting Safari and the website x.com separately. However, this is likely NOT the only thing that causes the overcounting, since users experience thresholds showing much higher screen time than can be only explained by their Safari usage. But I think this info can help point toward the root cause. Also have submitted a bug report: https://feedbackassistant.apple.com/feedback/15103784

Another Update: for many users, turning off Screen Time completely on their other iOS devices has fixed the issue for them (while "Share Across Devices" was still always turned off). Still for some users, this has not fixed it. And for other users, they never had other iOS devices to begin with but they were still experiencing the issue. So I would assume that this issue has something to do with screen time being shared incorrectly across devices, but still can be experienced without other iOS devices sharing screen time. Also this issue is still happening on iOS 18.

Can an internal dev please address this issue in some way? It was introduced in later versions of iOS 17, still happening in latest version of iOS 18, and many other devs have reported the same issue. This is a core problem with the Screen Time API that should be addressed as it renders the monitoring schedule fundamentally unusable for affected users. Would really appreciate some kind of response from the internal devs, thanks!