I have not. My experience with Feedback Assistant has been poor, none of my bug reports ever get any replies. I simply avoided using @AppStorage variables in the DeviceActivityMonitor extension functions. This seemed to help at first, but have started breaking again with the release of iOS 17.2 without the use @AppStorage. I suspect it may be caused by any use of User Defaults at all. How does your app read / write data in the extensions?

Seems like this happens when event thresholds are two close together. I have some thresholds that are an hour apart that usually deliver normally, however I have some that are ten minutes apart that recently get delivered together consistently.

Another Update: When troubleshooting with an affected user, after turning on "Share Across Devices," the screen time shown in Settings matched exactly the screen time indicated by the DeviceActivityEvents. Previously the user had this setting turned off, but events were still firing for thresholds triggered from her other devices. This helps to confirm my hypothesis that DeviceActivityMonitor is tracking screen time from other devices even when "Share Across Devices" is turned off for iOS 17.6

Please file a bug report using Feedback Assistant, making Apple much more likely to address this growing issue!

Please file a bug report using Feedback Assistant, making Apple much more likely to address this growing issue!

Submitted: https://feedbackassistant.apple.com/feedback/15776860 A more severe issue that may be related is that DeviceActivityMonitor is over-counting screen time for a large percentage of my users. I've detailed the issue at https://developer.apple.com/forums/thread/763542 - with other devs noting they have the same issue. I've also filed a bug report at https://feedbackassistant.apple.com/feedback/15103784 . PLEASE look into this, it renders DeviceActivityMonitor essentially unusable.

Can you please investigate DeviceActivityMonitor overcounting screen time? (https://developer.apple.com/forums/thread/763542 and https://feedbackassistant.apple.com/feedback/15776860). It was introduced in later versions of iOS 17, still happening in latest version of iOS 18, many other devs have reported the same issue, and it renders the monitoring schedule fundamentally unusable for affected users. Would really appreciate some kind of response from the internal devs, thanks!