Anyone by chance ever experience this?

I have the same issue, submitted a ticket to dev support, haven't heard back in two weeks.

@Claude31 Thanks I will try that out and report back.

@joadan What you're saying about an array being a value type even if it has reference types makes sense to me. What I'm a little confused about is that when I pass subcategories by reference in the sample project I have (i.e. passing it as a parameter to a struct where it's declared as var subcategories: [Subcategory], it still does update when I mutate the array using project.subcategories?.removeAll { $0 == subcategory }. Regarding what I was saying in the paragraph after the second block of code, I just meant that you can't unwrap the array like normal: if var subcategories = self.project.subcategories { subcategories.removeAll { $0 == subcategory } } and instead have to do this: if let subcategories = self.project.subcategories { self.project.subcategories?.removeAll { $0 == subcategory} } Just feels off to me.

@joadan but for self.project.subcategories?.removeAll { $0 == subcategory} you won't know if it didn't removeAll because subcategory didn't exist in the array, or if subcategories was nil to begin with because it didn't load from CloudKit / SwiftData.

@DTS Engineer Thanks for that. Just had one last question, when you say "if the other part of your app prefers to consume an empty array", what do you mean by that?