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?

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, I will try to make it more clear and create a new post below

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

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

Thank you! Regarding SF Symbols in ControlWidgetToggle: I am using a Label with both text and system image. For testing I'm keeping the same symbol for .on and .off state, setting a fixed font, e.g. .font(.system(size: 20)) -> but it doesn't work: The symbol is rendered way smaller in the off state. Hint I'm using the ControlWidgetToggle on the lock screen bottom (the default place of flashlight/ camera).

Hi Albert, I created a sample project, you can find it here: https://github.com/benrudhart/ControlWidgetTest You'll be able to see that the SFSymbol for off state is rendered differently when the control is used on the lock screen. Also: the tint color/ foregroundStyle is always ignored

@DTS Engineer I guess you haven't seen my comment? sorry for posting in the wrong spot!