DeclaredAgeRange API not triggering in regulated regions (Brazil, Utah) — Is it functioning in production?

Question

Created May ’26

Replies 1

Boosts 1

Participants 2

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.

Answer 1

mikko1 OP

2w

We are seeing the same issue and would also appreciate a clear answer from Apple.

Apple’s own developer news page for Texas SB 2420 states that “These changes will go into effect starting June 4, 2026” and that developers can request age category data for these Apple Accounts through the Declared Age Range API.

However, even when testing with a user physically located in Texas and using an Apple Account registered to Texas, isEligibleForAgeFeatures still returns false.

This leaves developers in a very difficult position: Apple has publicly communicated effective dates and developer-facing APIs, but the production behavior does not appear to match that communication. If this is expected behavior, we need Apple to document it clearly. If it is a rollout issue, we need a timeline. If there are additional eligibility requirements beyond account region and physical location, those also need to be documented.

Can Apple please clarify the following:

Is isEligibleForAgeFeatures expected to return true in production for Texas Apple Accounts after June 4, 2026?
What exact conditions must be met for isEligibleForAgeFeatures to return true? For example: Apple Account region, current device location or something else?