Greetings fellow WatchOS app developers, On the iOS simulator running 12.5 beta, the method updateApplicationContext() claims that it succeeded, no exception is thrown and yet the WatchOS app, running on a WatchOS 7.4 simulator never gets its language session(_ session: WCSession, didReceiveApplicationContext applicationContext: [String : Any]) method invoked. Same issue in the other direction: The WatchOs app claims success on updating the iPhone app's application context. Yet nothing arrives. This works fine on real devices running iOS 14.5 beta and WatchOS 7.4 beta. Are there any workarounds? Due to Covid-19, I'm working remotely and can't debug on a real device, and need to be able to debug a critical WatchOS 7.4 specific issue. Thanks in advance!

Hi, Xcode 12.5's iPhone simulator silently fails in sending its app context via updateApplicationContext() to the Watch simulator. No exception is thrown, so it appears as if everything is ok - but not really because the WatchOS simulator never gets the app context This works fine on real devices as well as earlier versions of Xcode. Doing a updateApplicationContext() from the WatchOS simulator to the paired iPhone simulator does work. I filed a bug report for this issue, because this behavior has been in Xcode 12.5 since the beta version: FB9095737 (Xcode 12.5 WatchOS Simulator never receives application context from iPhone counterpart) Before anyone says "why not debug on a real device instead?", please be aware that due to the pandemic, while I do test on real devices, I can only debug on a simulator. Thanks

In order to determine what is wrong with my simulators' behavior, Apple is asking me to run sysdiagnose on all devices involved. However, aside from my mac mini, all other devices involved this issue are simulators. Can one run sysdiagnose on a simulator for iOS and WatchOS? And if so how? Thanks in advance

Our WatchOS app requires that http redirects work in a reasonably timely manner, and it has been the case until WatchOS 7.4 beta. Now in WatchOS 7.4 beta they take such a long time that the application simply hangs with no errors being returned back to the app. We've looked at the release notes for WatchOS 7.4 beta and there's nothing in there about slow HTTP redirects. Has anyone experienced this issue with the latest 7.4 beta? Is this a known issue? Thanks

Greetings, Our WatchOS 7 app offers the user a complication for each of the items in the app. So if the app currently has only 5 items, we have 5 complications for each complication family type, if the user has 8 items we have 8 unique complications for each complication family and so on. This is incredibly useful, because we can now have multiple items on an active watch face. We've noticed that if we have more than 10 items only the first 10 register in the getComplicationDescriptors() call. The rest are not visible to the user and as a result cannot be selected. However, we've noticed that Apple's World Clock app, which shows the time for different cities has no limit. i.e. if the clock app has 18 cities in it, the user can pick from 18 complications for each complication family . When will we be able to offer more than 10 complications? Thank you