+1 Thank you for bringing this up! I posted (a much less clear explanation than this post) of encountering this issue: https://developer.apple.com/forums/thread/748542?page=1#782949022

OK this thread talks about the actual problem: https://developer.apple.com/forums/thread/745675

+1 also submitted: FB13066529

Same: FB11836901 (has a testing app to reproduce)

+1 (thank you Thomas for being on top of this!) I had a user bug report of this happening where permissions are 'randomly' lost so DeviceActivityCenter scheduling starts returning errors as if there are no permissions. Radar here with some details (if more is needed, happy to help): FB12364989

+1 Similar thread here for .individual authorization: https://developer.apple.com/forums/thread/714651

+1 on having more power to display the icons in various ways While on the topic of icons, there seems to be a bug where the icon inside the Label is a different size depending on the device...on my iPhone 14 Pro, there's a "border" around the icon (icon image is about 20x20). On iPhone XS and one of the latest iPad Pro's, the icon spans the full 'space' of Label (icon image is about 40x40). One of the issues is that it makes it difficult to size properly. I am not sure what size the icons will have on all the different devices.

+1 please create the ability to to restrict the user from disabling Screen Time access (ex. via ManagedSettings)

Part of my problem when getting this error was a faulty extension from an older Xcode beta version. In Xcode Beta 1, it created extensions one way. In Xcode Release Candidate, it created extensions another way. I had to delete the extension from the project, and re-create it in the Xcode Release Candidate.

The documentation you linked seems to say that the limit is 20: The maximum number of activities that can be monitored at one time by an app and its extensions is twenty.

The code corresponds to the backwards order of the FamilyControlsErrors seen in the documentation and it starts from 0. So restricted is Code 0, unavailable is Code 1, invalidArgument is Code 2.  If "5" is FamilyControlsError.authorizationCanceled, I am still a little confused on the order?

@cinnamontoast I opened FB10798095 If it indeed is a cancellation issue, then this log may be relevant: error 2022-07-20 19:41:44.011573 -0400 FamilyControlsAuthenticationUI Attempt to present <FamilyControlsAuthenticationUI.ConfirmationViewController: 0x103032600> on <FamilyControlsAuthenticationUI.AuthenticationUIServiceViewController: 0x10550e700> (from <FamilyControlsAuthenticationUI.AuthenticationUIServiceViewController: 0x10550e700>) whose view is not in the window hierarchy.

@cinnamontoast Hi there! Thank you for your help :) How do I know FamilyControlsError.authorizationCanceled maps to "Code 5"? I can't find a number in the docs? I might be missing something obvious? To note, this worked in Beta 1 and Beta 2. I can't get it to work in Beta 3. I call: do {    try await AuthorizationCenter.shared.requestAuthorization(for: .individual) } catch { } It then prompts me: "Allow 'APP' to Manage Restrictions on This iPad" I click "Continue." FaceID succeeds, and it just returns the error: Error Domain=FamilyControls.FamilyControlsError Code=5 "(null)"

@tjpaul I can't get anything to work properly in Beta 3 - waiting for Beta 4

remove the app and try install it again. Do you able to see the alert dialogue asking for authentication? I have tried that, and it's the same effect. In Beta 3, Screen Time API's are not working well for me. For example, I can't even disable Screen Time restrictions for my app in Beta 3 (well, that happened before I wasn't able to enable them).