iOS: Watch Kit paired device unavailable for development

I can't run my Apple Watch application in XCode. My phone+watch is listed as a "Unavailable Device" and says "paired device unavailable for development". When I try to launch the app it says the same thing.

How can I resolve this?

I'm using XCode 7.1, iOS 9.0, WatchOS 2.0.1.

This is what worked for me, and it is a lot easier and faster than un-pairing so I would try this first. From the Clock Face Swipe up, and click on the Ping iPhone button. After it makes a sound, go back in Xcode it should change no longer be unpaired or unavailable for development.

I had the same issue on iOS 9.1 + WatchOS 2.01 that XCode 7.1 kept saying "paired device not available for development". Here is what I did to solve it finally, not quite sure which step is critical -

1. Unpair my watch
2. Reboot both iPhone and apple watch
3. Pair them again, and setup my watch as a new one
4. Plug (unplug first) iPhone to Mac
5. On apple watch, say Trust the computer when it asks
6. Unplug and plug again

Bang! My apple watch is well recognized for development. Hope it helps.

I can confirm having this too by using the following configuration: OS X, Xcode7.2 beta, iPhone5s with iOS9.2 and WatchOS 2.1

I unplugged the iphone again, closed and restarted Xcode and plugged in the iPhone again - than it worked fine!

Rebooting the Apple Watch worked for me, after that it displays the 'trust this computer' message which is required to debug the watch with XCODE.

I just restart the Xcode to solve the problem.

Deleting the 'famous' XCODE Derived Data folder did it for me.

Steps for newbies:

1. Close XCODE.
2. Delete the Derived Data folder, to find it's location go in XCODE to upper menu: XCODE -> Preferences -> Locations: Here click on the Derived Data arrow.
3. Reopen XCODE.

Tested on XCODE8.0.

Go to Window--> Device and Simulator , Unpair device and Disconnect from cable and connect back works for me.

It just happened to me and I fixed it by

1. quitting Xcode
2. putting the Watch on the charger
3. open Xcode
4. select the Watch App Target
5. select the iPhone paired to watch as the device to run
6. Wait until '(paired device unavailable for development)' or '(no paired Apple Watch)' disappears from device description at the Xcode toolbar
7. Run!

I followed the steps above repeatedly and still got the same issue. What I found fixed the issue was not signing into iCloud and only using Messages instead. Once I did that it worked beautifully. Thank you.

Deleting everything in ~/Library/Developer/Xcode/watchOS DeviceSupport/ worked for me.

I had the same issue with watchOS 2.1. Unplugging my phone restarting Xcode and plugin in my phone did the trick. I suggest trying that before you re-pairing phone and watch

I had issues with this too, using Xcode Beta 7.3 version 3. I updated to Xcode Beta 7.3 version 5 and it's working fine. Hope this helps!

I met this problem as well.

What I do is quite simple, turn off bluetooth from iPhone and turn on, wait till apple watch got connected again.

Then fire up the app.

I had to unlock the watch with my passcode.

• If already unlocked, lock it then unlock.

I had issues with this too with Xcode 10.1 and Watch OS 5.x Really need delete Xcode Derived data files, and reboot Watch, and click 'Trust' button in Watch for debug.

my problem was having to authorize the computer from the Apple Watch... (with last release Xcode 10.2)

For me the only thing that worked was unpairing the watch from the iPhone and setting it up as a new watch (restore from backp didn't work).

I tried unpairing in Xcode, deleting derived/cached data, platform support, restarting Xcode, all combinations of unplugging and restarting! Nothing worked.

Whether it was this nuclear action, or the simple fact that it then goes through the re-authorisation process between the Mac + Watch, we'll never know.

What I do know is that at times Xcode can be shockingly unstable.

This happened to me over the last few days. Xcode was being extremely unstable (sometimes, in the Build Scheme, it would say "paired watch unavailable for development", other times it would say "null" when referring to the watch, other times it would work!). I did all of the steps below, but the inconsistency was not solved:

Unpair my watch, Reboot both iPhone and apple watch, Pair them again, and setup my watch as a new one, Plug (unplug first) iPhone to Mac, On apple watch, say Trust the computer when it asks, Unplug and plug again

Eventually, the I realised a slightly newer version of Mojave (10.14.5), and a slightly newer version of iOS (12.3.1) had been released. After I made these quick updates, XCode appears to be much more stable now.

I updated my phone to iOS9.1 and it's working now.

In my case I disable the passcode of apple watch, then DerivedData and restart Xcode solves the issue.

I got rid of the message after re-pairing which took about 30+ mins.

However, it could have been that restarting the watch would have fixed it so try that.

Also try deleting the DerviedData.

After I got the message to go away, the app wouldn't install on the phone. I had previously created a WatchKit project from an AppCode template. After creating a new project from XCode, it started to work.

For me, I had to Trust this Mac from my Watch.

Then I cleared the derived data, restarted XCode and it worked. Didn't have to restart phone or Watch.

Today I had the same issue. My phone was availbale for development but the watch was unavailable. I restarted the iphone, watch and mac. After the restart of all devices I got the notification on the watch to trust the mac and I was able to start my application on the watch and iphone.