Posts

Post not yet marked as solved
19 Replies
I have the same issue. Cannot even see the watch listed when I use xcrun devicectl list devices in the Terminal. Tried unpairing the Watch from my iPhone and pairing it again, cleaning out all sorts of caches, turning on and off developer mode. watchOS 10.4, Xcode 15.3 (15.2 doesn't work either).
Post not yet marked as solved
20 Replies
Same issue. Xcode 15.3 (tried downloading 15.2 as well, no luck). watchOS 10.4. Here's how I got into this state: Xcode would never be able to build to my watch, so I figured I'd try and unpair the Watch from the devices list in Xcode and then pair it again. Should probably never have done that, because even after unpairing the Watch from my iPhone and resetting it, turning on and off developer mode, cleaning out all sorts of caches... I've tried everything and it never shows up anywhere. It's not even listed when using xcrun devicectl list devices. It's now taken about 24 hours of dev time away from me, which is unacceptable for something this basic.
Post marked as solved
17 Replies
Since I'm still experiencing the same issue in Xcode 15.1, I've now also submitted feedback for this issue (FB13467714). It's quite ridiculous this hasn't been fixed yet.
Post marked as solved
17 Replies
I have the same issue using the latest Xcode 15.0.1 (15A507). Previews stop working if any dependency imported using the Swift Package Manager doesn't support watchOS, even if those frameworks (in my case Datadog and Lottie) are not directly linked or used in the watchOS target.
Post not yet marked as solved
4 Replies
How are you initiating your ink annotations? More specifically, what bounds do you assign to them? I had the same problem when I initially initiated each ink annotation with the bounds of the PDF page (which I at the time thought was the correct approach), only to later discover that initiating each annotation with the bounds of the bezier path that represents the drawing fixed the memory issue.