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?

Since there is no 'NEFilterFlow.sourceAppIdentifier' for the flow in handleNewFlow(MacOS NEFilterDataProvider), the one alternative is to find  the owner of the flow by the conversion of sourceAppAuditToken to designated identifier. For a simple WkWebView App, The designated identifier (derived from SecCodeCopyDesignatedRequirement) is returning as :- key : "requirements" value : designated => identifier "com.apple.WebKit.Networking" and anchor apple The above same value is returned even if we use a flow from Safari Browser. The expected output is to get “com.apple.Safari" , but not sure why “com.apple.WebKit.Networking” is returned. Even, bundle Identifier is also showing “com.apple.WebKit.Networking” instead of “com.apple.Safari”. (I used eskimo shared code https://developer.apple.com/forums/thread/128423?answerId=403770022#403770022 for BundleId and slightly modified code for designated identifier using kSecCodeInfoDesignatedRequirement) How can we differentiate flows from a wkwebkit-webview app and flows from Safari Browser flows? Any alternative approaches there?, lack of flow.sourceAppIdentifier field on Mac cause all these additional derivations per each flow is expensive at network extension level?

We are using Keychain Services and saving password using SecItemAdd() with kSecClassGenericPassword in our App. We know using the Keychain Access on Mac, we can see Keychain Items for MacOS Apps by the admin of Mac PC. Is there a way exist to view keychain items for iOS(iPhone/iPad).? My use case is, iPad(company device, not MDM) is shared between two or more persons.Each time app-user logs in to the same app using their own respective passwords(stored in keychain) . Security Concern is, such keychain items(passwords) will be able to see by others(including the owner of iPad/iPhone)? Ex: connecting to another Mac PC or some tool exist like Keychain Access present in MacOS or case when current local keychain is sync'd to iCloud Keychain. We don't want users of iPad/iPhone to see other users password. Is there any other solution exists other than Keychain?

I'm using storyboard for a Mac App. Quite a very simple layout, but it's kind of impossible for me to make it right with storyboard. I'm trying to set two text fields in same line, first text field width shorter than the second one width. They should appropriately resize when the super view resized. Things I tried. Two text fields pinned to both ends. Made 'width' with 'greater than' for both text fields, so that it occupies more width when view resize to bigger space. Behaviour is ,only the first text field box resizes, second text field doest not. I tried, changing CHCR, reduced priority for first text field width, but whatever may be the case, only the first text field stretches when view is stretched big. What we can do to make both text fields resize proportionally based on super view resizes.? Both text fields resize nicely only when Setting both text fields associated as "Equal Width".But my use case wants different width for both text fields and they should proportionally resized when view is resized. Using xcode 12.5. on big sur 11.4. Some screenshot attached.