As per Apple documentation , AuthorizationCenter API's. func requestAuthorization(completionHandler:) is available on iOS 15.0 and deprecated on iOS16.0. func requestAuthorization(for:) is available on iOS 16.0 and Later, but this API in still in Beta. For an app that is targeting to release now(before 16.0 release), how do we code? It appears that, if we use first api, it will deprecate when 16.0 comes and we don't know how it behave in 16.0. For second api,we can't use 16.0 API, as its a Beta API now.It is a subject to change. For first API, it is deprecated, for the second api, it is still in beta. Question is, What is the best way to handle this in code, with minimum future updates to App? Anyone from Family Controls team, Pls guide. Thanks.

We have an App with Content Filter Network Extension. We tested our App on physical devices (iPhone and iPad) and all looked OK. We uploaded our App build to AppStore Connect, for Test Flight. External Testers received the App, but noticed Network Extension is not triggering any function. App downloaded from TestFlight, dint ask usual (Allow/Not Allow) Dialog box to kick start the NW Extn. AppStore Connect Entitlements lists included NW Extn as seen in attached screenshot. Question is, Is there any limitation for Apps installed via Test Flight with Network Extensions? How to debug a Test Flight Test App or at least verify the presence of NW Extn and their logs? Is it not safe to expect, AppStore App in production and Test Flight Installed App should behave almost same? I noticed, In the settings, the Test App installed via TestFlight is not listed on physical device, is it that TestFlight App has Sandboxed the test App and its extensions and cannot behave as normal App with its full capacity? That means NW Extn Apps cannot be tested completely via Test Flight?