We have the same questions, and this ambiguity is creating a real implementation problem for developers. Apple’s developer communication for Texas SB 2420 says the changes go into effect starting June 4, 2026, and that developers can request age category data for Apple Accounts in Texas using the Declared Age Range API. However, in our own testing, even for a person physically located in Texas with 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.

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?