We got an answer! https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app#Check-eligibility-for-age-related-features

We got an answer! https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app#Check-eligibility-for-age-related-features

@DTS Engineer None of the above linked documents answer any of these 4 questions. Based on https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app we can answer questions 1 and 4 ourselves. We can expect that for all users with Brazilian App Store accounts: Before the date, isEligibleForAgeFeatures will return false. After the date, isEligibleForAgeFeatures will return true. For Question 3, the Brazilian law says: This Law shall enter into force six months after the date of its publication. And I think it was published on September 17, 2025, so it should be effective March 17, 2026. I don't know anything about Question 2's answer.

Whether iOS provides any mechanism or API that allows iPhone apps to trigger or request parental re-approval after the application has already been installed PermissionKit has that for you: https://developer.apple.com/documentation/PermissionKit/SignificantAppUpdateTopic Also from which iOS version this capabilities will work & how to handle lower iOS version which is not supporting. The APIs seem to only be supported in iOS 26.2 and above. The laws say that "A developer shall verify through the app store's data sharing methods...." Since Apple has not provided any "data sharing method" for users on iOS versions before 26.2, my interpretation is that we do not need to do any age verification for users on older versions of iOS, but I can not be sure at this time and this is not legal advice. I doubt Apple will provide any recommendation since doing that could be considered legal advice. The only way we will know for sure though is for the deadlines to pass, a law to come into effect, a relevant law suit filed, and a court to rule on it.

@DTS Engineer When my team has tried to submit our apps with PermissionKit added to use SignificantAppUpdateTopic, AppReview always rejects us because they cannot exercise PermissionKit: Please provide us step-by-step instruction regarding how to locate below feature. PermissionKit Since PermissionKit flow in our app is only used when the app has had a Significant Change, there is no way for them to test it during AppReview. How do we tell them to test it so we can submit our app?

"isEligibleForAgeFeatures API is always returning false" is correct behavior currently because there are no jurisdictions where any of these laws currently apply. TX is blocked by an injunction and UT doesn't start until 2026-05-06. I don't know if there is any way to mock/force that API to return True.

I and my team have asked this twice on these forums and no one from Apple has responded. My assumption is that we should fully rely on that API because apps that don't already have user location permission should not need to request it. Also, the user's current location is unrelated to if the law applies to them; it applies to all app store accounts that reside in the affected jurisdiction, regardless of where they are when they use the app.

@DTSEngineer Can you please reply to one of these threads with the expected bahavior of isEligibleForAgeFeatures ?

@DTSEngineer Can you please reply to one of these threads with the expected bahavior of isEligibleForAgeFeatures ?

We asked weeks ago and got no response from Apple. https://developer.apple.com/forums/thread/809829 My assumption is that it should currently return false everywhere and begin to return true only for users from Utah and Louisiana whenever those laws some into effect. https://developer.apple.com/forums/thread/809829?answerId=870440022#870440022

Given the Federal Court Injunction on Dec 23, will isEligibleForAgeFeatures now accurately return false for minors in Texas?

Related to termination, my advice is to NEVER terminate your app. In the past, some of our Apps had a Decline button on the Terms of Service (ToS) screen that terminated the app, but App Review flagged that behavior as a Crash and blocked our app submission. Now our ToS screens only have an Accept button and the user can press that or they can close the app themselves; this always gets through App Review. For Age Verification, we have implemented similar: If an eligible user Declines to share their Age Range or is a minor without parental consent, they see a screen explaining that they are blocked with a link to App Store documents about the law and settings. There is no way out of that screen other than closing the app.

Apple's hands have been tied Apple could have implemented it much more simply. The way Google Play is doing it is simple to understand, clearly documented, easy to implement, and just as privacy-secure for end users. https://developer.android.com/google/play/age-signals/overview From my reading and discussions, I believe raising an app's Age Rating to 18+ and Geo-Blocking Texas are both NOT COMPLIANT with the Texas (or UT (later in 2026), LA (later in 2026), and CA (January 2027)) law. AgeRangeService.shared.isEligibleForAgeFeatures is currently broken though: https://developer.apple.com/forums/thread/809829 My team is working under the assumption that it will eventually work and it's on Apple to fix their backend so it correctly returns True or False based on the user being in the impacted region.

It's known to crash with iOS 26.2 RC and XCode 26.2 RC. I've seen it working in my tests with the released versions of iOS 26.2 and XCode 26.2.

Answering the question in the OP and not the discussion about the blue warning box: I am not a lawyer, but my reading of the TX law is that implementing the age verification and parental consent workflows applies to all app developers regardless of target age range of the app. It DEFINITELY applies to all apps usable by minors in TX.