Thanks for your fast reply. I tried implimenting what you said would work, but I wasn't able to figure out how to do it. Could you please provide a simpler way/make this more clear?

I tried this, but it looks like it immediately crashes when I open the view. No errors are given by swift either, just "Preview Crashed". When I build this and run in the simulator, it says "Index out of range." I looked at the code but cannot see what is happening, could you help?

Could you show the file where the ModelContainer was set up? That would help find the issue.

UPDATE: After further testing, the app is crashing but the iPhone simulator screen still shows the app for some reason.

I updated my Mac to the developer beta and a new problem is appearing. View the new thread here

I just looked into this some more, and found out that it(according to Xcode, I checked activity monitor and it wasn't) using 100% cpu(even though I am using M2 Pro MacBook Pro 14-inch), high energy impact, and lots of memory. In beta 4, it barely used any. I enabled -com.apple.CoreData.SQLDebug and it wasn't showing anything. My iOS app seems to be in an infinite loop of fetching data. It might be related to that but I am not sure. You can view that thread here.

Update to 14.0 Beta (23A5301g) and Xcode 15 beta 5. (Beta 5 is quite broken, but there isn't another way around it.)

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.

You should call support. The forums can't help much.

It might be possible, but I think the way to go would be to buy a Mac mini if you are on a budget, or opt for something like a MacBook if you are willing to spend that much. Another thing is that you would need Xcode 15.

I would wait until beta 6 and try those steps you took again because of how broken Xcode 15 beta 5 is.

You cannot run Xcode 14 on Sonoma.

Try downloading the simulator, and install it when Xcode is transferred to the other device.

What settings did you use to create them and on which platform?

Based off the exception type, it looks like you don't have edit access in that folder.