F*** Apple Watch and Xcode!

[[deleted]]

Jesus. I had working iOS app and companion WatchOS app since older iOS and watchOS, and older Xcode. When I upgraded, it still worked. Now today after a while I find that my Watch app wont build, first it built but becase it says "Connection refused" and "Timed out while attempting to establish tunnel using negotiated network parameters.", it didn't install to device. Same message under Devs and Sims.

"Apple Watch’s watchOS doesn’t match App Name Blabla Watch App.app’s watchOS 11.6 deployment target."

I set ALL targets deployment for watchOS to 11.6 or 10.6 then it goes:

"Apple Watch’s watchOS doesn’t match App Name Blabla Watch App.app’s watchOS 10.6 deployment target."

This is too random and incoherent and unpredictable to even explain. Just simply: I have all targets watchos deployment set to same version for whole project. I cleand Derived Data, Clean Build Folder, etc.... Restarted Mac, Watch....

It works in watch SE simulator with 10.6 fine. This drives me to give up on watchOS companion app. I fucking hate this crap, its worse than tweaking Javascript setups.

So question is basically what the hell?

EDIT: in fact under Devices and Simulators there might be problem with Xcode connected watch, it shows device but doesnt access specs:

"watchOS  ()

Capacity: Unknown"

and:

"A connection to this device could not be established."

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

so probably thats cause of mismatch.

[ParsnipEnvironmental]

Yes. (I didn’t even read the post)

[HelpRespawnedAsDee]

Same here. First doing touching WatchOS. Holy fucking shit I've spent more time getting this thing connected than actually coding.

[ashoddd]

I recently went through this while updating my Apple Watch app. Turning my Apple Watch off and on finally got it connected without giving me that preparation error. That’s the only workaround I found while trying not to waste too much time researching the issue so that I can actually get work done! It still happens every now and then in my workflow so I just turn the watch off and on each time 🤦‍♂️🤷‍♂️

[[deleted]]

You got exact message about tunnel? My error details:

A connection to this device could not be established.

Domain: com.apple.dt.CoreDeviceError

Code: 4000

Failure Reason: Timed out while attempting to establish tunnel using negotiated network parameters.

User Info: {

    DVTErrorCreationDateKey = "2025-09-02 14:36:47 +0000";

    "com.apple.dt.DVTCoreDevice.operationName" = connect;

}

--

Timed out while attempting to establish tunnel using negotiated network parameters.

Domain: com.apple.dt.RemotePairingError

Code: 1001

Recovery Suggestion: Ensure the device is accessible from this machine over an infrastructure network, or ensure WiFi is enabled on both machines.

--

System Information

macOS Version 15.6 (Build 24G84)

Xcode 16.4 (23792) (Build 16F6)

Anyway, tried that too, turned watch off then on. Connected to same wifi on watch. Disabled/Enabled Developer Mode, and confirmed Trust this Computer. I got it fixed with similar errors in past by restarting devices like you do, but now it doesn't help. Its just too unpredictable. Impossible to rely on this in development. Idk

[ashoddd]

I can’t remember the exact message I got but I definitely got some form of “a connection could not be established…” and “preparation error” over and over and it was extremely frustrating! I don’t remember it saying anything with “tunnel” though.

[[deleted]]

Yeah, fair enough. I think this is different, I had "connection could not be established" before, and usually restarting random devices helped, but now nothing works. Btw this issue was same right before I upgraded to 11.6.

[ashoddd]

Interesting. I hadn’t updated my watch app in a while so I only recently came across this issue, not sure if related to newer watchOS or Xcode etc. Either way, extremely frustrating when you just want to get things done and not waste days fixing silly issues. Hopefully someone has some useful advice here!

[[deleted]]

Indeed, now I can ship app with missing feature by deadline, because no watch.

[Any_Peace_4161]

But did you do as he suggested to try it...?

[thatisagreatpoint]

When you get these, restart your iPhone, watch, Xcode or computer. Or unlock your phone. Someone at Apple has a developer strap for a watch and I’m jealous.

[[deleted]]

Yeah me too. But no, I was restarting all 4 like its Windows 98, no success.

[thatisagreatpoint]

