I found the issue! It was actually in my code - although it wasn't obvious from the error message. I was using c2i_ASN1-INTEGER for receipt validation. The reason why I didn't find it was that I included the underscore in my search string, whereas the method is c2i_ASN1-INTEGER in my code. Anyway, I substituted it with the d2i_ASN1-INTEGER and that fixed the problem.

I have the same issue. My app is a mix of UIKit and swiftUI running in WKHostingControllers. The fact that the close button has shifted down a line is causing me all sorts of grief. It seems a bit pointless to me and a total waste of screen real estate!

This can be accomplished in awake with context: override func awake(withContext context: Any?) {         setTitle("<")     }

Me too! Surely there's a fix for this?

I've installed the latest Mac OS (12.3.1) and Xcode 13 and although I can send messages and context updates to/from real devices (a series 7 watch to an iphone 13 mini) I can only send them in one direction i.e. watch to phone, on the simulator. The Series 5 simulator works for messages, but not context updates. The Series 6 doesn't communicate with the companion app in either direction!

My watch app is writen in Objective C and WatchKit. It is very large with many WKInterfaceControllers. I only need one screen to update in Always-On mode. Rather than recode my entire user interface in SwiftUI is it possible to code just that single screen in SwiftUI and call it from WatchKit?