Have you granted permissions to other third-party screen time apps? If so, turn off those permissions in Settings > Screen Time (leave only yours, obviously) and try again. In my experience, the allow list doesn’t apply correctly if I have restrictions set by other screen time apps. Let me know if that also ends up being the cause of your issue!

I often face this issue on my phone. I've noticed that in the Shield Configuration Extension, the domain string returned by Apple always starts with www.. If I select a domain starting with www. in the Family Controls picker, everything works fine. But if I pick a domain without www., the token doesn't match. It seems there's a mismatch between the domain string from the Family Controls picker and the one sent by Apple in the Shield Configuration Extension. Since the domain name surely influences the token generation, a simple www. changes the token. Of course, we can't control if a web domain includes a www. or not in the Family Controls Picker which is very frustrating...

I also filed a bug report (FB13551195) a few months ago. Can an Apple engineer update us on this problem? Was it improved in iOS 18?

One situation where this can occur is if you join an iCloud family. I suppose that since tokens are intended to be shared among family members in some manner, they will be updated at this moment. I hope this helps!

Thank you for contributing to this thread! I saw in another thread that you were having issues with writing to UserDefaults from the Device Activity Monitor extension. I will check if I can reproduce the issue on my end. Have you filed a bug report with Apple regarding this? If so, could you please provide the report identifier (FBXXXXXXXX) so I can include it in my report? Regarding the analytics events, if you can reproduce the issue consistently, it's possible that Apple has restricted the ability to make network calls from the extension. If the issue is intermittent, it might be worth examining the memory usage. The Device Activity Monitor extension has a fairly strict memory limit (6MB). I assume you are using a third-party SDK for your analytics. Depending on what they instantiate, along with network calls, you might reach this limit at some point. When that happens, your extension will crash immediately.

The problem has recurred on my device, and I've managed to gather a sysdiagnose. By analyzing the logs, I think I've been able to track down one of the issues. This is the error I am seeing: Failed to notify (null) that appLimitThreshold's threshold was reached: Error Domain=PlugInKit Code=4 "RBSLaunchRequest error trying to launch plugin com.jomo.Jomo.JomoDeviceActivityMonitor(8104FF60-5C49-45BD-8AFB-97BE88488134): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x5dd8273e0 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to launch plugin com.jomo.Jomo.JomoDeviceActivityMonitor(8104FF60-5C49-45BD-8AFB-97BE88488134): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x5dd8273e0 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} Basically, it seems the system is failing to launch the device activity monitor extension. As a result, the eventDidReachThreshold won't be triggered. This issue may persist for several minutes or hours once it begins. By checking a previous error, it appears the system is failing to launch the extension because it's looking at an invalid path: Service could not initialize: access(/private/var/containers/Bundle/Application/C6598B47-8977-447C-870B-4D21BDE8ACF9/Jomo.app/PlugIns/JomoDeviceActivityMonitor.appex/JomoDeviceActivityMonitor, X_OK) failed with errno 2 - No such file or directory, error 0x6f - Invalid or missing Program/ProgramArguments I've filed a new bug report (FB13556935), which includes the sysdiagnose and precise timestamps of when the issue was reproduced. I think this bug is CRITICAL for all apps relying on the Device Activity framework. It likely explains a range of issues reported since the framework's release. Specifically, due to this bug, end users may encounter problems such as apps not unblocking at the end of a schedule, apps not blocking at the start of a schedule, and time limits not being updated, among others.

I was wondering the same thing!

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.

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.

@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.

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

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?

This is also happening in my app!

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.

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