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.