Apple watch Xcode pairing & connection issues

Hello, I have exactly the same problem, the watch does not appear in Xcode despite all possible attempts to connect it. Have you found a solution to the problem? Thank you in advance

Same issues here. What (somewhat) worked for me was to enable the personal hotspot on the iPhone that the Watch is connected to. Then connect the Mac and the Watch to that hotspot. Do not connect the iPhone via USB to the Mac. Restart Xcode and maybe have a look into "Window > Devices and Simulators".

However, copying shared cache symbols from the Watch literally takes forever and is usually stuck at 0% or 1%.

This is definitely NOT the developer experience you would expect from Apple.

I'm having the same issue. So frustrating. Watch is no where to be found. I've tried unpairing, re-pairing, and everything else I could think of.

Unable to find/set any Developer Mode on the watch.

Sorry to hear the issue, which seems to me a regression in 26.2. Do you have a feedback report yet? If not, would you mind to file one and share the report ID?

To make the feedback report more actionable, please install the CoreDevice logging profile to your Mac, iPhone, and Apple Watch, and also the sysdiagnose profile for watchOS to your Apple Watch, then follow the instructions at the latter link to capture the co-sysdiagnose, and attach it to your feedback report. Thanks!

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

I'm experiencing the same issue since iOS 26.0 and 26.1. With 26.2 I am now able to see the watch but it takes so much time to copy shared cache symbols from the watch. It times out after a few minutes, even though the watch is unlocked on my wrist, next to my laptop and iPhone, both 2 feet away from my Wifi router

watchOS 26.2.1 seems a worse pain than previous watchOS versions to copy cache over to Xcode 26.2 than before.

Put the watch, the phone, and your computer on a 2.4ghz wifi network. I tried all the other fixes, they dont work. This works.

Same issue

Thanks again for reporting the issue. It seems that the issue is impacting the community, but I haven't seen any feedback report ID posted here. Do folks have any feedback report yet? If not, would you mind to file one and share your report ID here? I understand that filing an actionable feedback report takes time, but that will help.

I am trying to capture the issue, and yet, my current configuration, Xcode 26.2 (17C52) + iPhone 17 Pro with iOS 26.3 (23D127) + Apple Watch series 10 with watchOS 26.3 (23S620), does work for me.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

Same issue here, Apple Watch not visible on Xcode. my set up is iPhone 13 with iOS 26.3, Apple watch series 2 with iOS 26.3

I Have the same issue. MacOS 26.3.1, Xcode 26.2, iOS 26.3.1 iPhone 17 Pro Max and WatchOS 26.3 Apple Watch S10.

pretty much same issue, OSX / apple watch version 26.3.

• Developer mode does not show on apple watch settings
• Apple watch does not show as available in Xcode even if paired to an iphone connected to Mac via USB-c

same issue

os: 26.3.1（25D2128）

Xcode : 26.4 beta 3 (17E5179g)

iPhone 15pro: 26.3.1 (23D8133)

Apple Watch : 26.3.

same issue here, it was working perfectly than suddenly it stopped, tried to unpair and now there is no way to recover. I have also tried to initialize the apple watch... seems like it really doesn't want to work anymore

iphone 15 pro max v 26.3.1 apple watch ultra 2 v 26.3 xcode v 26.3

Same issue for me as well and my ability to test on a real device is totally blocked and has been actually since some time back in Nov.!

• Xcode 26.3
• iOS 26.3.1
• watchOS 26.3

1. Watch was paired to Xcode but would never connect due to the same "tunneling" errors mentioned by others.

2. After unpairing via Xcode Devices and Simulators the watch cannot be repaired even though I have unpaired and repaired it with iPhone and unpaired and repaired the iPhone to Xcode. NOTHING will cause Xcode to find the watch again.

Damn it Apple this crap has been an ongoing issue since Xcode 26.0 How do you have 3 dot releases and not fix something like this?!

Might have gotten the watch re-connected via another suggestion in higher up in this thread to connect mack to iPhone via Hotspot. I can see the watch again in Devices and Organizers, but the setup is taking foreeeeeevvverrr so not sure what happen when I switch the mac back to regular wifi.

Definitely a hell of an experience in the worse way.

• Apple Watch Series 4
• iPhone 11
• Mac Neo

I had 0 issues developing/deploying to Pixel WearOS, but obstacles after obstacles, developing for and deploying to Apple WatchOS.

After several days of working around each obstacle with the help of Gemini, I'm adding the summary of what I had to do so far to get to initial deployment in case this helps Apple/others with fix/workarounds:

Here is the complete technical post-mortem for the development environment setup. This summarizes the specific hurdles cleared to get a Watch Series 4 (watchOS 10.6.2) communicating with your Mac via a No-SIM iPhone bridge.

🛠️ Environment Recovery Summary

1. The Networking Layer

The primary blocker was extreme network instability on the default 10.0.0.x gateway.

The Symptom: ping tests showed 62% packet loss and 1,000ms+ latency.

The Fix: Migrated all devices to a clean 192.168.86.x subnet.

The Result: Achieved 0% packet loss and ~13ms latency, providing the stable "pipe" required for the cryptographic DDI handshake.

1. The "Physical" Overrides (Critical Breakthroughs)

Even with a good network, the Series 4 hardware required specific environmental states to stay "Ready":

