What is your start time stamp of the new activity monitor? Is it in the past? or current time? or future?

Might be related to this issue, reported a couple of months ago. Still no reply / comment / workaround from apple. they dont seem to care unfortunately. https://developer.apple.com/forums/thread/758325

Is there any update on this, Thomas? Seems like a pretty serious issue, but no feedback / input from Apple so far!

Have you been able to resolve this issue?

Same problem here, I’ve filed a feedback report as well (FB14237883), but have not heard anything back. @Frameworks Engineer is there any workaround for this? It’s now been a known issue for 2 years so it should be plenty of time to find the issue, fix it, or at least provide a workaround. Thanks a lot!

+1 This would be a great addition to the Apple’s Screen Time functionality! Screen Time is such a wonderful tool, and it’s great that Apple offers APIs for 3rd party developers to build apps on top. Here and there there’s a lots of low-hanging-fruit to improve the API, and I feel like this one is a great example for such an improvement.

For further reference, this is the same issue that has been reported on here: https://forums.developer.apple.com/forums/thread/758325 It has been reported to Apple by multiple different App Developers after the bug was introduced in iOS 17.5 early 2024. As of today, the bug has not been acknowledged by Apple. They haven’t shared any workaround either, nor did they provide a roadmap for the bug fix. When this regression was introduced, I would’ve expected a bug fix to be shipped in iOS 17.6 or iOS 18 – but here we are on iOS 18.1 beta 4 and that weird behavior still reproduces just fine. I did some additional debugging and provided a sample project to Apple: As an example, the ApplicationToken that is provided from the FamilyActivityPicker looks like this: { "data": "AAAAAAAAAAAAAAAAKkToQ2HBrz\\/mb1b5nBgxUGvTxFdokb1dbbM9w8aRhfFTiSv2eMY\\/G6E\\/apO4whQ2nUhLdje0YZngcsi7bysG1HGeSwLQsEgVsJEgzXWMpej7eFdLMOJPPU3+8s61R0MljkHltNcE1JVek59MD9V3+5M4MOQ=" } The ApplicationToken that is then later provided to my ShieldConfigurationDataSource and ShieldActionDelegate looks like this however: { "data": "AAAAAAAAAAAAAAAA0vp9A47itDEtRFJBo1qTIcnqhPUqGPgXo9lsfUwtJznfeI8C0\\/mKPRCjuNlXw7Vv4fUbglMx+A4I6v7MKZvmIfWMbR+ufOy14e6SZMsvPd6k76Mu3dmMv98QAKDKwNEKJv7aLpH2JT7RPEqttrv1vBhHKPs=" } In simple words, a completely different token. So far I wasn’t able to dig any forther to figure out if there is actually a way to connec these two Tokens together, but I thought I’d share this nonetheless.

Hello, we have a similar problem, but on macOS. All settings + data of the user (& myself included) are gone after updating to macOS Sequoia / Safari 18. We are still not sure if that’s a bug on our side or Apple’s. Maybe there’s a new permission that we need to request? Sequoia has a lot of new pop-ups that users need to confirm all the time when opening apps, so maybe there’s also a new permission for the storage that we need to request?

I’m seeing the very same issue right now (iOS 18.1 beta 4). Have you been able to figure out what’s going on? For me, the exempted apps show the default shield configuration "App Restricted" even though no shield should be shown at all. Feedback Report filed under FB15190710

Hello, from the documentation, this API should work how you described: A policy that indicates the device shields all apps and websites, except content that you specify. However, it does not seem to work how documented, because the apps that are specified under except are still shielded, but with a generic shield that just says "Restricted" (even though it shouldn't be shielded at all). Similar unexpected behavior has been reported here as well: https://forums.developer.apple.com/forums/thread/762287

That’s great feedback. AppStore guideline says: User-Generated Content: Apps with user-generated content must include: • A method for filtering objectionable material. • A mechanism to report offensive content promptly. • The ability to block abusive users from the service. • Published contact information for user support. And also: We treat all developers the same. So, Twitter’s update should be rejected!

@amalshyjo the issue you're seeing could be related to a bug that has been talked about in these posts: https://forums.developer.apple.com/forums/thread/732845 and https://forums.developer.apple.com/forums/thread/758325 This bug was introduced by Apple in iOS 17.5 in spring 2024, however until now they have not responded to our feedback reports. I think it would be useful if you could file a feedback report on this as well, highlighting your perspective on the problem. Hope that helps!

Hello, due to privacy restrictions, bundle IDs are only available in the ShieldConfigurationDataSource. Otherwise they are nil / not provided. Hope that helps!

which iOS version are you on? For me, the picker regularly crashes / disappears completely (iOS 18.1).

Hello everyone, I wanted to get back to this, it’s October now and we’ve seen some new iOS betas. Did anyone of you find a workaround for this issue? I’m on the latest iOS 18.1 beta and I can still reproduce this problem every day. As suggested by Apple in June, I have: Filed a radar Created a sample project to reproduce Filed a DTS ticket Even after 5 months: no responses. I am very frustrated by their non-existing help with this issue.