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

  1. 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?
  2. Is a sandbox tester's Age Assurance setting expected to stay in effect after the tester signs out? If so, what clears it?
  3. Can that state reach a TestFlight install or an App Store install on the same device?
  4. 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.