UPDATE: After further testing, the app is crashing but the iPhone simulator screen still shows the app for some reason.
I went from an app that was working in many respects to one that basically doesn't load at all with the new betas. This Xcode b5 and iOS 17b4 ain't it.
I've enabled "-com.apple.CoreData.SQLDebug 1" in my app target to see the sql logs and with Xcode 15b5 the app seems to loop (fetching infinite some sql data). Maybe that's the reason for your blocked UI too.
I seem to have the same issue and am investigating. Without any changes to my view, if I run the app that used to work on beta 4, the app becomes unresponsive. I've tracked it down to a couple of queries that look like this:
@Query(filter: #Predicate<MyModel> { $0.myProperty == "value" })
If I remove the filter, the view works and am no longer unresponsive.
I’ve got the same issue here, beta 5 has been a nightmare...
using a data attribute causes a crash, and any query with a predicate seems to cause a memory leak…
I tested this further, and predicates seem to cause memory leaks that jam the app. SwiftData looks simple, but it isn't, at least for now.
I face the same issue. The app freezes and consumes all memory it has while being at 99% CPU.
I think I had the same issue but when I installed Xcode 15 beta 6, the problem seems to have been resolved.
I was wrong, the app still goes to 99% CPU - but it doesn't hang anymore.
I am experiencing something similar with my Mac app. Having investigated using the Instruments tool, it seems that my app is constantly fetching data, causing the main thread to be blocked and making the UI unresponsive. I wasn't encountering this in Beta 5, but I am in Beta 6.
I did run a smaller app that leverages SwiftData on the iOS Simulator, and I'm not getting 100% CPU usage. Strange
It looks fixed on beta 6
Having the same issue on Xcode 15.0 Cpu eventually hits %99.9 percent and the app crashes. But with Xcode 14.3 Command Line Tools and Swift 5.8 everything works fine.