Just noticed the error has been fixed. 🎉

@Hollycene @PavelRydvanskiy No update :( I've realized that the system consistently throttles the reload request in this scenario. I've also tried using push notifications to reload the widget but didn't work. As a workaround, I've set my widget timeline to 15-20 minutes so it reloads itself anyway. I also recommend submitting a new feedback report to Apple, as the original one is outdated.

Same here. Unable to upload app to App Store Connect. Xcode 26 beta 3 + new Composer icon + old asset catalog icon

FB19460396

FB19752732

RESOLVED: I used Realm database. After the app creates any FIFO file, the simulator can no longer be cloned. An error occurs during the simulator data copy process, indicating a lack of permission to copy FIFO files. This cloning failure prevents Xcode from launching tests properly. A simple way to reproduce this issue is to create a new iOS app, add a Realm database, and create any database file (since Realm creates FIFO files for interprocess communication). After that, the simulator can no longer be cloned. To work around this issue, I wrote a script that removes all pipe files from the simulator directory.

@HOsy No :( no luck with the popover. I workaround the crash by implementing a custom floating panel using UIViewControllerRepresentable.

macOS 26.2 RC. Still the same.

Same issue.

Same issue here. Is there any solution?

@DTS Engineer Hello! Thanks for the link🙏. I believe I encountered a new issue about Xcode Cloud. Please refer to https://developer.apple.com/forums/thread/810011

Reproducible with Xcode 26.2 (17C52) FB21322904

@DTS Engineer Thanks for the information! Based on my observations (after repeated experiments and spending quite a bit of my Xcode Cloud quota), it seems that projects with an Apple Watch target cannot be exported normally on Xcode Cloud using Xcode 26.2. iOS projects without an Apple Watch target do not have this issue. Project with Apple Watch app target:

Never mind. Building locally revealed the real problem.

@Zaba Hello! It’s very likely that your new Widget Extension is missing some necessary InfoPlist values or specific entitlements. You can try downloading the Archives that were successfully built but failed to export from Xcode Cloud, and then use the local Xcode Organizer to upload them to the App Store. If there are any configuration issues, the local Xcode will provide much more accurate error messages than Xcode Cloud.