Other threads: https://developer.apple.com/forums/thread/809829 https://developer.apple.com/forums/thread/810769

Which Topic are you asking? I think SignificantAppUpdateTopic should fail if both child and guardian accounts are registered outside of Texas, Utah, or Louisiana.

It was working in our app last I tested, but I don't know if we've exercised that path in the last 2 weeks. My expectation is that it should always return false currently and definitely return something.

We have a startup sequence that began with our ToS screen then went on to other loading screens. That startup sequence is part of out AppCoordinator and is called from didFinishLaunchingWithOptions. We added all of the ageVerification stuff to a new part of the startup sequence that is before the ToS screen.

@dev-forum-user Neither of those links say that AgeRangeService.shared.isEligibleForAgeFeatures is returning accurate values. My team's experimentation as described in https://developer.apple.com/forums/thread/809829 shows that it is always returning false until after the user has given permission to share age range, which is not required to access that instance variable and must not be required because this is meant to be checked before requesting that permission from the user.

I replied in the other thread about how we are using it, but here it is again: let isEligible = try await AgeRangeService.shared.isEligibleForAgeFeatures For the import, just @preconcurrency import DeclaredAgeRange

Are you calling it on the shared instance? This works for me: let isEligible = try await AgeRangeService.shared.isEligibleForAgeFeatures

I'm pretty sure "terminating" is not allowed. Our apps are going to present a screen that says they are locked out of the app with a link to the AppStore instructions for end users. https://support.apple.com/en-us/122770

The law is intended to allow parents to refuse consent in any case for minors of any age. https://developer.apple.com/documentation/declaredagerange/agerangeservice/iseligibleforagefeatures this parameter should only return True for people in TX. Currently it seems to be broken and always just return False though, even for Sandbox accounts in TX.

What I expect will actually happen is that the next time you try to submit a new version after January 31st, you will need to update the questionnaire and also "trigger the significant change consent process" to update your app. We won't know anything for sure until after January 31st though.

@mattn "If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect." That means to me that if you do not do it, your app will be "frozen forever at the current version". I don't think that's what will actually happen, but that's what Apple's words have said.

My interpretation of their posts here and in the documentation is that the AppStore is not going to limit apps on older versions of Xcode or targeting older versions of iOS, but also that ONLY apps targeting iOS26.2+ can be in full compliance with the Texas law. I am not a lawyer and am also very confused about who will be liable for what after January 1st.

Does this mean that iOS 17, 18, and 26.1 apps are no longer going to be allowed in the US at all then since every app in the US must comply with the Texas Law?

I think that part of the dialog is the current user's Age Range that would be shared, not the age range the app will gate with. In my testing, using 18+ accounts, I see "Age Range: Adult" in the dialog.

The current dialog is misleading though. Some apps have no child or teen content, i.e. the app shows the same thing for all users, but the app needs to make this request for anyone in Texas to use the app at all.