MacKuba

(See full blog post here)

PHPicker: new system-provided picker screen that gives you access to photos and videos from the user’s photo library

New design and new easy to use API

It’s recommended that you use this picker instead of building your own custom photo selection UI

New version includes:

• an integrated search
• easy multi-select
• zoom gesture

PHPicker is private by default:

• the picker screen runs out of process and talks to the app via XPC
• your app has no direct access to the photos library
• it doesn’t need to get photo library permission (don’t ask for it unless you *really* need it)
• you only get selected photos and videos in response

Elements of the API:

PHPickerConfiguration – lets you specify limits and filters:

• selectionLimit – number of items that can be selected (1 by default, 0 = unlimited)
• filter – e.g. .images or .any(of: [.videos, .livePhotos])

PHPickerViewController – the main VC handling the picker

• the picker doesn’t dismiss itself automatically, call picker.dismiss(animated:) when you get the response

PHPickerViewControllerDelegate – delegate for the picker

• picker(_: didFinishPicking results:)

PHPickerResult – an array of these objects is passed to the app in response

• get itemProvider from the result
• check itemProvider.canLoadObject(ofClass: UIImage.self)
• get the image via itemProvider.loadObject(ofClass: UIImage.self) { … }

You can normally extract picked photos from PHPickerResult item providers without touching the PHPhotoLibrary at all, but if you do need to access the photo library anyway, then pass it to PHPickerConfiguration.init and get assetIdentifier references from the picker results

If you use PHPicker with photo library access and you only got limited access to a subset of photos, then:

• PHPicker will still let the user choose photos from their whole library
• but the selection you have direct access to will not be extended by what they choose in the picker

The photo library APIs from UIImagePickerController are deprecated