The problem. Our iOS app decides at launch whether to ask for a person's age range, from whether requiredRegulatoryFeatures contains .declaredAgeRangeRequired. The app is not yet released; everything here is pre-release testing. We want to confirm the cases where that member can be absent or can change, and what to do when the read fails.
Questions
- Thread 815952 (Apple, March 2026) says the set could be empty while
isEligibleForAgeFeaturesistrue. Can that case occur on iOS 27? - The article "Requesting people's age range information in your app" says that in some regulated regions people "can't decline sharing". Is Texas one of those regions? Where
.declaredAgeRangeRequiredis present, can a decline remove it afterwards? Another developer reports Texas users who read the requirement and could still decline (thread 836191, no answer yet). What we saw in sandbox is below. - Apple's news post of June 3, 2026 says the Texas requirements apply to new Apple Accounts in Texas from June 4, 2026. Does an account created before that date ever read
.declaredAgeRangeRequired(iOS 26.4 or later), for example after moving to Texas or after an OS update? (A related question, about the sheet, is in thread 853955, no answer yet.) - The
requiredRegulatoryFeaturespage says it throwsnotAvailablewhen the service is unavailable, and the article's example has a barecatch. When it throws, should the app treat the person as required, not required, or retry? (Another developer reportsnotAvailableafter a device was switched from a parent's account to a child's, thread 854397, no answer yet. That report is theirs, not ours.)
What we saw on a decline (question 2). In sandbox (iOS 26.6.2), with a tester on '13 - 15' signed in, a request we made by hand presented the sheet; we declined and it returned declinedSharing. A read after that, tester still on '13 - 15', did not contain .declaredAgeRangeRequired; it was present again once the tester was switched to an 18+ scenario. We had not read the set just before the decline. The device's own account later listed a decline for our app dated that day, so we cannot say which account the sheet belonged to.
What we read (question 1). On iOS 26.6.2 we printed the whole set together with isEligibleForAgeFeatures on 15 reads of sandbox testers created in App Store Connect with region United States. isEligibleForAgeFeatures was true on every read where the set was not empty (7) and false on every read where it was empty (8). On iOS 27.2.1, with a small native sample app that reads the set and isEligibleForAgeFeatures and calls requestAgeRange(ageGates: 16, in:), every launch where we printed both had a non-empty set and true (7 launches). On two further launches the set was empty (a tester signed in, its Age Assurance showing '13 - 15') and we did not print isEligibleForAgeFeatures, so we cannot say whether those were the case in question 1.
Environment: iPhone 17e, iOS 26.6.2 and iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Reads made from development builds.
Related Feedback: FB25530441, FB25530501, FB25530513.