I still see the issue in Xcode 12.5 beta 3 as well. I see both a @StateObject initialized twice and onAppear called twice.

FYI this has been fixed in release version of 12.5

I’ll also add that I see this across two different applications that I use CloudKit in

Thanks for the tip about raising deployment target. That works for my testing.

Same here also! The response above from apple doesn't address the issue: After installing Xcode 14.3 beta, Xcode 14.2 can no longer build apps using rosetta.

I'm having a similar issue, where a query-driven parent passes results to another view. Updates are not reflected until leaving the view and returning to it.

I've confirmed that updates made in a background context are not being reflected in the query results. If I keep everything on the main actor it is fine. Certainly a bug in iOS 18 b1 and b2.

Still broken in beta 3

Beta 5 still broken.

Glad there is a fix coming - let's hope it makes it in time. This is still broken in iOS 18 / Xcode 16 beta 5. I'm going to hold off on the "workaround" as it is very heavy handed and inefficient. Any single change to the main context will cause all views driven by Query to redraw, regardless if they need to. Not sure how this one got past QA...

I’m seeing some differences in iOS 18 beta 6 (but still using Xcode 16 beta 5). I won’t call them “improvements” as the feature is still not reliable, but I do see changes propagating to the main context sometimes. There hasn’t been a single mention of SwiftData in any of the release notes so far: no known issues, nothing fixed. And that’s concerning, as I am seeing plenty of issues in addition to this one.

Seeing same issue on second app launch. Sometimes see the failures as “failed to parse response“ or “network connection was lost” errors.

req.assumesHTTP3Capable does not solve the problem for me. Things do work with an ephemeral session.

Good news: Appears to be fixed in Xcode 16.4 beta 1.

Still seeing this with Beta 2. To repro, I just build and run my Mac Catalyst app on macOS 15.5. My minimum deployment target is macOS 14 / iOS 17. Crashes immediately with dylib unable to find the framework. My app uses CoreLocation and MapKit. Thanks!