Great, I'm gonna try this. Thank you.
benrudhart
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
thank you
👍 done: FB11814100
Thank you. This is a pretty extensive "example". Does anybody know about a shorter Tutorial or Example. I'm interested in learning how to commission a Matter device via MatterSupport framework and also how to create/ maintain a custom Matter Fabric
Thank you. Yes, I'm aware of it. Unfortunately the video is not helpful to answer my questions.
In other words: the #Unique macro cannot be used when the DB is backed by CloudKit, correct?
Ok - that's a bummer. Thanks for the clarification!
Thank you - that is a really great post, lots of detail and background information.
Actually I would really love not to use any other crash reporter but the built in one provided by / the system. But unfortunately I don't get any results/ collected crashes for watchOS. Hence my question: Is there any workaround or anything I can do to capture crashes on watchOS?
@DTS Engineer is it possible that something has been changed in Xcode/ Crash Reporting Backend? I'm now seeing Apple Watch crashes in the Xcode Organizer, that I didn't see a couple of days ago.
Yes, I sorted it. I also tried to list the views (steppers) manually instead of using a ForEach. No luck either...
@DTS Engineer Ziqiao Chen: What is the recommended way of handling the situation if a SwiftUI View is holding a reference to the Model but the model gets deleted?
When using relationship in the model I figured out this:
Before accessing the relationship I check both: model.isDeleted || model.modelContext == nil. In either case I must not access the relationship property to avoid a crash.
-> is there a best practice way of handling this?