We have also filed a bug report (FB13056211) for the exact same issue. This is a MAJOR problem for all apps using DeviceActivityReport views. We hope it's going to be fixed in time for the iOS 17 official release!

@Kmart @eskimo Any help on this will be appreciated :)

You won't be able to do that. Your Device Activity Report extension runs in a sandboxed environment to protect user privacy. As stated in the documentation, "this sandbox prevents your extension from making network requests or moving sensitive content outside the extension’s address space". What this means is that even if you place your Core Data database in an app group container that is shared between your app and extension, you won't be able to write anything to it from the extension. You might be able to read from it, though I have never tried this with Core Data.

What time range would you like? Your best bet would be to use a segment interval set to .hourly. This way, you can obtain hourly segments of screen time data on the interval of your choice. Unfortunately, you won't be able to get anything more precise than this.

Take a look at this: https://developer.apple.com/documentation/managedsettings/webcontentsettings/filterpolicy

Have you tried to toggle off/on the screen time permission? You could also try a force restart. Tell me if that works.

The issue still arises when compiling on an iOS 16 device with Xcode 15.0 beta 8 (15A5229m).

The issue persists when compiling on an iOS 16 device using Xcode 15.0 RC 1 (15A240d). This is incredibly frustrating because the public release of iOS 17 is imminent. Currently, we cannot submit builds that take advantage of the new features in iOS 17 without compromising the experience for a significant portion of our user base—until a majority of our users upgrade to iOS 17. For developers reading this thread: I invite you to file a bug report to Apple using the Feedback Assistant app and to upvote this thread massively. For anyone working on or related to the Screen Time API frameworks: Could you please provide us with an update on this situation? Thank you.

This is also happening in my app!

Thank you for sharing this issue. I will attempt to reproduce it when I have time. Does the problem occur on all versions of iOS 17, or did it start with a specific version (e.g., 17.2)? Have you filed a bug report with Apple regarding this?

Was is it linked to https://developer.apple.com/forums/thread/743175 or is this another problem?

@Kmart Any updates on this issue? The bug is still present a year later and reported by users every day on our app. We've also filed a bug report (FB13549454) on this matter.

This bug is has been around for over a year now. We've receiving complaints from users every day about this. We've also filed a bug report (FB13549454) to Apple about this matter. I really hope they will fix it soon.

We're seeing the same issues in our app. They have been around for a while now and it seems they are getting even more frequent on recent iOS 17 versions. We have users contacting us because they can't open any category or search anything without the FamilyActivityPicker crashing. We've filed a bug report (FB12270644) about this. It'd be really great if you could do the same. Make sure to reproduce the issue and start a sysdiagnose right after. Then add the diagnostics file to your report.

I was wondering the same thing!