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.

Solution here: https://developer.apple.com/forums/thread/770289?answerId=853752022#853752022

@Priff That might be a new issue then. If everything in your app was built from source with XCode 15.3, my understanding of the issue this thread is about is that it would all work. If that isn't working, that's a different root cause than ~everyone else was seeing here. @Samuellllll AFAIK, it's the same in cocoapods. If the empty project with no deps isn't working in XCode 15.3, that's new to me (and may be the same issue as @Priff is seeing).

Yes, that's because it's been by-design since XCode 14.3. You need to rebuild all of your upstream dependencies with a version of XCode 14.3 or greater. There is no known easy way to figure out which upstream dependencies must be rebuilt that works for every project; I just know how to do it for projects that use Carthage as posted above.