Follow-up question! This webpage has a section on "Regulated Financial Services Disclosure": https://developer.apple.com/app-store/app-privacy-details/#regulated-disclosure I work on a regulated financial app, and we do use some API calls that would be affected by the new Disclosure rules - and these calls are used by us exclusively to assist our fraud-prevention efforts. I believe I can tick all four bullet points in that section. Will there be a process to apply for exemption? None of the NSPrivacyAccessedAPITypeReasons are correct for our use case, and the nature of our fraud-prevention models requires that some "derived information" is sent off device. Matthew

The file was not added to the right target under Target Membership And that correct target is.....?

I see this too, with iOS 15 beta 2. Beta 1 was OK.

Have you tried adding ITSAppUsesNonExemptEncryption:NO to your iOS target's Info.plist?

I added ITSAppUsesNonExemptEncryption:NO to my iOS target's Info.plist, and pushed another build. This seemed to unblock things. (Or maybe it was just a co-incidence!)

For anyone else with a freezing WatchOS 7 beta 3: I think it’s the watchface. ”Numerals Duo” freezes regularly. “California” does not.

I had the same problem too - and also couldn't register TouchID fingerprints. Resetting the SMC fixed it - thank-you @mattprowse.

NavigationView is a container for other views; it starts by showing its child view - the root view in the navigation stack - and the user can use NavigationLinks to navigate to second view, which will be shown inside the same parent NavigtionView. So it's the child's responsibility to provide content to display - and that includes the title.