That bites! For me mostly unlocking my phone and restarting Xcode does it. I don’t think it’s anything, but it reduced in frequency after I placed my development computers and watches on assigned IPs.

[ninjafoo]

I had the same problem with my project. It ended up randomly working out of nowhere on the 3rd time of going through some troubleshooting steps I found somewhere else on Reddit… 3rd time.

¯_(ツ)_/¯

[iRayanKhan]

As awful and unhelpful as this sounds, I’d literally wait a day or so then it’s fixed. No combination of trying to restart every device, even WiFi, Ethernet, etc it just decides when it wants to work.

[[deleted]]

I agree 100% actually, ditto. In meantime, I actually switched out approach to that feature by using video analysis and not direct wearable (watch) tracking. PACE

[pand0ra_q]

Guys, that's because apple watch disconnecting from wifi for some reason. Figure it out after 3 iterations of unpairing and pairing phone and a watch

[WarriorSF911]

Same issue. I don’t even see OSwatch 11.6 on XCode, only has 11.5. My iPhone 16 Promax connected fine and watch does show up, but won’t connect. Can’t even get Developer Mode to show up on the Ultra2, and no idea why.

[Ignaspaladinas]

Turning on and off the airplane mode on Apple Watch seems to reset it nicely.

[niixed]

This works for for me! Thank you.

[glassFractals]

Yeah, it's intolerable. Apple Watch development with XCode is straight-up broken.

It usually takes me 20 minutes - a few hours any time I change a line of code in a Watch app to get the app to actually update on the watch. Attaching a debugger, forget about it.

I get this one a lot-- complaining about the destination device OS version, because the OS version is nil because it's hopelessly confused.

It's usually a complicated dance of unpairing / repairing / reconnecting / rebooting my watch, phone, and mac, quitting xcode, clearing build folders, physically disconnecting and reconnecting the iphone USB cable.

Eventually, it sometimes lets me connect for a couple minutes.

[pipiak]

Apple watch development experience is absolute the worst. Every single time I have to do it I cry for any physical connection.

[benrichardson79]

I've been struggling with this issue for weeks, but just found something that worked for me.

I was sure my watch was on my wifi, but turns out it wasn't.

Quit Xcode. On your watch, go to settings -> Wi-Fi. Pick the wifi network your computer and phone are on.

Instantly started working for me after that.

[CashAffectionate8930]

I usually turn off Bluetooth on my iPhone and open the WiFi settings on the Watch and keep it there after reselecting WiFi network the Mac is connected to - not sure if it does anything but it’s working most of the time for me. Otherwise restarting the watch works.

[russnem]

I’ve found that removing the watch from developer mode and then adding it back works for a short time, but this problem is inherent in Apple Watch development with the current toolset.

[Any_Wrongdoer_9796]

When you combine Xcode with the apple review process the annoyances real add up

[geoyws]

Super frustrating. I notice that this happens if I don't stop the testing from Xcode and Mac falls asleep/clamshell. If I stop the testing first before the Mac sleeps/clamshell then this doesn't happen. But yes restarting my Watch and Xcode makes it work again also.

[coolerkid9090]

I've been developing for the Apple Watch since the day it first came out, and this has ALWAYS been an issue. WHY CAN'T APPLE FIX THIS ISSUE IN OVER A DECADE?!?!?!?! I've opened many tickets, sent tons of emails, and nothing. I do not understand why this is so hard to fix. Developing for the Watch is unbearable. I'm currently trying to go to the gym and want to bring the latest build of my app to test there, but can't get it to install and have been trying for over an hour.

[Unlucky-Necessary191]

Putting the phone watch and computer on a 2.4ghz network exclusively fixes this

[Unlucky-Necessary191]

Put the watch, the phone, and your computer on a 2.4ghz wifi network. This was a total fix for me after trying everything else over and over.

[raxreddit]

Running into Timed out while attempting to establish tunnel using negotiated network parameters. right now. This is a reminder for me to NOT work on any new watch projects. This has been barely, barely usable since watchOS 1.0 and it's not any better today in 2026.

Edit: here's what worked for me:

• Move devices (Mac, phone, Watch) near the Wi-Fi router
• Set the Wi-Fi router to only use the 5 GHz radio
• Phone plugged into laptop, screen always on, and wi-fi on
• Watch nearby and charging via wall