I know how to set up a parental gate to keep a child user away from a web portal for parents or guardians. But is it even OK with Apple (or just in general) to open a browser from inside a kids app? I can think of two ways to do this: Launch a browser with UIApplication.shared.open(). This takes the user (presumably an adult) out of the app. Will Apple object to this? Use an in-app browser with WKWebView. (Wrapped in UIViewRepresentable because I'm using SwiftUI.) Option 2 has some problems with Google SSO, which is a requirement for me. Some details in stackoverflow 2016 and stackoverflow 2019 and gitHub. I can't figure out how to apply the solutions in those posts to the SwiftUI architecture or even the UIViewRepresentable.

TL;DR App does not appear in Subscription list during free trial. Details We set up✻ a week free trial (for my two subscriptions (monthly, yearly) in App Store Connect: They were approved by Apple and the app is live. During the free trial, the app does not show up in the subscriptions list, neither in the App Store or the device's Settings. Our users can not cancel a subscription during the free trial. What could be causing this? We are currently updating the app to use StoreKit 2, so maybe that will help. But as you all know, testing subscription flow is not so easy. Even with Xcode's StoreKit Configuration files. Remarks For comparison, we subscribed to Apple News+, which has a free trial period. The app does show up in the subscriptions list, and has a Cancel Free Trial button: ✻ The unintuitive sequence for this in App Store Connect is [App] > Subscriptions > [Subscription Group] > [Subscription] > View all Subscription Pricing > Introductory Offers. (Where things in [brackets] will be your own names for app, subscription groups, etc.)

TLDR: Adding the Facebook SDK to a fresh, empty Xcode project yields an executable that links to AdSupport. Q: Can I prevent this? This happens without importing or using the SDK. The mere presence of the dependency (via SPM) in an otherwise empty app triggers the inclusion of AdSupport.framework in the executable, as confirmed by nm and otool. The phrase "Facebook SDK does not require AdSupport.framework to be included." appears in lots of searches, but is never accompanied with an explanation of how to exclude the framework. This is also a question for a Facebook forum, but I am posting it here as a question about build tools: Apart from downloading the SDK source and painstakingly commenting out the transitive closure of all references to AdSupport, ASIdentifierManager, and IDFA, are there any compile/link directives that could stop the inclusion of the forbidden fruit?