Same issue.

macOS 26.2 RC. Still the same.

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

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.

FB19752732

FB19460396

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

@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.

Just noticed the error has been fixed. 🎉

Might be relevant: Cannot load cross-import overlay for 'StoreKit' and 'SwiftUI': Input/output error (declared by '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.1.sdk/System/iOSSupport/System/Library/Frameworks/StoreKit.framework/Modules/StoreKit.swiftcrossimport/SwiftUI.swiftoverlay')

FB15932459

Update On iOS 18, AppShortcutProvider+AppIntent+IntentDonationManager can reliably make the system display the corresponding shortcuts in Spotlight. This works on both the simulator and real devices.

FB15290642

@Developer Tools Engineer FB15244277

@DTS Engineer @Developer Tools Engineer Thank you for your fast response and detailed information! ❤️ After further investigation, I found the implementation of JSONSerialization seems to be incorrect. When using .sortedKeys options with JSONSerialization, the keys are always sorted in the "Finder-like" order instead of lexicographic order. This is inconsistent with the documentation. But I'm not sure what is the expected behavior. I can reproduce this issue with Xcode 16.0 on the latest macOS 15.0 and iOS 18.0. I've submitted a feedback FB15177571.