Age Range API - Sandbox Testing Available

Following feedback submitted for the same - https://feedbackassistant.apple.com/feedback/21097477

Pease see Testing Age Assurance in Sandbox for more information.

Testing requires using a device running iOS 26.2 or iPadOS 26.2 and a Sandbox Apple Account.

Use isEligibleForAgeFeatures to determine whether a person using your app is in an applicable region that requires additional age-related obligations for when you distribute apps on the App Store. For more information, refer to Next steps for apps distributed in Texas.

DTS Engineer Apple Use isEligibleForAgeFeatures to determine whether a person using your app is in an applicable region ...

Hi, thank you for information. Could you please share where isEligibleForAgeFeatures is placed in - there is no such property in AgeRangeService.shared in Xcode 26.2.0-Beta. Google doesn't know anything at all about it. Thank you.

we did went through the following WWDC video https://developer.apple.com/videos/play/wwdc2025/299/ and it is mentioned that Users can manage the cached responses in settings.

We did not see any such settings, not even under the sandbox account "Test Age Assurance".

Could you please let us know how do we clear the cached age response

Could you please share where isEligibleForAgeFeatures is placed in - there is no such property in AgeRangeService.shared in Xcode 26.2.0-Beta.

The isEligibleForAgeFeatures is available when using Xcode 26.2 beta 2 (17C5038g). To view the version of Xcode, select Xcode > About Xcode.

do {
    let response = try await AgeRangeService.shared.isEligibleForAgeFeatures
    // Handle response
    if response {
        logger.info("Eligible for age features.")
    } else {
        logger.info( "Not eligible for age features.")
    }              
} catch {
     logger.error("Fail to check eligibility for age features.")
}

Using Xcode 26.2, targeting an iPhone 17 Pro running 26.1, Xcode crashes saying the symbol isn't available.

The isEligibleForAgeFeatures property is actually available in iOS 26.2 beta or later. The documentation showing it as iOS 26 is a bug. Thank you for filing your Feedback report.

Upgrade your device to iOS 26.2 beta to test it.

I am currently using Xcode 26.2 Beta 2 and iPadOS 26.2 Beta and am signed in with my sandbox account (as I would be for IAP testing) I've implemented the code snippet above exactly and the function does not return a result or throw an exception. Any thoughts?

Xcode Version 26.2 beta 2 (17C5038g)

iOS Version 26.2 (23C5044b)

do {

            let response = try await AgeRangeService.shared.isEligibleForAgeFeatures
            // Handle response
            if response {
                print("Eligible for age features")
            } else {
                print("Not eligible for age features")
            }
        } catch AgeRangeService.Error.notAvailable {
            print("isEligibleForAgeFeatures not available error")
        } catch {
            print("isEligibleForAgeFeatures Unhandled error: \(error)")
        }

The above code snippet gets hang at the API call isEligibleForAgeFeatures

could you please suggest what is wrong here

Hello, we have had the same issue. Does this mean that the entire Age Range API should target users aged 26.2?

Using Sandbox testing I am always getting false returned for AgeRangeService.shared.isEligibleForAgeFeatures no matter which option I select under Age Assurance.

It works now after updating to the latest iOS 26.2 RC

Even with

XCode Version 26.2 beta (17C5013i)

iOS 26.2 beta (23C5027e)

I am receiving

Value of type 'AgeRangeService' has no member 'isEligibleForAgeFeatures'

as an error on

the provided code.

    public func testEligible() async
    {
        do {
            let response = try await AgeRangeService.shared.isEligibleForAgeFeatures
            // Handle response
            if response {
               print("[K]: Eligible for age features.")
            } else {
                print("[K]: Not eligible for age features.")
            }
        } catch {
            print("[K]: Fail to check eligibility for age features.")
        }
    }

For my testing:

try await AgeRangeService.shared.isEligibleForAgeFeatures

fails to even execute. The async task never comes back. Is anyone else seeing this behavior?

Edit: Would help to have the Declared Age Range entitlement added to the project. That fixed the issue for me. 🤦‍♂️

One thing I have noticed about the sandbox testing account is that it will still return the value of false for AgeRangeService.shared.isEligibleForAgeFeatures even if you have a valid scenario selected from the developer menu, if you happen to be signed into your sandbox account via the standard iCloud sign in flow (like how one would for Apple Pay sandbox accounts)

You must make sure you are not signed into your sandbox account anywhere else on the test device other than in the developer settings.

I cannot find Sandbox Testing > Age Assurance from my iPhone's Developer Settings.

From the documentation:

Test various age range scenarios on the Age Assurance page in iOS by following these steps:

1. Open Settings and select Developer.
2. Tap Sandbox Testing from the main menu.
3. From the Sandbox Testing screen, tap Age Assurance.
4. Choose from the available age scenarios based on your testing needs.

The following image shows what I can see from my iPhone's Developer setting screen. There is no Sandbox Testing for Age Assurance. What did I missed to make the menu appear?

I should also note that the iPhone is on iOS 26.2 RC. This is an iPhone SE (2nd generation).