Can confirm that this is happening on iOS 18.0 RC with Xcode 16 RC when in Swift 6.0 mode and optimisations enabled. When optimisations are not enabled, or if we're in Swift 5 mode, the crash does not occur. From what I see the crash is with an assert - so the issue may be an assert in iOS that assumes the asynchronous renderer is being tied to a specific dispatch queue, and the optimised build possibly does not tie the renderer into a specific dispatch queue, as it possibly uses an actor. I hope this additional input helps. It would be a shame if we can't compile for Swift 6.0 for iOS 18.0, I hope this gets fixed...
Edit: Found the exception text too:
EXC_BREAKPOINT: BUG IN CLIENT OF LIBDISPATCH: Assertion failed: Block was expected to execute on queue [com.apple.main-thread (0x1eee64a80)] > com.apple.main-thread
ptsochantaris
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
It seems to be corrected now for me. Just started Xcode in the morning and the usual download, which should start and fail, succeeded.
Submitted FB FB15092093 for this
Same here!
Having exactly the same issue
I think in my case I found a workaround, and I'm posting it here in case it works for others too - I had SWIFT_REFLECTION_METADATA_LEVEL set to "None" for release builds. Setting this back to the default (All) seemed to do the trick and let appintentsmetadataprocessor extract the info during the archiving step. There's probably a more elegant solution, like telling the compiler to emit reflection data only for the file containing the app intents definition, so if anyone finds this workaround helpful and has a better way to do it, please shout :)
I am getting this as well. Xcode 14.0.1, running on Monterey 12.6 release (21G115)
Does anyone know of a workaround?
(Filed this as FB11602587)
Same question here
Same issue here :( Has anyone found/heard of workarounds?
From the iOS 15 beta 8 notes, this may help:
Using dispatch semaphores in an iOS app running in a device simulator on a Mac with Apple silicon running macOS 11 will cause the app to crash. (81783378)
Workaround: In Xcode, select Product > Scheme > Edit Scheme, then deselect Run > Options > Queue Debugging > "Enable backtrace recording."
Seems to be fixed now
Same here, beta 5 seems to have corrected the issue.