Hi Ritesh,Did you find a resolution to this other than reinstalling the watch App? I am getting the same error messages:[WC] -[WCFileStorage loadAppContextDataFromInbox] error loading in application context from inbox NSFileReadNoPermissionError -> EACCESI can confirm that the only way to get the communication up and running again is to delete the Watch app and reinstall it.It seems to start happening after transferring volumes of data (a few megabytes in multiple dictionaries) between the watch and ios app. Perhaps there is some sort of undocumented limit on data transfers in place? I also find that when transferring a lot of data via context updates eventually they stop working without the above error message and the only solution seems to be to power down both the watch and the phone. In both instances it appears to only affect context updates, not messages.I'm now moving the bulk of data transfers to the background file transfer mode to see if that avoids the problem. I this mode you can send a metadata dictionary, which will suffice as a means of transferring the context dictionaries I'm sending now.

Well I'm based in New Zealand and I have the issue. I contacted Apple support and provided them with screen shots etc. Hopefully it will be resolved soon!

I have just submitted this post https://developer.apple.com/forums/thread/654583. I just checked my Agreements, Tax and banking in App Store Connect and found that the contact info needed updating. I'll resubmit my app for review and see what happens.

The issue appears have been that I had some missing information in App Store Connect. Specifically, I was missing some contact information. The lesson here is before submitting your app for review check that there are no agreements to sign, or anything missing under Agreements, Tax & Banking. See this discussion: https://developer.apple.com/forums/thread/120852?page=1#621644022 Anyway it's working for the reviewers now. Happy days!

I had a very similar issue after installing WatchOS 7.3.2. No matter what I tried I couldn't get the Watch symbols to download. I even raised a TSI. While I was waiting for a response from Apple I tried opening another project and noticed that the symbols were being downloaded successfully. Then when I subsequently opened the project experiencing the issue I found that the symbols were now successfully downloaded! So, if you experience this issue it might be worth checking if it only affects one of your projects.

I just had the same problem. No response following an SKProductsRequest. I was able to resolve it by rebooting my phone.

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?

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!

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

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

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!

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.