[quote='808703022, Shirk, /thread/759364?answerId=808703022#808703022, /profile/Shirk'] One point especially is giving me grey hairs right now - if an @Model contains an array of other @Model's and a property of one of those changes via a background context the changes do not propagate at all even if the workaround by DTS Engineer is applied. [/quote] Sadly, this still seems to be broken even in iOS 26 beta. The one workaround that seems to work is to add the related model to the FetchDescriptor.relationshipKeyPathsForPrefetching pased to a Query (for directly related models) or add a @Query specifically for the related models. For the latter, one need not use the actual result of the @Query itself (though the results must be faulted, by for instance, calling items.isEmpty). Rather simply fetching them through a @Query appears to allow update notifications to work even if a view uses a model accessed via a relationship. For instance. Suppose one has two models, Shelf and Item. Shelf.items is [Item] a
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags: