When using PhotosPicker in SwiftUI to let users pick a photo, it will fail to load after switching to the "Collections" tab on iOS 18. This issue doesn't occur on iOS 17. Additionally, using PHPickerViewController will still have the same issue.
The code is pretty simple:
struct ContentView: View {
@State private var selection: PhotosPickerItem? = nil
var body: some View {
VStack {
PhotosPicker("Pick photo", selection: $selection)
}
.padding()
}
}
And I create a repo for this code: https://github.com/JuniperPhoton/PhotosPickerIssueiOS18
This issue has been reported via Feedback app, and the report ID is FB15069998.
I tested in the Xcode 16 Beta 6 and iOS 18 Beta 8. However with the Xcode 16 RC and the iOS 18 RC, this issue still exists.
Hoping to find out any workaround to resolve this issue. Thanks.
juniperphoton
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Hi there. I build a ControlWidget to let users perform action in the control center.
The Image View inside the ControlWidgetButton fails to render the images from the Assets. It seems like it can only render Symbols from SFSymbols using the Image(systemName:) API.
Here is the code to reproduce this issue:
struct LockedCamWidgetExtensionControl: ControlWidget {
var body: some ControlWidgetConfiguration {
StaticControlConfiguration(
kind: "com.juniperphoton.widget.control"
) {
ControlWidgetButton(action: MyAppCaptureIntent()) {
Image(.actionButton)
}
}
.displayName("Launch Camera")
.description("A an example control that launch camera.")
}
}
Note that I can ensure the image can be displayed in the normal Widget in Home Screen and its target also includes the Widget Extension itself.
So is this a feature or a bug? If we can only use the SFSymbols provided by the system, then users are hard to distinguish the difference between apps.
I tested the app built agains Xcode 16 Beta 5 and iOS 18 Developer Beta 6.