Previous to iOS 16, if you want to show a photograph picker for customers to decide on images from Photograph library, it’s important to depend on PHPickerViewController
or the older UIImagePickerController
of UIKit. It’s not troublesome to make use of it as you possibly can combine UIKit elements with UIViewControllerRepresentable
. That stated, it might be nice if the SwiftUI framework comes with a local view for photograph picker.
In iOS 16, Apple lastly brings PhotosPicker to SwiftUI that it has the identical functionalities as its UIKit counterpart. In case your app will solely assist gadget operating iOS 16 or up, you should use this new view for dealing with photograph alternatives.
Let’s see the way it works with some pattern code. Please be aware that you want to use Xcode 14 beta 4 to comply with this tutorial.
Utilizing PhotosPicker in SwiftUI
The PhotosPicker
view is bundled within the PhotosUI
framework. Earlier than utilizing it, it’s important to first import the framework:
Subsequent, we declare a state variable to carry the chosen photograph:
@State non-public var selectedItem: PhotosPickerItem? |
It’s fairly simple to deliver up the images picker. Right here is the essential utilization of PhotosPicker
:
PhotosPicker(choice: $selectedItem, matching: .photographs)) { Label(“Choose a photograph”, systemImage: “photograph”) } .tint(.purple) .controlSize(.giant) .buttonStyle(.borderedProminent) |
You instantiate PhotosPicker
by passing it a binding to the chosen merchandise and a photograph filter. Within the closure, you describe the looks of the button. With a couple of strains of code, Xcode ought to present you a button within the preview.
Should you click on the button, it shows a Images picker for selecting photographs from the photograph library. While you select a photograph, the photograph picker mechanically dismisses and the chosen photograph merchandise is saved within the selectedItem
variable.
Filtering the Images
The matching
parameter enables you to specify the photograph filter to use to the photograph library. Within the code above, we set its worth to .photographs
to point out photographs solely. If you wish to show each photographs and movies, set the worth of the parameter to the next:
.any(of: [.images, .videos]) |
The .photographs
filter consists of all photographs within the person’s photograph library. What if you wish to exclude reside images from the picture set? You possibly can set the worth like this:
.any(of: [.images, .not(.livePhotos)]) |
You utilize the .not
filter to exclude Reside Images.
Dealing with the Photograph Choice
As talked about earlier, the chosen photograph is mechanically saved within the selectedItem
variable, which has a sort of PhotoPickerItem
. So, how can we load the photograph and show it on display screen?
First, we connect the onChange
modifier to take heed to the replace of the selectedItem
variable. Every time there’s a change, we name the loadTransferable
methodology to load the asset knowledge.
.onChange(of: selectedItem) { newItem in Job { if let knowledge = attempt? await newItem?.loadTransferable(kind: Information.self) { selectedPhotoData = knowledge } } } |
Within the WWDC22 session (What’s new within the Images picker), Apple’s engineer confirmed us to specify the sort as Picture.self
. That is to instruct loadTransferable
to return an occasion of Picture
. Nevertheless, I couldn’t make it work on Xcode 14 beta 4. For this reason I used Information.self
as a substitute. Later, we are able to convert the information into an UIImage
object for displaying in an Picture
view.
The selectedPhotoData
variable is one other state variable that’s used to carry the information object:
@State non-public var selectedPhotoData: Information? |
To show the chosen picture in a picture view, we create an occasion of UIImage
utilizing the picture knowledge after which cross it to the Picture
view:
Picture(uiImage: picture)
.resizable()
.scaledToFill()
.clipped()
}
if let selectedPhotoData, let picture = UIImage(knowledge: selectedPhotoData) {
Picture(uiImage: picture) .resizable() .scaledToFill() .clipped()
} |
That is the way you deal with the picture choice. To recap, we retrieve the picture knowledge when a person selects a picture from the built-in Images library. We save the picture knowledge to a state variable (i.e. selectedPhotoData
). SwiftUI detects the worth change and triggers a UI replace to render the photograph on display screen.
Choosing A number of Images
The PhotosPicker
view can even assist a number of photograph choice. Let’s construct one other fast demo to see the way it works. Once more, we have now two state variables to carry the PhotosPickerItem
objects and Information
object. Because the person could choose a couple of images, each variables change into an array:
@State non-public var selectedItems: [PhotosPickerItem] = [] @State non-public var selectedPhotosData: [Data] = [] |
To assist a number of photograph choice, the trick is to make use of one other initialization methodology of PhotosPicker
:
Job {
if let knowledge = attempt? await newItem.loadTransferable(kind: Information.self) {
selectedPhotosData.append(knowledge)
}
}
}
}
PhotosPicker(choice: $selectedItems, maxSelectionCount: 5, matching: .photographs) { Picture(systemName: “photograph.on.rectangle.angled”) } .onChange(of: selectedItems) { newItems in for newItem in newItems {
Job { if let knowledge = attempt? await newItem.loadTransferable(kind: Information.self) { selectedPhotosData.append(knowledge) } }
} } |
This methodology has a further parameter named maxSelection
. We set the worth to 5
, which implies the person is allowed to assist as much as 5 images. On this case, we could seize a couple of images within the onChange
closure. What we did is to load every of the photograph gadgets and add it to the information array (i.e. selectedPhotosData
).
For this demo view, as a substitute of making a button on the centre of the display screen, we put the button within the navigation bar. Right here is the complete code snippet:
ScrollView {
VStack {
ForEach(selectedPhotosData, id: .self) { photoData in
if let picture = UIImage(knowledge: photoData) {
Picture(uiImage: picture)
.resizable()
.scaledToFit()
.cornerRadius(10.0)
.padding(.horizontal)
}
}
}
}
.navigationTitle(“Images”)
.toolbar {
ToolbarItem(placement: .navigationBarTrailing) {
PhotosPicker(choice: $selectedItems, maxSelectionCount: 5, matching: .photographs) {
Picture(systemName: “photograph.on.rectangle.angled”)
}
.onChange(of: selectedItems) { newItems in
for newItem in newItems {
Job {
if let knowledge = attempt? await newItem.loadTransferable(kind: Information.self) {
selectedPhotosData.append(knowledge)
}
}
}
}
}
}
}
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
NavigationStack {
ScrollView { VStack { ForEach(selectedPhotosData, id: .self) { photoData in if let picture = UIImage(knowledge: photoData) { Picture(uiImage: picture) .resizable() .scaledToFit() .cornerRadius(10.0) .padding(.horizontal) } } } }
.navigationTitle(“Images”) .toolbar { ToolbarItem(placement: .navigationBarTrailing) { PhotosPicker(choice: $selectedItems, maxSelectionCount: 5, matching: .photographs) { Picture(systemName: “photograph.on.rectangle.angled”) } .onChange(of: selectedItems) { newItems in for newItem in newItems {
Job { if let knowledge = attempt? await newItem.loadTransferable(kind: Information.self) { selectedPhotosData.append(knowledge) } }
} } } } } |
When there’s any adjustments of the selectedPhotosData
variable, SwiftUI will refresh the UI and show the images within the scroll view.
Should you get pleasure from this text and wish to dive deeper into SwiftUI, you could take a look at our Mastering SwiftUI e book.