Declared Age Range

RSS for tag

For creating age-appropriate experiences in your app by asking people to share their age range.

Posts under Declared Age Range tag

105 Posts

Post

Replies

Boosts

Views

Activity

PermissionKit significant-change consent: is a parent's answer delivered if the app is closed?
Our app is not yet released. We have built, but not switched on, the parental consent step for a significant change: when requiredRegulatoryFeatures contains .significantAppChangeRequiresParentalConsent, the app creates PermissionQuestion(significantAppUpdateTopic: SignificantAppUpdateTopic(description:)), calls AskCenter.shared.ask(_:in:), and holds the changed app until an approval arrives. It listens with for await response in AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) from launch, on every launch while an approval is owed. The ask and listen part runs on iOS 26.2 and later; the set is read on iOS 26.4 and later. We have seen iOS 27's askSignificantChangePermission(for:permissionFlow:in:) with .approveInPerson, which returns the answer to the caller; the questions below are about the Ask to Approve path through ask(_:in:). A parent may answer hours later, after the child has closed the app. "Creating a communication experience" says to obtain the sequence promptly after launch, and points to a background route for communication limits, but says nothing about SignificantAppUpdateTopic. The sample "Implementing age assurance and permissions" listens at its entry point but does not say what happens to an answer given while the app is closed. If the parent answers while the app is closed, is that response delivered on the next launch's responses(for: SignificantAppUpdateTopic.self)? Is a response delivered once, or again on every later launch? Does that differ for an approval and a decline? On the Ask to Approve path, is there a supported way for the app to be woken, or to fetch the current answer, so that it does not depend on a response arriving while it is running? Without an expirationDate, how long does a question stay open for the parent? What does ask do when a question on the same topic is already pending? After a decline, can the child send a new question? "Testing Age Assurance in Sandbox" says that for a selected scenario PermissionKit returns the associated response status. Does that response arrive through responses(for:) after ask, and can the closed-app case in question 1 be exercised in sandbox? We have not yet run this on a device. Environment: iPhone 17e, iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK.
0
0
40
1d
Declared Age Range: does a sandbox tester's Age Assurance setting reach other installs after sign-out?
The problem. We are trying to confirm, before release, what our app's age check will read on an App Store install. On a development-signed install, a sandbox tester's Age Assurance setting was still returned after the tester signed out. We want to know whether a TestFlight or App Store install would read the same state. The app is not yet released; everything here is pre-release testing. Questions On a development-signed install with no sandbox tester signed in, does the API answer from the device's real Apple Account as production would, or from sandbox state? Is a sandbox tester's Age Assurance setting expected to stay in effect after the tester signs out? If so, what clears it? Can that state reach a TestFlight install or an App Store install on the same device? Do TestFlight installs read production or sandbox for this API? How should a developer verify before release what an App Store install will read? Other developers have asked near questions 3 and 4 (threads 851245 and 854172) without an Apple answer. What we read (iPhone 17e, iOS 27.2.1; a small native sample app, development-signed, that reads requiredRegulatoryFeatures and calls requestAgeRange(ageGates: 16, in:)) With the device's own adult account and no sandbox tester signed in: [declaredAgeRangeRequired], sharing with a lower bound of 18, declaration confirmed, no sheet. We signed in a new sandbox tester and set Age Assurance to '13 - 15, significant change approved': the set gained .significantAppChangeRequiresParentalConsent, and the request returned 13 to 15 with .significantAppChangeApprovalRequired in activeParentalControls. After the tester signed out, with no sandbox tester signed in, reads still returned the tester's 13 to 15 on every read for the next 21 minutes, one of them after a restart, and again the next morning, about 16 hours later. No sheet was seen on any of these reads. The next morning we signed the same tester back in (its Age Assurance still showed '13 - 15'; the set read empty) and made one request by hand, which presented a sheet; we chose Share and it returned 16 or older, self-declared. We then set the tester to '18+, age confirmed, significant change not applicable' and signed it out. From then on, with no tester signed in, reads returned a lower bound of 18 again. On TestFlight. A TestFlight build of our app has no console, so we could not read what the API returned there. Once (iOS 26.6.2), three sandbox testers had used the phone earlier in the day, the last set to '13 - 15', and all were signed out. With the phone then signed out of every Apple Account, a TestFlight build opened in about a second. Just after, a development build of the same source read both .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent and ended on the screen our app shows when the request returns anything other than a shared range of 16 or older. Environment: iPhone 17e, iOS 27.2.1 and iOS 26.6.2. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Related Feedback: FB25530441, FB25530501, FB25530513.
0
0
41
1d
Declared Age Range: when can the requirement be absent or removed, and what if the read throws?
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 isEligibleForAgeFeatures is true. 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 .declaredAgeRangeRequired is 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 requiredRegulatoryFeatures page says it throws notAvailable when the service is unavailable, and the article's example has a bare catch. When it throws, should the app treat the person as required, not required, or retry? (Another developer reports notAvailable after 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.
0
0
41
1d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
0
0
36
3d
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
0
0
75
1w
Declared Age Range: fallback behavior, cached results, and older iOS versions
Hello, I am preparing an 18+ workout logging app for iOS and would like to clarify the supported behavior of the Declared Age Range framework before completing its integration. Workout records, body measurements and saved videos are stored locally. Outside additional regulatory requirements, the planned entry flow uses a neutral adult self-declaration without collecting a date of birth or identity documents. The intended storefronts are Japan, the United States, the United Kingdom, Canada, Australia, New Zealand, Ireland and Singapore. These are implementation-design questions, not errors reproduced in a completed DAR integration. I am seeking documented API/platform behavior, not legal approval. Applicability checks that fail If isEligibleForAgeFeatures throws, returns notAvailable, or does not complete, is there a supported fallback signal or recommended retry strategy? I would not interpret an error as a successful “outside regulated scope” result. Is there a documented platform requirement for app access while applicability remains unresolved, separate from developers’ obligations under applicable law? Previously returned adult age ranges If declaredAgeRangeRequired applies and requestAgeRange fails after an earlier adult response, does Apple support relying on an app-stored result? I understand that the system caches responses; my question concerns a result stored separately by the app. Is there a supported way to detect when that result must be invalidated because of an Apple Account change, changes to age information, or sharing/consent changes? If no such signal exists, what implementation pattern does Apple recommend? I would not assume that a previous result always belongs to the current person or invent a cache lifetime. Earlier OS versions For affected newly created Apple Accounts in regulated regions, what supported path applies on: iOS versions without Declared Age Range; iOS 26.0–26.1, without isEligibleForAgeFeatures; iOS 26.2–26.3, without requiredRegulatoryFeatures? The age-assurance Q&A discusses existing Apple Accounts on iOS 18 or earlier. Is there additional documentation covering newly created affected accounts on earlier OS versions? While checks remain unresolved, the proposed design withholds advertising and new purchases and preserves existing data with free export. This is a proposed design, not an assumption that local recording is exempt from any requirement. References reviewed: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app Pointers to relevant documentation or sample code would be appreciated. Thank you.
0
0
42
1w
How can I disable sharing age range with an app
I am still in development phase of an app, I integrated AgeRangeAPI and shared age range with my app. When I go to system settings > profile > personal information > Age Range for Apps , I see the app and it says "Shared", but I can't unshare anymore. I can unshare globally but now per app. I know the AgeRangeAPI can be tested from the Developer > Account > Manage, but that kind of testing skips the native UI I want to test again full scenario to see what real users will experience, I want to see the real UI of sharing again.
5
0
151
1w
Clarification on Declared Age Range Prompt in Texas and Brazil
Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.
1
1
809
2w
Declared Age Range on iOS 27.2: different mandatory-sharing behavior with BR detected
Two physical iPhones on public iOS 27.2 (24B119), using separate adult US Apple Accounts, produce different results from the Declared Age Range framework under a BR country classification. Device A displays the mandatory Brazil-sharing notice, does not accept Never in the native selector, and returns an 18+ range to a real request with ageGates:18. Device B accepts Never after the update. The same local checker receives declinedSharing with no age bounds. Never remains checked afterward. The checker invokes requestAgeRange even when regulatory eligibility is false; it does not synthesize a refusal locally. Device logs indicate normal flow, without a sandbox override. Selected diagnostics show US billing countries for App Store, Music and iCloud on both devices and BR detected on both. Their separate age-assurance classifications differ: BR with account eligibility true on A, versus unset with account eligibility false on B. Unset is not being treated as US. The captures were made on different dates, and identical account histories and management payloads have not been established. Both devices are supervised. No location simulation or network filter was active during B's test. For developers handling these API results, what documented account or device criterion explains this difference? What supported diagnostic and correction path is available when the native sharing control is unavailable on one device but effective on another under the same detected country? The detailed comparison has been supplied privately through Feedback Assistant. This question concerns the public framework's behavior and supported remediation; it does not assume US billing country alone creates an exemption.
0
0
265
2w
[Age Range]System-level Age Range prompt fails to appear after Switching from Parent to Child Account.
When switching a device from a Parent Apple Account to a Child Apple Account using the "Keep Data" option, the system-level Declared Age Range prompt fails to render. Instead of presenting the onboarding flow to the user, the system immediately throws AgeRangeError Code=2 (AgeRangeService.Error.notAvailable Indicates the system was unable to share the person’s age range). This causes the app to bypass the intended age verification and log the child in directly. Steps to Reproduce: Sign in to a verified Parent Apple Account on the device and log in to the PTT app. Sign out of the Parent Apple Account in device Settings, ensuring the "Keep Data" option is selected. Sign in to a Child Apple Account on the same device, selecting "Keep Data" (Sign in and Merge data). Open the existing PTT app. Expected Behavior: The OS should present the system-level Age Range onboarding prompt to the new child user so the age range can be properly verified or shared.
0
0
564
3w
Testing Declared Age Range API on Production
Hello, We want to ensure that our Declared Age Range API is working correctly, in Production, but we had concerns on how this is done. Do we need to have an account created from Texas with a credit card/addressed based in Texas? What's the best approach to be able to test this in a live environment to ensure everything is working as intended? Thank You.
0
0
47
3w
Declared Age Range: is the sheet shown for Texas accounts created before June 4, 2026, and where can a decline be changed?
This is a question about expected behaviour rather than a bug. Environment iOS 26.x on iPhone 17 Pro Xcode 27. Swift, SwiftUI Declared Age Range capability enabled Context Our app is currently available without age restrictions. Starting in January 2027, we plan to restrict access by age in regulated US jurisdictions using the Declared Age Range API, and treat .declinedSharing as "age unknown." Before rolling this out, we want to understand what existing users will experience. Apple's June 3, 2026 developer news says "new Apple Accounts in Texas are now subject to the law." We couldn't find documentation on how the API behaves for Texas accounts created before that date. Code @Environment(\.requestAgeRange) private var requestAgeRange // ... let response = try await requestAgeRange(ageGates: 16, 18) switch response { case .sharing(let range): // use range.lowerBound / range.upperBound / range.ageRangeDeclaration case .declinedSharing: // treat as age unknown @unknown default: break }Questions For a Texas Apple Account created before June 4, 2026, on iOS 26.x, will requestAgeRange show the age range sheet, as it would in a nonregulated region? If the sheet is shown and the user declines to share: a. Where can they change that decision afterwards? Only under the Apple Account (Settings > [name] > Personal Information > Age Range for Apps), or also on the app's own page (Settings > Apps > [app] > Age Range for Apps)? b. Can the app show the sheet again by calling requestAgeRange, or does it return the cached .declinedSharing without UI until the user changes the setting? c. Is there a supported way to deep-link the user directly to that setting from the app? Thanks!
0
0
58
3w
TestFlight Declared Age Range Sandbox Scenarios Not Reflected in App Responses
Hello team, We are testing the Declared Age Range/Age Signal functionality in a TestFlight build and would appreciate guidance on the correct setup and testing process. Current Behavior Observed We are seeing inconsistent behavior between the Sandbox environment and the age-range results returned to the application. Scenario 1: Apple Account Signed In A regular Apple ID is signed in on the device. The TestFlight build is installed and launched. The application returns Verified Adult (18+). We then sign in to the Sandbox environment using a Sandbox Test Account and select a different test scenario (for example, a child/minor scenario). After relaunching the application, the age signal response still remains Verified Adult (18+). Scenario 2: Apple Account Signed Out We sign out of the Apple account from the device. As a result, TestFlight is also signed out. When the application is launched, the response changes to Unable to Verify. Even after changing Sandbox test scenarios (such as child, teen, or adult scenarios), the application continues to return Unable to Verify rather than the selected test case response. Based on this behavior, it appears that the application is not reflecting the scenario selected in the Sandbox environment. Questions What is the correct process for connecting an application to the Sandbox environment when testing Declared Age Range scenarios? Does the Apple ID used for TestFlight need to be associated with or match the Sandbox Test Account? Should the device remain signed in to a regular Apple ID while the Sandbox Test Account is used for testing? How does the app determine whether it should use the selected Sandbox scenario versus the signed-in Apple account? Are there any additional device settings, account requirements, or configuration steps required for Sandbox age-range testing? Is there a way to verify that the application is successfully connected to the Sandbox environment and consuming the selected test scenario? If the Sandbox scenario is configured correctly, should we expect the API response to change immediately when switching between child, teen, and adult test cases? At present, regardless of the Sandbox scenario selected, the application either continues to return Verified Adult (18+) or Unable to Verify, and we have been unable to validate the documented Sandbox test scenarios. Could you please provide guidance on the expected setup and testing workflow for TestFlight applications using the Declared Age Range feature? Thank you for your assistance.
2
0
133
3w
Declared Age Range and consent revocation in an entirely offline iPhone app
We are implementing regional age-assurance checks for an iPhone app that supports iOS 17 and later. It is a paid toddler app with no backend, app accounts, ads, in-app purchases, messaging or shared user content. All content is suitable for young children. Optional family voice recordings remain on the device. We plan to request Declared Age Range when Apple's regulatory signals require it, process the response locally, and avoid logging, storing or transmitting age data. We are seeking supported technical behavior, rather than legal advice or preapproval: What supported API or platform guarantee establishes that initial download/purchase parental consent was obtained? The age-range response does not appear to expose a separate initial-consent status. Apple's age-assurance Q&A says the platform prevents launching an app after a parent revokes consent. The implementation guidance also describes RESCIND_CONSENT through App Store Server Notifications. For an app with no backend or remotely accessible service, can local access rely on the platform's launch blocking, or is a notification server still required? If a server is required, what local enforcement behavior should it drive? What is the supported behavior for offline reopening and unavailable or network-error results, particularly on older supported iOS versions where the regulatory APIs are unavailable? Does platform enforcement also cover an app already running when consent is revoked, and how should an offline app handle that transition? Documentation or a sample showing this entirely local case would be helpful.
0
0
414
Oct ’26
Declared Age Range API availability on iOS versions below iOS 26
Hello team, We are currently evaluating the Declared Age Range API for supporting age-related regulatory requirements in our application, and we would appreciate some clarification regarding iOS version compatibility. Based on the documentation, we understand that newer age-related capabilities such as isEligibleForAgeFeatures and Regulatory Features are available only on newer iOS versions (for example, iOS 26.4+). We would like to clarify the following: Is the Declared Age Range API itself available only on iOS 26+ devices, or can age range information also be retrieved on earlier iOS versions? For users running iOS versions below 26, will the Declared Age Range API: Return age range information? Return a limited response? Be completely unavailable? Is our understanding correct that applications running on iOS versions earlier than iOS 26 cannot obtain age range information through the Declared Age Range API and therefore cannot determine whether age-related regulatory requirements apply? Are there any recommended fallback approaches for supporting age-verification or age-assurance requirements on devices running iOS versions below 26? Has anyone successfully implemented a solution that provides equivalent age-related signals or regulatory age-verification handling for users on earlier iOS versions? If so, are there any best practices or recommended approaches? Any clarification or guidance would be greatly appreciated. Thanks!
1
0
148
Oct ’26
DeclaredAgeRange: older-iOS fallback and consent revocation for a server-free utility
I am integrating Declared Age Range into the initial release of an all-ages iPhone utility with an iOS 17 deployment target. It stores user-created records only on the device and has no app accounts, backend, in-app purchases, subscriptions or remotely accessible data. The planned distribution includes the United States. On iOS 26.4 and later, the planned implementation checks AgeRangeService.shared.requiredRegulatoryFeatures and requests a range when .declaredAgeRangeRequired is present. On iOS 26.2–26.3, it uses isEligibleForAgeFeatures. Returned age information would be used transiently on-device, without persistence or export. A requested boundary of 18 would not restrict this all-ages app to adults. Two technical points remain unclear: The current Q&A says existing Apple Accounts on iOS/iPadOS 18 or earlier are unaffected. What supported fallback should an app use for affected new accounts on older supported versions, including iOS 26.0–26.1 without the eligibility property? When a required eligibility or age-range request temporarily fails, is there documented guidance for the access/retry behavior of an all-ages app? The documented notAvailable outcome can represent refusal or unavailability; the implementation should not misreport either as a completed check. The Q&A says Apple prevents app launch after parental consent revocation and also directs developers to RESCIND_CONSENT App Store Server Notifications V2. For a utility with no server, app account or remote data/access to revoke, is any additional client action or notification endpoint required? If so, what technical mechanism should connect that action to the fully local installation? I am seeking the documented API and system behavior, not a determination of legal compliance. References: Age assurance Q&A Update for apps distributed in Texas Requesting an age range
0
0
390
Sep ’26
DeclaredAgeRange API not triggering in regulated regions (Brazil, Utah) — Is it functioning in production?
Hi, We've implemented age assurance logic in our app using the DeclaredAgeRange framework to comply with regulations in Brazil (Digital ECA, effective March 17, 2026) and Utah (App Store Accountability Act, effective May 6, 2026). Our implementation calls AgeRangeService.shared.isEligibleForAgeFeatures on app launch to determine whether the current user is subject to age assurance requirements, and proceeds to call requestAgeRange(ageGates:) accordingly. However, after monitoring in production since the Brazil enforcement date, we've consistently observed isEligibleForAgeFeatures returning false for users in regulated regions, with no age range data being returned. What we'd like to clarify: Is isEligibleForAgeFeatures currently returning true for users in Brazil in production (not sandbox)? For Utah — given that HB 498 pushed the developer compliance deadline to May 6, 2027, will isEligibleForAgeFeatures reflect the original May 6, 2026 activation date or the revised 2027 date? Is there a known rollout schedule or gradual activation plan for these regions that would explain why the flag remains false even after the legal enforcement dates have passed? We've seen similar reports from other developers on these forums, so it seems this may be a widespread issue rather than an implementation problem on our end. Any official guidance on the current status of the API in regulated regions would be greatly appreciated. Thanks.
2
2
1.8k
Aug ’26
AppStore.ageRatingCode always returns 0 on real device — is this expected behavior?
Hello everyone I'm implementing age verification in my app to comply with upcoming age assurance laws (Utah, etc.), and I'm using AppStore.ageRatingCode from StoreKit to retrieve my app's current age rating. According to the documentation: extension AppStore { @available(iOS 26.2, macOS 26.2, tvOS 26.2, watchOS 26.2, *) public static var ageRatingCode: Int? { get async } } "Use this property to fetch the age rating for your app and compare it with the last known age rating to check if it has changed." However, calling this always returns 0 in my environment. Environment: Device: Real physical device (not simulator) iOS version: 26.4 Sandbox Apple Account: signed in via Settings → Developer → Sandbox Apple Account App Store Connect: app is registered and age rating is configured Xcode Scheme → Run → Options → StoreKit Configuration: None Code: func getAgeRatingCode() async -> Int? { guard let ageRatingCode = await AppStore.ageRatingCode else { print("Age rating code unavailable") return nil } print("ageRatingCode: \(ageRatingCode)") // always prints 0 return ageRatingCode } Questions: What integer values does ageRatingCode map to? (e.g., does 4+ = 4, 9+ = 9, 13+ = 13, etc.? Or is it a different internal code?) This mapping is not documented anywhere I can find. Is 0 a valid return value, and if so, what does it represent? Is there a known issue with this API returning 0 even when all conditions appear to be correctly configured? Any guidance from Apple engineers or developers who have successfully used this API would be greatly appreciated.
1
0
706
Jul ’26
Swift thread continuation crash when calling isEligibleForAgeFeatures
Hi, We’ve been observing crashes when calling “try await DeclaredAgeRange.AgeRangeService.shared.isEligibleForAgeFeatures”. Our crash logs show a “suspend resume partial function” crash from libswift_Concurrency.dylib swift::runJobInEstablishedExecutorContext. Based on our analysis, this is because once Apple’s eligibility check completes, it attempts to resume the Swift task continuation directly on its own internal background thread instead of yielding back to the Swift cooperative thread pool. Because the caller task inherits @MainActor isolation (due to a UIViewController being passed into our pipeline further up as it’s needed for requestAgeRange), the Swift runtime crashes when trying to reconcile the @MainActor context on Apple's foreign background thread. Has anyone encountered this and found a fix, and is this a known issue? Thanks!
1
0
362
Jul ’26
PermissionKit significant-change consent: is a parent's answer delivered if the app is closed?
Our app is not yet released. We have built, but not switched on, the parental consent step for a significant change: when requiredRegulatoryFeatures contains .significantAppChangeRequiresParentalConsent, the app creates PermissionQuestion(significantAppUpdateTopic: SignificantAppUpdateTopic(description:)), calls AskCenter.shared.ask(_:in:), and holds the changed app until an approval arrives. It listens with for await response in AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) from launch, on every launch while an approval is owed. The ask and listen part runs on iOS 26.2 and later; the set is read on iOS 26.4 and later. We have seen iOS 27's askSignificantChangePermission(for:permissionFlow:in:) with .approveInPerson, which returns the answer to the caller; the questions below are about the Ask to Approve path through ask(_:in:). A parent may answer hours later, after the child has closed the app. "Creating a communication experience" says to obtain the sequence promptly after launch, and points to a background route for communication limits, but says nothing about SignificantAppUpdateTopic. The sample "Implementing age assurance and permissions" listens at its entry point but does not say what happens to an answer given while the app is closed. If the parent answers while the app is closed, is that response delivered on the next launch's responses(for: SignificantAppUpdateTopic.self)? Is a response delivered once, or again on every later launch? Does that differ for an approval and a decline? On the Ask to Approve path, is there a supported way for the app to be woken, or to fetch the current answer, so that it does not depend on a response arriving while it is running? Without an expirationDate, how long does a question stay open for the parent? What does ask do when a question on the same topic is already pending? After a decline, can the child send a new question? "Testing Age Assurance in Sandbox" says that for a selected scenario PermissionKit returns the associated response status. Does that response arrive through responses(for:) after ask, and can the closed-app case in question 1 be exercised in sandbox? We have not yet run this on a device. Environment: iPhone 17e, iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK.
Replies
0
Boosts
0
Views
40
Activity
1d
Declared Age Range: does a sandbox tester's Age Assurance setting reach other installs after sign-out?
The problem. We are trying to confirm, before release, what our app's age check will read on an App Store install. On a development-signed install, a sandbox tester's Age Assurance setting was still returned after the tester signed out. We want to know whether a TestFlight or App Store install would read the same state. The app is not yet released; everything here is pre-release testing. Questions On a development-signed install with no sandbox tester signed in, does the API answer from the device's real Apple Account as production would, or from sandbox state? Is a sandbox tester's Age Assurance setting expected to stay in effect after the tester signs out? If so, what clears it? Can that state reach a TestFlight install or an App Store install on the same device? Do TestFlight installs read production or sandbox for this API? How should a developer verify before release what an App Store install will read? Other developers have asked near questions 3 and 4 (threads 851245 and 854172) without an Apple answer. What we read (iPhone 17e, iOS 27.2.1; a small native sample app, development-signed, that reads requiredRegulatoryFeatures and calls requestAgeRange(ageGates: 16, in:)) With the device's own adult account and no sandbox tester signed in: [declaredAgeRangeRequired], sharing with a lower bound of 18, declaration confirmed, no sheet. We signed in a new sandbox tester and set Age Assurance to '13 - 15, significant change approved': the set gained .significantAppChangeRequiresParentalConsent, and the request returned 13 to 15 with .significantAppChangeApprovalRequired in activeParentalControls. After the tester signed out, with no sandbox tester signed in, reads still returned the tester's 13 to 15 on every read for the next 21 minutes, one of them after a restart, and again the next morning, about 16 hours later. No sheet was seen on any of these reads. The next morning we signed the same tester back in (its Age Assurance still showed '13 - 15'; the set read empty) and made one request by hand, which presented a sheet; we chose Share and it returned 16 or older, self-declared. We then set the tester to '18+, age confirmed, significant change not applicable' and signed it out. From then on, with no tester signed in, reads returned a lower bound of 18 again. On TestFlight. A TestFlight build of our app has no console, so we could not read what the API returned there. Once (iOS 26.6.2), three sandbox testers had used the phone earlier in the day, the last set to '13 - 15', and all were signed out. With the phone then signed out of every Apple Account, a TestFlight build opened in about a second. Just after, a development build of the same source read both .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent and ended on the screen our app shows when the request returns anything other than a shared range of 16 or older. Environment: iPhone 17e, iOS 27.2.1 and iOS 26.6.2. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Related Feedback: FB25530441, FB25530501, FB25530513.
Replies
0
Boosts
0
Views
41
Activity
1d
Declared Age Range: when can the requirement be absent or removed, and what if the read throws?
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 isEligibleForAgeFeatures is true. 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 .declaredAgeRangeRequired is 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 requiredRegulatoryFeatures page says it throws notAvailable when the service is unavailable, and the article's example has a bare catch. When it throws, should the app treat the person as required, not required, or retry? (Another developer reports notAvailable after 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.
Replies
0
Boosts
0
Views
41
Activity
1d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
Replies
0
Boosts
0
Views
36
Activity
3d
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
Replies
0
Boosts
0
Views
75
Activity
1w
Declared Age Range: fallback behavior, cached results, and older iOS versions
Hello, I am preparing an 18+ workout logging app for iOS and would like to clarify the supported behavior of the Declared Age Range framework before completing its integration. Workout records, body measurements and saved videos are stored locally. Outside additional regulatory requirements, the planned entry flow uses a neutral adult self-declaration without collecting a date of birth or identity documents. The intended storefronts are Japan, the United States, the United Kingdom, Canada, Australia, New Zealand, Ireland and Singapore. These are implementation-design questions, not errors reproduced in a completed DAR integration. I am seeking documented API/platform behavior, not legal approval. Applicability checks that fail If isEligibleForAgeFeatures throws, returns notAvailable, or does not complete, is there a supported fallback signal or recommended retry strategy? I would not interpret an error as a successful “outside regulated scope” result. Is there a documented platform requirement for app access while applicability remains unresolved, separate from developers’ obligations under applicable law? Previously returned adult age ranges If declaredAgeRangeRequired applies and requestAgeRange fails after an earlier adult response, does Apple support relying on an app-stored result? I understand that the system caches responses; my question concerns a result stored separately by the app. Is there a supported way to detect when that result must be invalidated because of an Apple Account change, changes to age information, or sharing/consent changes? If no such signal exists, what implementation pattern does Apple recommend? I would not assume that a previous result always belongs to the current person or invent a cache lifetime. Earlier OS versions For affected newly created Apple Accounts in regulated regions, what supported path applies on: iOS versions without Declared Age Range; iOS 26.0–26.1, without isEligibleForAgeFeatures; iOS 26.2–26.3, without requiredRegulatoryFeatures? The age-assurance Q&A discusses existing Apple Accounts on iOS 18 or earlier. Is there additional documentation covering newly created affected accounts on earlier OS versions? While checks remain unresolved, the proposed design withholds advertising and new purchases and preserves existing data with free export. This is a proposed design, not an assumption that local recording is exempt from any requirement. References reviewed: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app Pointers to relevant documentation or sample code would be appreciated. Thank you.
Replies
0
Boosts
0
Views
42
Activity
1w
How can I disable sharing age range with an app
I am still in development phase of an app, I integrated AgeRangeAPI and shared age range with my app. When I go to system settings > profile > personal information > Age Range for Apps , I see the app and it says "Shared", but I can't unshare anymore. I can unshare globally but now per app. I know the AgeRangeAPI can be tested from the Developer > Account > Manage, but that kind of testing skips the native UI I want to test again full scenario to see what real users will experience, I want to see the real UI of sharing again.
Replies
5
Boosts
0
Views
151
Activity
1w
Clarification on Declared Age Range Prompt in Texas and Brazil
Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.
Replies
1
Boosts
1
Views
809
Activity
2w
Declared Age Range on iOS 27.2: different mandatory-sharing behavior with BR detected
Two physical iPhones on public iOS 27.2 (24B119), using separate adult US Apple Accounts, produce different results from the Declared Age Range framework under a BR country classification. Device A displays the mandatory Brazil-sharing notice, does not accept Never in the native selector, and returns an 18+ range to a real request with ageGates:18. Device B accepts Never after the update. The same local checker receives declinedSharing with no age bounds. Never remains checked afterward. The checker invokes requestAgeRange even when regulatory eligibility is false; it does not synthesize a refusal locally. Device logs indicate normal flow, without a sandbox override. Selected diagnostics show US billing countries for App Store, Music and iCloud on both devices and BR detected on both. Their separate age-assurance classifications differ: BR with account eligibility true on A, versus unset with account eligibility false on B. Unset is not being treated as US. The captures were made on different dates, and identical account histories and management payloads have not been established. Both devices are supervised. No location simulation or network filter was active during B's test. For developers handling these API results, what documented account or device criterion explains this difference? What supported diagnostic and correction path is available when the native sharing control is unavailable on one device but effective on another under the same detected country? The detailed comparison has been supplied privately through Feedback Assistant. This question concerns the public framework's behavior and supported remediation; it does not assume US billing country alone creates an exemption.
Replies
0
Boosts
0
Views
265
Activity
2w
[Age Range]System-level Age Range prompt fails to appear after Switching from Parent to Child Account.
When switching a device from a Parent Apple Account to a Child Apple Account using the "Keep Data" option, the system-level Declared Age Range prompt fails to render. Instead of presenting the onboarding flow to the user, the system immediately throws AgeRangeError Code=2 (AgeRangeService.Error.notAvailable Indicates the system was unable to share the person’s age range). This causes the app to bypass the intended age verification and log the child in directly. Steps to Reproduce: Sign in to a verified Parent Apple Account on the device and log in to the PTT app. Sign out of the Parent Apple Account in device Settings, ensuring the "Keep Data" option is selected. Sign in to a Child Apple Account on the same device, selecting "Keep Data" (Sign in and Merge data). Open the existing PTT app. Expected Behavior: The OS should present the system-level Age Range onboarding prompt to the new child user so the age range can be properly verified or shared.
Replies
0
Boosts
0
Views
564
Activity
3w
Testing Declared Age Range API on Production
Hello, We want to ensure that our Declared Age Range API is working correctly, in Production, but we had concerns on how this is done. Do we need to have an account created from Texas with a credit card/addressed based in Texas? What's the best approach to be able to test this in a live environment to ensure everything is working as intended? Thank You.
Replies
0
Boosts
0
Views
47
Activity
3w
Declared Age Range: is the sheet shown for Texas accounts created before June 4, 2026, and where can a decline be changed?
This is a question about expected behaviour rather than a bug. Environment iOS 26.x on iPhone 17 Pro Xcode 27. Swift, SwiftUI Declared Age Range capability enabled Context Our app is currently available without age restrictions. Starting in January 2027, we plan to restrict access by age in regulated US jurisdictions using the Declared Age Range API, and treat .declinedSharing as "age unknown." Before rolling this out, we want to understand what existing users will experience. Apple's June 3, 2026 developer news says "new Apple Accounts in Texas are now subject to the law." We couldn't find documentation on how the API behaves for Texas accounts created before that date. Code @Environment(\.requestAgeRange) private var requestAgeRange // ... let response = try await requestAgeRange(ageGates: 16, 18) switch response { case .sharing(let range): // use range.lowerBound / range.upperBound / range.ageRangeDeclaration case .declinedSharing: // treat as age unknown @unknown default: break }Questions For a Texas Apple Account created before June 4, 2026, on iOS 26.x, will requestAgeRange show the age range sheet, as it would in a nonregulated region? If the sheet is shown and the user declines to share: a. Where can they change that decision afterwards? Only under the Apple Account (Settings > [name] > Personal Information > Age Range for Apps), or also on the app's own page (Settings > Apps > [app] > Age Range for Apps)? b. Can the app show the sheet again by calling requestAgeRange, or does it return the cached .declinedSharing without UI until the user changes the setting? c. Is there a supported way to deep-link the user directly to that setting from the app? Thanks!
Replies
0
Boosts
0
Views
58
Activity
3w
TestFlight Declared Age Range Sandbox Scenarios Not Reflected in App Responses
Hello team, We are testing the Declared Age Range/Age Signal functionality in a TestFlight build and would appreciate guidance on the correct setup and testing process. Current Behavior Observed We are seeing inconsistent behavior between the Sandbox environment and the age-range results returned to the application. Scenario 1: Apple Account Signed In A regular Apple ID is signed in on the device. The TestFlight build is installed and launched. The application returns Verified Adult (18+). We then sign in to the Sandbox environment using a Sandbox Test Account and select a different test scenario (for example, a child/minor scenario). After relaunching the application, the age signal response still remains Verified Adult (18+). Scenario 2: Apple Account Signed Out We sign out of the Apple account from the device. As a result, TestFlight is also signed out. When the application is launched, the response changes to Unable to Verify. Even after changing Sandbox test scenarios (such as child, teen, or adult scenarios), the application continues to return Unable to Verify rather than the selected test case response. Based on this behavior, it appears that the application is not reflecting the scenario selected in the Sandbox environment. Questions What is the correct process for connecting an application to the Sandbox environment when testing Declared Age Range scenarios? Does the Apple ID used for TestFlight need to be associated with or match the Sandbox Test Account? Should the device remain signed in to a regular Apple ID while the Sandbox Test Account is used for testing? How does the app determine whether it should use the selected Sandbox scenario versus the signed-in Apple account? Are there any additional device settings, account requirements, or configuration steps required for Sandbox age-range testing? Is there a way to verify that the application is successfully connected to the Sandbox environment and consuming the selected test scenario? If the Sandbox scenario is configured correctly, should we expect the API response to change immediately when switching between child, teen, and adult test cases? At present, regardless of the Sandbox scenario selected, the application either continues to return Verified Adult (18+) or Unable to Verify, and we have been unable to validate the documented Sandbox test scenarios. Could you please provide guidance on the expected setup and testing workflow for TestFlight applications using the Declared Age Range feature? Thank you for your assistance.
Replies
2
Boosts
0
Views
133
Activity
3w
Declared Age Range and consent revocation in an entirely offline iPhone app
We are implementing regional age-assurance checks for an iPhone app that supports iOS 17 and later. It is a paid toddler app with no backend, app accounts, ads, in-app purchases, messaging or shared user content. All content is suitable for young children. Optional family voice recordings remain on the device. We plan to request Declared Age Range when Apple's regulatory signals require it, process the response locally, and avoid logging, storing or transmitting age data. We are seeking supported technical behavior, rather than legal advice or preapproval: What supported API or platform guarantee establishes that initial download/purchase parental consent was obtained? The age-range response does not appear to expose a separate initial-consent status. Apple's age-assurance Q&A says the platform prevents launching an app after a parent revokes consent. The implementation guidance also describes RESCIND_CONSENT through App Store Server Notifications. For an app with no backend or remotely accessible service, can local access rely on the platform's launch blocking, or is a notification server still required? If a server is required, what local enforcement behavior should it drive? What is the supported behavior for offline reopening and unavailable or network-error results, particularly on older supported iOS versions where the regulatory APIs are unavailable? Does platform enforcement also cover an app already running when consent is revoked, and how should an offline app handle that transition? Documentation or a sample showing this entirely local case would be helpful.
Replies
0
Boosts
0
Views
414
Activity
Oct ’26
Declared Age Range API availability on iOS versions below iOS 26
Hello team, We are currently evaluating the Declared Age Range API for supporting age-related regulatory requirements in our application, and we would appreciate some clarification regarding iOS version compatibility. Based on the documentation, we understand that newer age-related capabilities such as isEligibleForAgeFeatures and Regulatory Features are available only on newer iOS versions (for example, iOS 26.4+). We would like to clarify the following: Is the Declared Age Range API itself available only on iOS 26+ devices, or can age range information also be retrieved on earlier iOS versions? For users running iOS versions below 26, will the Declared Age Range API: Return age range information? Return a limited response? Be completely unavailable? Is our understanding correct that applications running on iOS versions earlier than iOS 26 cannot obtain age range information through the Declared Age Range API and therefore cannot determine whether age-related regulatory requirements apply? Are there any recommended fallback approaches for supporting age-verification or age-assurance requirements on devices running iOS versions below 26? Has anyone successfully implemented a solution that provides equivalent age-related signals or regulatory age-verification handling for users on earlier iOS versions? If so, are there any best practices or recommended approaches? Any clarification or guidance would be greatly appreciated. Thanks!
Replies
1
Boosts
0
Views
148
Activity
Oct ’26
DeclaredAgeRange: older-iOS fallback and consent revocation for a server-free utility
I am integrating Declared Age Range into the initial release of an all-ages iPhone utility with an iOS 17 deployment target. It stores user-created records only on the device and has no app accounts, backend, in-app purchases, subscriptions or remotely accessible data. The planned distribution includes the United States. On iOS 26.4 and later, the planned implementation checks AgeRangeService.shared.requiredRegulatoryFeatures and requests a range when .declaredAgeRangeRequired is present. On iOS 26.2–26.3, it uses isEligibleForAgeFeatures. Returned age information would be used transiently on-device, without persistence or export. A requested boundary of 18 would not restrict this all-ages app to adults. Two technical points remain unclear: The current Q&A says existing Apple Accounts on iOS/iPadOS 18 or earlier are unaffected. What supported fallback should an app use for affected new accounts on older supported versions, including iOS 26.0–26.1 without the eligibility property? When a required eligibility or age-range request temporarily fails, is there documented guidance for the access/retry behavior of an all-ages app? The documented notAvailable outcome can represent refusal or unavailability; the implementation should not misreport either as a completed check. The Q&A says Apple prevents app launch after parental consent revocation and also directs developers to RESCIND_CONSENT App Store Server Notifications V2. For a utility with no server, app account or remote data/access to revoke, is any additional client action or notification endpoint required? If so, what technical mechanism should connect that action to the fully local installation? I am seeking the documented API and system behavior, not a determination of legal compliance. References: Age assurance Q&A Update for apps distributed in Texas Requesting an age range
Replies
0
Boosts
0
Views
390
Activity
Sep ’26
DeclaredAgeRange API not triggering in regulated regions (Brazil, Utah) — Is it functioning in production?
Hi, We've implemented age assurance logic in our app using the DeclaredAgeRange framework to comply with regulations in Brazil (Digital ECA, effective March 17, 2026) and Utah (App Store Accountability Act, effective May 6, 2026). Our implementation calls AgeRangeService.shared.isEligibleForAgeFeatures on app launch to determine whether the current user is subject to age assurance requirements, and proceeds to call requestAgeRange(ageGates:) accordingly. However, after monitoring in production since the Brazil enforcement date, we've consistently observed isEligibleForAgeFeatures returning false for users in regulated regions, with no age range data being returned. What we'd like to clarify: Is isEligibleForAgeFeatures currently returning true for users in Brazil in production (not sandbox)? For Utah — given that HB 498 pushed the developer compliance deadline to May 6, 2027, will isEligibleForAgeFeatures reflect the original May 6, 2026 activation date or the revised 2027 date? Is there a known rollout schedule or gradual activation plan for these regions that would explain why the flag remains false even after the legal enforcement dates have passed? We've seen similar reports from other developers on these forums, so it seems this may be a widespread issue rather than an implementation problem on our end. Any official guidance on the current status of the API in regulated regions would be greatly appreciated. Thanks.
Replies
2
Boosts
2
Views
1.8k
Activity
Aug ’26
AppStore.ageRatingCode always returns 0 on real device — is this expected behavior?
Hello everyone I'm implementing age verification in my app to comply with upcoming age assurance laws (Utah, etc.), and I'm using AppStore.ageRatingCode from StoreKit to retrieve my app's current age rating. According to the documentation: extension AppStore { @available(iOS 26.2, macOS 26.2, tvOS 26.2, watchOS 26.2, *) public static var ageRatingCode: Int? { get async } } "Use this property to fetch the age rating for your app and compare it with the last known age rating to check if it has changed." However, calling this always returns 0 in my environment. Environment: Device: Real physical device (not simulator) iOS version: 26.4 Sandbox Apple Account: signed in via Settings → Developer → Sandbox Apple Account App Store Connect: app is registered and age rating is configured Xcode Scheme → Run → Options → StoreKit Configuration: None Code: func getAgeRatingCode() async -> Int? { guard let ageRatingCode = await AppStore.ageRatingCode else { print("Age rating code unavailable") return nil } print("ageRatingCode: \(ageRatingCode)") // always prints 0 return ageRatingCode } Questions: What integer values does ageRatingCode map to? (e.g., does 4+ = 4, 9+ = 9, 13+ = 13, etc.? Or is it a different internal code?) This mapping is not documented anywhere I can find. Is 0 a valid return value, and if so, what does it represent? Is there a known issue with this API returning 0 even when all conditions appear to be correctly configured? Any guidance from Apple engineers or developers who have successfully used this API would be greatly appreciated.
Replies
1
Boosts
0
Views
706
Activity
Jul ’26
Swift thread continuation crash when calling isEligibleForAgeFeatures
Hi, We’ve been observing crashes when calling “try await DeclaredAgeRange.AgeRangeService.shared.isEligibleForAgeFeatures”. Our crash logs show a “suspend resume partial function” crash from libswift_Concurrency.dylib swift::runJobInEstablishedExecutorContext. Based on our analysis, this is because once Apple’s eligibility check completes, it attempts to resume the Swift task continuation directly on its own internal background thread instead of yielding back to the Swift cooperative thread pool. Because the caller task inherits @MainActor isolation (due to a UIViewController being passed into our pipeline further up as it’s needed for requestAgeRange), the Swift runtime crashes when trying to reconcile the @MainActor context on Apple's foreign background thread. Has anyone encountered this and found a fix, and is this a known issue? Thanks!
Replies
1
Boosts
0
Views
362
Activity
Jul ’26