Looks like if userInfo is included in the CLKComplicationDescriptor they don't sync between the watch and iOS Watch App, however removing userInfo from my descriptors causes them to work as expected. Is this a bug? What is the point of userInfo if you can't even use it. EDIT: After some further investigation and testing it looks like the only thing that works in the userInfo dictionary is string types. Adding unsupported data types causes an exception stating it needs to be one of the base NS types (NSData, NSString, etc). However even with those types it fails. The only way I can get it to work is by using Swift strings for the key and value.

UserInfo in complications only supports Swift Strings for both the key and value. Seems like a bug to me, but this is the only way for them to actually work.

After the user restarted their watch that one seems to be working fine. Now they are having an issue with a different complication that was working before. When WatchOS kills the complication for taking too much CPU time, how long before it is able to "update" again? Not sure that is what is happening since these are very simple complications that share the same data so it's very odd that 4 of them work fine on the same watch face, yet one seems to always have an issue for them. They are the only user with the issue currently.

Embedding without signing didn't solve the issue for me. Still present in the latest beta.

It's still crashing for me too. Would be great if this was resolved soon. I have abandoned Xcode 14 and all iOS 16 work for now since 90% of my testers are on iOS 15 and they want their widgets. I also noticed since Xcode 14 beta 3 that it is replacing/updating a lot of frameworks in the systems /Library/Developer path which now makes Xcode 13 unusable due to obscure build errors during the linking phase. I haven't seen this sort of problem with the Xcode betas since the very early days.