Apple watch Xcode pairing & connection issues

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.