Apple watch Xcode pairing & connection issues

Developer Tools & Services Xcode
PickNick OP
Created
Replies 28
Boosts 16
Views 5.9k
Participants 30

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators.

Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app.

Issue A (when Watch is visible in Xcode)

In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect.

Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.”

In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation.

Issue B (after unpairing Watch in Xcode only)

I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone.

Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination).

What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM)

Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report?

If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend.

Thank you in advance,

Replies  28
Boosts 16
Views  5.9k
Participants  30
CarreraGT OP

Update / solution for watchOS 27: the Watch no longer pairs through the iPhone, you have to start pairing from the Watch itself.

Step 1: On the Watch, go to Settings > Privacy & Security > Developer Mode > "Pair with [your Mac's name]".

Step 2: Xcode Device Hub shows a 6-digit code. Enter it on the Watch.

Step 3: The Watch shows up in Device Hub right away and can be used as a run destination (first run copies symbols, which takes a few minutes; keep the Watch unlocked and on the charger).

Until you do step 1, the Watch doesn't advertise itself at all, which is why it never appears in Xcode or "Pair Nearby Device". Added this to FB25364030 too.
(Watch Ultra 2, watchOS 27.2, Xcode 27.1, macOS 27.2.)
cenriqueortiz OP

Issue resolved!

Unpair. Then:

  1. Leave Device Hub open at + → Pair Nearby Device → Apple Watch.
  2. On the Watch, open Settings → Privacy & Security → Developer Mode.
  3. Look for Pair with [your Mac’s name], possibly under Devices. Select your Mac and initiate pairing.
  4. The reported sequence displays a six-digit code on the Mac. Enter that code on the Watch.
  5. Keep the Watch unlocked through device preparation.
SpaceMan OP

I'm having connectivity issues as well with iOS 27.2 and watchOS 27.2. Never had this before. My app runs on the watch, but no data is transfered over to it from the iPhone.