Hi folks. Sorry you're having this issue, but to date I don't think I've seen any reports come in with the data that Myke mentioned above.
With the transition to CoreDevice last year, we saw significant improvement in watch development, especially with S6+. S3-5 are a bit more challenging due to some difficult hardware constraints, but even those should be much better than things were when we were hopping through the phone with the previous device stack.
This particular error message is a bit confusing and needs to be cleared up, but essentially we are likely continually loosing connection with the device while trying to prepare it (mount the DDI on it).
There are a few known issues on all platforms regarding device prep (DDI mounting), but watch is indeed the most problematic. We WANT to fix these issues and will engage with anyone that is willing to provide us with data to diagnose such problems.
The most important thing here is to ensure we have a high quality network connection for both watch and host. Enwure bonjour traffic isn't blocked (which is common in corporate networks). Don't cheap out on low quality networking gear!
The best triage steps here are to drop below Xcode and run xcrun devicectl device info ddiSeevices --verbose --device <ID> and surface up that full error and timestamp with your bug report.
Please include the FB number here and include a link to this reddit post in the feedback report, so we can connect the two together (and ensure your report gets routed to me).
Regarding bugs with Apple products:
-
Don't assume that Apple engineers know about an issue just because you complained about it in forums or reddit or whatever. Bugs that are filed with Feedback Assistant generally get to an engineer within a business day. Comments in forums don't.
-
Don't assume that just because someone else filed a bug report that you don't have to. The vast majority of feedback reports that I see (I'd estimate 98% or more) are not actionable and almost all of them don't get a response back from the reporter when requesting more information. If you are serious about getting a bug fixed, then please take action and file that report because your investment in working with us is what will help us understand the issue and get it resolved.
-
If you are serious about engaging with us and not just submitting a "+1", then be sure you:
a. Change the title away from the default. This makes your radar stand out as likely containing more than just click-through data.
b. Provide solid repro steps (what hardware is involved, network config, versions, steps, etc).
c. Provide ample logging. In the case of any device connectivity issue, please provide diagnostic logging by running xcrun devicectl diagnose after reproducing (ideally with our logging profile installed per https://developer.apple.com/bug-reporting/profiles-and-logs/?name=CoreDevice). Please ensure that the resulting devicectl diagnose contains sysdiagnose from the host and relevant devices. If it does not, please collect those manually and include them as well.
Hope that helps!
--Jeremy