Bluetooth Disabling: You had to turn off Bluetooth on the iPhone. This forced the Watch to stop trying to tunnel through the low-bandwidth Bluetooth LE connection and instead use its internal Wi-Fi radio for a direct high-speed link to the Mac.

The "Puck" Requirement: The Watch had to be left on the magnetic charger. On the Series 4, watchOS 10 aggressively throttles the Wi-Fi chip to save battery; the charger acts as a "High Performance Mode" toggle, keeping the radio active for the 500MB+ disk image mount.

1. Security & Software Gatekeepers

Since the Watch had been recently reset, several security "flags" had to be manually toggled:

Passcode Enforcement: You set a 4-digit passcode. watchOS 10 often refuses to mount a developer partition if the "Secure Enclave" isn't active.

Developer Mode Loop: You performed a "hard refresh" of the Developer Mode toggle (Off -> Restart -> On -> Restart) to force the Watch to re-provision itself on the new subnet.

Daemon Flush: We cleared the "zombie" states on the Mac by killing remotepairingd, remoted, and flushing the CoreDevice cache in ~/Library/Developer/.

Additionally, I had to unlock 100's of times both phone and watch and keep the watch in wake state.

Oh, I ended up purchasing a Neo since the MBP 2015 was out of support and expect to spend $99/y for Apple Developer Program. Compared to one time $25 Android Development Fee and nothings else.

Also, I've been able to get Claude to build/deploy on AndroidStudio via CLI but many steps needed to be done manually on XCode.

For context, I started my Google/Apple phone/watch development journey last month at the same time and feel the need to convey the differences in developer experience between platforms.

I'm looking forward to closing the gap, Apple.

After 7 hours, successfully managed to get my first deployment on the watch. Definitely not something you expect from apple, in fact I cussed them out the whole way through. But here's what I did

Mostly followed entouss's guide and most advice is reiterated from him + some of my experiences

Before you do anything, make sure

• Apple Watch is fully charged (this WILL take a long time)
• It has a passcode

You might get the bright idea to remove the passcode and put it on charger to prevent lock. Keep it on.

Pre-pair

• Make sure you're on a 2.4 ghz network (mobile hotspot or create guest network on router)
• Connect all devices to that network
• Shutdown all devices and start them up 1 by 1 to start from a clean slate

Get it to show up in Xcode devices

If your apple watch is already in the xcode device list, DO NOT unpair it as it may not show back up again without large hassle

• WATCH for "trust this device" messages on your apple watch.
• If you accedentally press no, or press the crown while the dialog is on, you gonna have to disconnect iPhone, shutdown mac, shutdown iPhone, shutdown watch, and restart from clean slate
• Once you restarted make sure they're once again all connected to the same network
• The trust device doesn't work / is inconsistent when you don't have a password (maybe I did it wrong idk)
• If still nothing shows up in xcode, you can view logs with "log show --predicate 'process == "remotepairingd" OR process == "remoted""
• You can also kill it by "sudo pkill -9 remotepairingd"

Credits to Bar0kul on reddit under this post: "I think I found a reliable way to sync Apple Watch to XCode in development mode for debugging and logging" for the log command

ACTUALLY Connecting to Watch

Oh now it shows up? Hooray! You're not even close to deploying yo shit. Thanks apple!!!

• Now it shows, make sure NOT to un-pair your device
• At this point just hope the watch connects ngl
• Best you can do is re-verify all devices are on the same network, iPhone cable connected to mac, iPhone wifi and bluetooth all on
• If you have multiple phones use the "main" phone not the secondary phone
• watch is ON throughout the connecting process
• Now just keep trying till it connects

Sync Cache Symbols

• At first, it will get stuck on 0% or 4% for a long time, just let it do its thing.
• It will use a LOT of battery, up to 50% (for my series 6 at least)
• It takes up to 2 hours.
• Keep the watch on your wrist. You can let it sleep while its on your wrist as it'll remain unlocked
• If your watch is on charger, you'll need to keep it awake somehow. I found the best way is to open the camera app on the watch to mirror iPhone camera which keeps it on until the phone has slept or when the watch reaches 5%
• Its much more convenient to charge to 100% and leave on wrist than charger method
• Make sure Mac is also open the whole time

Hope this helps someone!

Although I understand the motivation to keep the watch small and seal gaps, sometimes a physical cable and data interface is the best way to go. Though we know apple will never go for it, so I urge for them to at least give us more logging. We're all developers here, not end users. If you're going to leave us with such a volatile interface, let us at least have a bit more insight into how to handle our issues.

You can also kill it by "sudo pkill -9 remotepairingd"

If you encounter an instance where you actually find this necessary, please file a Feedback Assistant Report which includes a devicectl diagnose (and separate mac / phone / watch sysdiagnoses if they're not all collected by it).

There are no known issues for which this step should be necessary, so if there are issues, we want to know about them.

make sure NOT to un-pair your device

If you un-pair or you accidentally tap the button to not trust, the only way to get the prompt to appear again is by physically re-connecting the phone.

watch is ON throughout the connecting process

Yes, and it needs to remain unlocked throughout the DDI mounting process as well. If the device locks before the DDI mounting completes, you will need to re-attempt mounting the DDI.

--Jeremy jeremyhu at apple dot com

Let's just pile on here. Same issue. Unbearably bad and a productivity killer. Up to date OS on all devices. Spend half my day waiting for Xcode to reconnect to my watch that it was already connected to.