Post

Replies

Boosts

Views

Activity

Reply to Xcode 12.5 WatchOS simulator updateApplicationContext() is broken
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!
Apr ’22
Reply to Xcode 12 beta 4 can not download and install Symbols for watchOS 7.0 (18R5350e). Failed to download package from ADC.
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.
Mar ’21
Reply to In app purchase fails only in App Store review
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!
Jul ’20
Reply to didReceiveApplicationContext not responding in iOS 13.
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.
Dec ’19