How can an app determine whether a user is in Texas before calling requestAgeRange()?

Question

Created 2h

Replies 1

Boosts 0

Participants 2

Hello Apple Developer Team, I'm implementing the DeclaredAgeRange framework to support age assurance requirements related to Texas SB 2420.

After reading the documentation for:

AgeRangeService.shared.isEligibleForAgeFeatures

I noticed the discussion states: "Check whether the person using your app is in a region that requires Age Assurance."

My understanding is that isEligibleForAgeFeatures uses the user's location and account settings internally to determine whether age assurance requirements apply.

However, I am unclear about the expected implementation flow. My questions are:

Should developers manually determine whether a user is located in Texas (for example using Core Location, IP-based geolocation, or other methods) before calling requestAgeRange()?
Or is Apple recommending that developers simply call:

let eligible = try await AgeRangeService.shared.isEligibleForAgeFeatures

and rely entirely on the framework to determine whether Texas age assurance requirements apply?

If a user is located in Texas and age assurance is required, will isEligibleForAgeFeatures reliably return true without the app needing any location permission?
Is there any supported API that allows developers to know which specific region/state triggered the age assurance requirement, or should developers treat isEligibleForAgeFeatures == true as the only signal needed?

My goal is to implement the framework according to Apple's intended design while avoiding unnecessary collection of location data.

Thank you for any clarification.

Answer 1

Etresoft OP

39m

is Apple recommending that developers ... rely entirely on the framework to determine whether Texas age assurance requirements apply?

Yes.

My understanding is that Apple is leveraging its Apple Account information that will already have the users' legal residence.

It's possible that Apple may also use device location, but it would be Apple system frameworks performing that query, not your app. You wouldn't need to worry if location services is enabled or not.

When governments mandate these kinds of personal information disclosures, they also aren't going to allow personal privacy that would be in conflict.

All that being said, you should carefully review any result codes and gracefully handle unexpected failures. At Apple's scale, an app that works great 99% of the time could swamp your support and lead to thousands of complaints. Per day.