Apple Watch cannot reconnect

What do you see as the state of the device in output of xcrun devicectl list devices? What is the output of xcrun devicectl device info ddiServices --device <identifier> --verbose? Can you collect an xcrun devicectl diagnose while this is happening and include it in a bug report?

Done! FB12845184

It's not working for me either - exact same message in Xcode 15 Beta 6. I see this:

xcrun devicectl list devices
xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find devicectl 2> /dev/null' failed with exit code 17664: (null) (errno=Invalid argument)
xcrun: error: unable to find utility "devicectl", not a developer tool or in PATH

Getting:

/Applications/Xcode-beta.app/Contents/Developer/usr/bin/devicectl device info ddiServices --device UUID_HERE --verbose
Using verbose logging.
ERROR: The operation couldn’t be completed. Operation timed out (NSPOSIXErrorDomain error 60.)

I've tried everything as well - not connecting with Apple Watch Series 5, watchOS 10 (21R5295g) and Xcode 15 beta 6. Either says "Connecting ..." or "Waiting..." and keeps switching between the two. Unable to test the app.

Submitted report: FB12925643

I have been experiencing the same issue in the latest betas without any luck trying everything I can think of, has anyone found a solution? I have also filed a report about the issue: FB13022879

Seeing the same issue with Xcode 15 Beta 7 even though it says watchOS connectivity has been resolved. see "Waiting to reconnect to Apple Watch Series 5" and then a "Connecting to Apple Watch Series 5" message and it keeps switching between the two

Xcode 15 beta 7 here (still not working). The terminal this time however claims it's paired:

Apple Watch Series 5 *** XXXXXX-EA2A-4FB3-XXXXX-XXXXXXX available (paired) Watch5,2 iPhone 14 Pro Max *** XXXXXXX-0012-XXXXXXX connected (no DDI) iPhone 14 Pro Max (iPhone15,3)

And:

devicectl device info ddiServices --device XXXXXX-EA2A-4FB3-XXXXX-XXXXXXX --verbose

Using verbose logging. ERROR: The operation couldn’t be completed. Operation timed out (NSPOSIXErrorDomain error 60.)

Seeing the same issue with Xcode 15 Beta 7 even though it says watchOS connectivity has been resolved.

It says Waiting to reconnect to Apple Watch van Mark, Xcode will continue when the operation completes. (See image)

I tried:

• Completly erasing the Apple Watch
• Update iPhone to the latest Public Beta version
• Update Apple Watch to latest Public Beta version
• Repair the Apple Watch with the iPhone
• Connecting the iPhone with a cable

Nothing helped.

Xcode 15 Beta 8 the issue has not been resolved.

• Updated iPhone en Watch to the latest developer version
• Unpaired the Watch and then pair it again
• Turned Wifi off on the Mac, Turned it back on
• Opened the Watch app on the iPhone
• Turned airplane mode on all and back on
• Deleted everything in the cache (~/Library/Developer/Xcode)

Nothing works.

For me it works after I ensure that watch, phone and laptop are connected to the same WiFi network. Also once it helped to plug USB cable from phone to different port of laptop.

Just installed Sonoma and I'm having this issue now as well, no idea how to fix it.

Certainly! Here's an improved version of your forum response:

In Xcode Beta 8, I encountered the same problem. Here's how I resolved it:

1. Navigate to Manage Run Destinations.
2. Remove the watch from the list.
3. Set everything up from the beginning.
4. Connect the phone using a USB cable.
5. Add the watch back to the list.

This approach worked for me and resolved the issue. I hope it helps!

I have the same issue. When the Apple Watch tries to reconnect, I noticed that an error message flashes, which I was able to capture through screen recording.

Hi, Bruno! I had the same situation at start as you: no serial number, no watchOS number.

Then I turned on wifi on watches, so all my devices (macbook, iPhone and watch) were in the same network. after that all these numbers appeared, but still no connection, "trying to connect..."

Then I unpaired iPhone and watch from the "Manage Run Destination" menu, and started all over.

First connected my iPhone through a cable to MacBook (developer mode is on) - no problem. But now on the watches appeared the same menu under privacy settings developer mode - and it was - off. Then Xcode said fetching debug symbols... all that stuff. and it works eventually

I wish you luck, I was banging my head a long time

Here's what worked for me:

Conditions

• Xcode 15.0;
• iPhone already available as a Run Destination;
• Watch is shown in the list, but no information about it is displayed, status switched between "Connecting" and "Waiting to reconnect";
• watchOS 10.0.1;
• Shared WiFi network.

Steps

1. In Xcode, open Window > Devices and Simulators;

2. Connect iPhone with a cable (not sure if this step is required);

• At this stage, watch is in the "Devices" list, no information about it is displayed, status of the watch switches between "Connecting" and "Waiting to reconnect".

1. On the watch, go to Settings > WiFi, make sure WiFi is on and select the WiFi network;

• At this stage, Xcode clearly connected to the watch and the note under the status changed to "Enable developer mode".

1. On the watch, go to Settings > Privacy & Security > Developer mode (at the very bottom of the list);

• Watch restarted, asked to trust the Mac again, all permissions were given.

Xcode attempted to reconnect and, after a short while, connected to the watch successfully and started the pairing process. The whole procedure took a few minutes and now the watch is available as a Run Destination.

p.s. Xcode statuses are "rough approximations" from memory, all steps might not be necessary.

i did every possible thing, nothing helps

I followed the steps many others have posted but have had no luck...stuck in a waiting to reconnect connecting loop

hopefully Apple has a fix for this soon

I got it working by connecting my laptop, phone, and watch all to the same wifi network where devices could see each other. The problem was that all the devices were on a school network where the devices couldn't see each other. I created my own wifi network using my windows pc hotspot feature, which then used the school network under-the-hood, but allowed the devices to see each other since there was lower security rules in place.

In an earlier Xcode version, connecting to the school network with all devices still worked for Apple Watch to be available. It seems like connecting through the iPhone then going to the watch for testing the app is no longer working...The app now goes directly to the watch over the network.

After spending weeks trying to connect my Apple Watch Series 5 to Xcode, I suddenly discovered that all watches before the Series 5 (including the Series 5) can only connect to 2.4G Wi-Fi. My iPhone and Mac are connected to 5G Wi-Fi. So when I tried connecting my iPhone and Mac to the 2.4G Wi-Fi, the watch connected instantly.

But that's weird, There are a few times that I still using 5G Wi-Fi for iPhone and Mac, but I can still connect to my series 5. There might be some bug here for connecting watch on different Wi-Fi but actually the SAME LAN.

@jeremyhu, what is devicectl?

I had the same problem with "Waiting to reconnect to Apple Watch" because I used Personal Hotspot. I got to go to cafe to join WiFi there and the issue was resolved. iPhone, mac and watch want to be in the same WiFi network and Personal Hotspot was always the issue, starting from very first versions of watchOS.

XCode 15.2 beta and WatchOS 10.2 - Any fix to this real problem? Was able to connect few days ago and since no luck. Yup, unpaired then paired. Reloaded. Rebooted.

This is a workaround that won't work if you only have one Mac... In my case, I happen to have a Macbook Pro and a mac mini, and the problem did not occur on the Macbook Pro, so I copied watchOS DeviceSupport (latest is Watch6,6 10.2 (21S364)) to the mac mini, and the symptom was fixed. For some reason the download of watchOS DeviceSupport (about 2GB) appears to stop completing.