Thanks for the feedback. I just noticed that the same issue applies to the includehiddenassets of PHFetchOptions.: https://developer.apple.com/documentation/photokit/phfetchoptions/1624780-includehiddenassets?language=objc In this case the documentation was not updated for iOS 16, yet the includehiddenassets property seems to be ignored, if the user has turned on to require authorisation for hidden assets. Also it changes the behaviour of existing apps without a way to work around it. Makes it sense to fill a feedback on this? If it's not feasible to provide authorisation within apps for access, at least a property to check if the user has enabled authorisation would be useful.

Filled FB10577529 for this issue.

Any news on this issue now that iOS 16.1 is released? We had already some customers asking for "Importing into the Shared Library" and "Filtering between all photos, shared library and personal library".

A simple use case is a backup application (e.g. for backing up to a NAS), where the user has the choice to only backup the personal library, only the shared library or both. I filled a feedback (It's still open) for such an enhancement around iOS 16 beta times. It's however still relevant as such a feature (and therefore API extension) has also been requested by numerous of our users since the Shared Library was introduced in iOS 16.1. Please have a look at: FB10577368

Did you ever solve this issue? In my testing the @available annotation for the AppShortCutsProvider is totally ignored. I have AppShortCuts appearing on IOS 16 that are only compatible with iOS 17 and also lead to crashes.

Reported as FB13711844

Since you have experience with PHBackgroundResourceUploadExtension, I'd appreciate any guidance on debugging (=attaching the debugger to the extension) it during development. I've run the extension target with Photos (and my main app), then taken new photos, but process() is never called. Have you encountered this, and if so, how did you get it working? Thanks in advance!