6 years later and still an issue. It's not just for watch but widgets, notifications, etc.

Apologies forgot to mention I was using Xcode beta / iOS 16. I was trying to see if the behaviour changed.

Sorry I missed the "Form", that renders the screen very different but does indeed display the label. Outside of the Form tho, the Picker behaves inconsistently.

This didn't work either on iOS. The label does not render.

I take it back.. iOS does work perfectly. Sometimes I have to step away from testing it for a week, then I make changes to the iCloud management portal and the push notification gets sent to iOS using the exact same build.. no code changes. So there is some throttling of some sorts in iCloud, but more likely in iOS because I see them in the Console log but doesn't trigger the didReceive notification event sometimes in those throttled times. However, never have I seen this work for watchOS :(. Maybe it's not meant to if its a companion app to iOS (even though I have it set to "Supports running without iOS installation"). Wondering if anyone tried this with an independent watch app?? At this point, I'm thinking of letting iOS receive the push notification then use WatchConnectivity to tell the watch which maybe the recommended route but just more code and communication flows blah.. First Apple takes away AppGroup sharing with watchOS, then they didn't offer NSUbiquitousKeyValueStore for watchOS, now this.

Also on 15.3 but now can't get it to work again in 15.4. Silent notification seems really flaky overall and unreliable. I've gone down a rabbit hole from posts going back to iOS 11 with the same issue. Maybe I hit some limit with all the testing and just stops until it feels like starting again. Not sure but it's unreliable, inconsistent on iOS it seems, and don't think I've ever seen it work on watch.

I think I understand how it's related now.. SwiftUI is probably breaking Xcode

Only works in a real device but not in the simulator 😐