Yeah you're right. It seems to work fine now!

I see, thank you! That would be a workaround, but I don't like it either for my use case...

ok I see, I will try to make it more clear and create a new post below

Unfortunately there isn’t a way to serve an older version of the app to customers who cannot update their OS. What exactly does this mean? If I drop watchOS 10 (increase to 11) - will users with older Hardware (e.g. Apple Watch SE1) still receive the update on their iPhone (cause it runs iOS 18 or 26) and thus render the app useless as the companion app is no longer installable on their watch?

OK, I see, thank you. So how can I find out if it's safe to increase my minimum deployment target for the watchOS companion app without making the app useless for a part of my users? Since there is not an easy way to go back, I would rather not simply try it and mess around with my users. In any case: What is the recommended way to handle this?

Excellent question @khagan and thank you for you answer @Frameworks Engineer. I have one follow up: Is it still working the same with latest releases (iOS 26 and watchOS pre 26 (e.g. 10 or 11))? What happens if the user opens the detail page of my app on the App Store on iPhone: Will they "see" the update (i.e. enabled "Update" button) or will the update be hidden from them? In other words: Is updating only prevented from automatic updates or also from manually triggered ones?

That’s what I’m actually trying to achieve but it doesn’t work. Did you try it? Do you have a working example?

Thank you, that worked. Is it important to put my string catalog in a folder called Resources? (I realized mine had a typo but it still worked). When working with SF symbols in Texts, I'm wondering how this should work with generated symbols: Previously this worked (with strings instead of symbols): let image = Image(systemName: "exclamationmark") Text("myKey(image)", bundle: .module) When converting this generated key to a symbol it uses a String argument in the generated function :(

@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?

Yes, I sorted it. I also tried to list the views (steppers) manually instead of using a ForEach. No luck either...

Thank you!

@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.

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?

Ok - that's a bummer. Thanks for the clarification!

In other words: the #Unique macro cannot be used when the DB is backed by CloudKit, correct?