https://github.com/swiftlang/swift/pull/91791/ Here is a failing test from CI.

struct Input<T> { init(_ input: T) { } } struct Repeater<each T> { @SwiftUI.State private var storage = Storage() private var input: (repeat Input<each T>) init(_ input: repeat each T) { self.input = (repeat Input(each input)) } } extension Repeater { final class Storage { } } @main struct CrashDemoApp: App { private var repeater = Repeater(1) var body: some Scene { WindowGroup { EmptyView() } } }

https://github.com/vanvoorden/MemoProperty/commit/388a98d2fc7f732fe44a75abc8e4dce299537306 Actually… no… this one came back. The compiler fix that shipped seemed to fix one version of this crash. But I am now seeing another version of this crash. I will keep looking to see if I can find a clean repo. If you clone the MemoProperty you can also repro from Xcode_27_beta_6.

https://github.com/swiftlang/swift/issues/90929 It looks like the fix was already patched on 6.4. But the toolchain shipped in Xcode 27 beta 5 does not include it yet.

Sounds good. Thanks!

I am still a little unclear about some of these details… would I have the option to request a little more hands on support for this topic with DTS? My previous DTS request was 2023-10-27 and AFAIK I still have not heard back from Apple other than the automated replies. Is there any expected SLA estimate for a topic like this State question? If I requested a new DTS would I have the option for you specifically to be the engineer to help work on that request? Thanks!

Sounds good. Thanks!

FWIW… I am creating a ModelContext on an actor (and all queries and mutations go through that actor as serial operations). Is that ModelContext somehow "thinking" it belongs on main (which then throws an error later when the actor performs a serial operation)?

By any chance do we know if there are any known issues that might lead to false positive errors when using the ConcurrencyDebug argument with SwiftData? I am seeing some concurrency errors with a SwiftData stack… but I'm looking through how this stack is set up and I can't understand what could be leading to any kind of race condition. Wrong comment thread… this was meant for the previous comment. Sorry about that!

By any chance do we know if there are any known issues that might lead to false positive errors when using the ConcurrencyDebug argument with SwiftData? I am seeing some concurrency errors with a SwiftData stack… but I'm looking through how this stack is set up and I can't understand what could be leading to any kind of race condition.