While for watchOS 6 simulators the WCSession.default.transferFile(...) function from watchOS to iOS was already broken (FB7812483) while working flawlessly for watchOS 5 now with a Xcode 12 / watchOS 7 / iOS 14 beta combination that's still the case (FB7812526). Other things like WCSession.default.updateApplicationContext(...) are now also broken (FB7806876) which makes it basically impossible to work with WatchConnectivity and simulators for watchOS 7. I used https://developer.apple.com/documentation/watchconnectivity/using_watch_connectivity_to_communicate_between_your_apple_watch_app_and_iphone_app as an example project but originally discovered those problems in another app. I'm a big fan of Apple Watch but this situation makes it really hard to properly develop for it.

Is it possible to share data/settings between an iPhone app and a standalone WatchOS app? Or have the watch app connect to the iOS app to send messages if available? I know how to do it the old way, but I'm moving my Watch app to be standalone and don't see how to communicate or share settings. Thanks

In previous versions of Xcode you were able to pick a simulator pair (iOS + watchOS) when running a watch app. In Xcode 12, I cannot find the option for this. In fact, the only way I seem to be able to test connectivity between my iOS and watchOS is to build and run the iOS app. Then on the simulator open the "Watch" app, navigate to my app name and enable the Show App on Apple Watch option. This is clearly not a sustainable debug cycle. How am I able to launch both apps from Xcode without jumping through the above hoops so that I can test the connectivity between the two apps?

I am recording accelerometer data using CMSensorRecorder and then trying to retrieve the data in background refresh. However, I am getting the following error: "[Connection] Error on message reply (sync) for kCLConnectionMessageSensorRecorderGetMetasByDateRange (Connection interrupted)" Thanks in advance.