We also have multiple reports from our users on this issue, right now over 200 individual reports, with no workaround we can provide except not blocking Facebook. We also opened a feedback assistant about the underlying issue(FB11799302,opened in November 2022).

are you testing in the EU on the store ? approvedWithDataAccess is accessible only in the eu, and the associated functions that needs this permission, it works on dev devices everywhere. it's clearly indicated in the documentation : https://developer.apple.com/documentation/familycontrols/authorizationstatus/approvedwithdataaccess

Can you open a bug report for it ? we reported a lot of issues with DeviceActivityReport views not behaving like regular SwiftUI views, and this would complement those bug reports

Yes, this is on purpose to preserve user privacy, as stated in the documentation

Hey, I've opened a bug report (FB21974097) for this, can you do the same ?

Hey rebounding on this, I work at Opal, and we built a product for schools that looks exactly like what you're mentioning, and launched it at Harvard-Westlake School, the top high school in LA, you can check it out here -> https://www.opal.so/for-schools [quote='803911021, jjguth4, /thread/803911, /profile/jjguth4'] If anyone has any guidance here, it would be so helpful! My boss (Head of School) is super interested in this idea and significantly prefers it to every other alternative that he has encountered. The problem is this idea does not exist yet! [/quote]

Hey ! This is prohbited for privacy reasons, the DeviceActivityExtension can only read from the shared app group, but cannot write. You can write inside the extension sandbox, but those won't be readable by the main application.

We observed the same behavior with iOS 18.4, it's also impacting modally presented UIKit UIHostingController presenting a FamilyAcitivityPicker, they are dismissed alongside the FamilyPicker.

Hey ! This is by design, you cannot access app names or bundle identifier outside of the ActivityReport or shield extension sandbox for privacy reasons, you can only store and send opaque tokens in your app, not the actual apps.

Hey, the issue was already described here -> https://developer.apple.com/forums/thread/764457 And some workarounds were mentioned :) In the mean time, would be nice If you could open a bug report, the more there are, the most likely apple will fix it ! Regards

Hey, the issue was already described here -> https://developer.apple.com/forums/thread/764457 And some workarounds were mentioned :) In the mean time, would be nice If you could open a bug report, the more there are, the most likely apple will fix it ! Regards

Hey ! We opened an Apple bug report for this exact issue 2 years ago with id FB11400221, can you open a report yourself to get this fixed by apple ? We have a lot of user reports about it, and we didn't find a workaround. We found a way to detect the crash though, and we show am explanation dialog when it happens.

Hey, To my knowledge, you cannot create Tokens from bundle ID, only get them from the FamilyActivitiyPicker. I can also confirm that tokens are not portable across devices, an Instagram token on device A is not the same as on device B, using it to block apps will just do nothing on device B. I'm almost certain you cannot achieve what you are trying to do with the current set of APIs provided by Apple. I believe this is behaving as designed by apple for privacy reasons. Good luck !

We had multiple reports of this exact issue as well from Opal users, we didn't open a bug report because we weren't able to reproduce the issue on our own devices 😢

I concur ! This would make perfect sense. We also opened a radar for it -> https://feedbackassistant.apple.com/feedback/14051075