While l can't speak to the consequences of changing your Apple Account's age setting, changing the age setting will clear all statuses. This is based on my testing with iOS 26.1 and 26.2 beta 3. This might be as designed, but might also be unexpected. I submitted a feedback related to permission management as it is what I would describe as a one-way trip right now. FB21024854 - DeclaredAgeRange / Age Range for Apps: Cannot manage or even view age range for apps in Settings > Apps > AppName as described in learn more in main Age Range for Apps screen Please see the attached screenshots. In the age range for apps “learn more” it clearly directs the user that they can manage a per-app level age range sharing election in the apps settings. This is simply not true. When I go to my apps settings, there is nothing there for age range. Additionally, I cannot even edit the sharing status from the main menu under the Apple account screen. I have a separate feedback for that already. Something is broken or not implemented.

Regarding feedback FB20954846 for App Clip support, I got a message from Apple saying it is fixed. I can now compile, and code sign for an App Clip using the DeclaredAgeRange API. Great. Now that I can get past the compiler failure I'm running up against a new issue. When installed via TestFlight, an App Clip throws that the age range is unavailable. In the console app it looks like the App Clip is still prohibited from calling the system functionality: default PerformanceOrganizer AppClip 18:36:39.200071-0600 (501) Failed to fetch persona: got error from remote proxy: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} error PerformanceOrganizer AppClip 18:36:39.200108-0600 (501) personaAttributesForPersonaType for type:0 failed with error Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} For good measure, the same behavior happens for both installed via Xcode as well as TestFlight. Tested on iOS 26.1 public. Feedback updated with more details. For the other developers out there trying to add Age Assurance to your App Clips, are you running into the same issues?

This is not legal advice, nor a statement from Apple. I will share what I'm going to do in my apps and recommend to others. How I interpret 121.056 (B) (1) is basically, use the signals when they're available. If they're not available, you can't use them. You can't do the impossible. So if you have an app update that supports iOS 26, implement it there, and < 26 you simply can't. As a developer, it is impossible to use the age signals provided by the App Store if they don't exist. If you're not comfortable with this approach, file feedback asking for support on devices < 26. Hypothetically, if Apple were to add support to, say iOS 18, it would still be something like iOS 18.8.x or higher. I am closely following the OS Usage page and waiting for an update to show the adoption of 26. https://developer.apple.com/support/app-store/ For my specific usage, I'm moving my apps to 26+ for my updates. However, I have apps that include watch extensions, and an Apple Vision Pro target. This presents its own challenges. I posted quite extensively about the framework being unavailable on several Apple platforms. You can read more about those gaps here: https://developer.apple.com/forums/thread/808139

Please familiarize yourself with the Developer News page. https://developer.apple.com/news/ As of today, Apple has posted two articles about this topic: New requirements for apps available in Texas Next steps for apps distributed in Texas I'd highly encourage watching these WWDC25 videos a few times to catch all the details: Deliver age-appropriate experiences in your app - WWDC25 Enhance child safety with PermissionKit - WWDC25

@DTS Engineer Tested with Xcode 26.2 downloaded from the App Store, against iPhone 17 Pro running 26.1 (23B85) Xcode Version 26.2 (17C52) So this property wasn't tested. I haven't touched PermissionKit yet so I wasn't actively testing this, however my wrapper library code still fails for this property too and causes a runtime crash due to symbol not found. AgeRangeService.ParentalControls.significantAppChangeApprovalRequired 55C0A89C-7970-4C69-B5D3-1E6873C6EF2B-diagnostic.json Here is some offending code, assumes iOS 26 minimum target: extension ParentalControls { public init(activeParentalControls: AgeRangeService.ParentalControls) { var value: Int = 0 if activeParentalControls.contains(.communicationLimits) { value |= ParentalControls.communicationLimits.rawValue } if activeParentalControls.contains(.significantAppChangeApprovalRequired) { value |= ParentalControls.significantAppChangeApprovalRequired.rawValue } self.rawValue = value } }

I don't think that Apple will give developers options to modify this one due to its sensitivity. Additionally, this permission is attached to the user's Apple Account, not their device. Out of curiosity, what would you want to put here? In my onboarding I'm doing a permission priming experience before I make the request.

@brianindeed Use PermissionKit and the new significant change topic to notify 'the App Store' of your change. My understanding is that this will trigger the parental consent flows. Check out this video, I assume the behavior is identical across the two different topic types: https://developer.apple.com/videos/play/wwdc2025/293