Issue persists with Xcode 16.1 iOS 18.1 that was released today (October, 28 2024)

I'm experiencing this issue after changing to pass PersistentIdentifiers between Actors instead of the actual model. I have standings, which are children of an event (one to many), When the children are updated by an @ModelActor, the changes are not reflected in the UI. The parent passed to the view as an @Bindable parameter. The updates to the UI do appear upon relaunching or navigating away and returning. I have a sample project I can share if anyone is interested. Observing the NotificationCenter, suggested by @DTS Engineer does not resolve this issue. Feedback Submitted: FB15281260

iOS18 watchOS11 macOS15 Xcode 16RC1 - Issue persists iOS18 watchOS11 macOS14 Xcode 15.4 - Issue persists I can install the app on to the phone but get an error when trying to install the app from the phone to the watch "This app could not be installed at this time". The app does appear on the watch, when I try to open the app, I get the error: Unable to Install "APPNAME" This app cannot be installed because its integrity cannot be verified I purchased the watch in June '24 to do watchOS development, I figured they'd sort this out with the release of iOS18 and watchOS11. I've performed every step in this thread multiple times.

Same issue today. Xcode 15.4 iOS 17.4 & 17.5. Submitted feedback FB13812722 (Complex Migrations with SwiftData do not work. Irrelevant Error: Fatal error: Expected only Arrays for Relationships - String)

I just resolved this issue for myself. Per @milutz in this response: https://developer.apple.com/forums/thread/733519. The relationship can't be set in the init which requires the relationship to be optional. To get your code to work, you'd need to update addItem() to set the relationship after you insert the new object.

It's because all SwiftData relationships must be optional, at least at this time and in my experience thus far. I've received this error quite a bit. Changing your code to the below should resolve your issue, I'd be curious if not class MyItem { var name: String var item: Item? init(name: String, item: Item? = nil) { self.name = name self.item = item } }

Actually, IT DOES seem that adding 'modifiedTimestamp' as QUERYABLE and SORTABLE (along with recordName) as indexes does allow it to pull down correctly. Upon the very first launch of the app, it does not have any of the Public data and currently takes quitting the app and restarting to get the public records to display. I assume this is something I can handle with polling. Thanks

Looks like you can now hide containers in the console. Select your container, click the title once the page loads and select 'Manage Containers'