435

When I tried to build and run, Xcode said my device was locked. I looked at my iPhone, and it's not locked at all. How do I fix this?

18
  • 5
    lock it and unlock it again
    – ChrisH
    Nov 6, 2014 at 23:50
  • 6
    tried it, still no luck Nov 6, 2014 at 23:59
  • 80
    For me, unplugging and re-plugging did the trick. No need to Clean Build Folder, restart Mac with Command+Option+P+R, leave the house and come back again, burn a Voodoo doll of Steve Jobs, etc. Sep 16, 2016 at 3:22
  • 13
    I solved this issue with disabling hotspot
    – levye
    Jan 28, 2017 at 10:20
  • 21
    @NicolasMiari For me it has not worked and I am looking for the Voodoo doll
    – zirinisp
    Dec 20, 2017 at 12:23

42 Answers 42

562

My phone was set to "trust" the Mac, and I still ran into this error with Xcode 6.1.1.

This worked for me:

  • unplug device
  • quit xcode
  • open xcode
  • plug in device
  • build/run
8
  • 116
    Unfortunately this is too often the solution for many of your weird Xcode woes.
    – Jarsen
    Dec 20, 2015 at 3:58
  • 6
    November 2019 and Xcode still has this problem! It hit me this morning. unplug device, quit Xcode, (go get more coffee), open Xcode, plug in, big time sink but seems to work. My other "favorite" is Xcode sees the device then doesn't see the device. Nov 20, 2019 at 19:17
  • 1
    XCode 10.1 and still had to do this to get it to deploy to device. Some things never change. Feb 11, 2020 at 22:30
  • 2
    as of the latest Xcode 11.4.1... this is till the answer
    – rickrvo
    May 11, 2020 at 2:49
  • 2
    If this does not work, just turn off and turn on the device again. It worked for me in Xcode 12 and Ipad with Ios 14 Jan 22, 2021 at 22:01
154

Did you by chance not "trust" the device? This will prevent it from communicating with xcode even if the device is unlocked.

Update here's a support doc from Apple: http://support.apple.com/en-us/HT5868

9
  • 2
    I'm not sure what you mean by "trust"...how do i enable that? Nov 6, 2014 at 23:59
  • 97
    Unplug the device, close xcode, and then open xcode and plugin the device. When you plug it in (after unlocking it) it you should be prompted to "trust" the computer (in the iOS device). My guess is you may have accidentally tapped "do not trust" and so the device will refuse to connect to the computer. Nov 7, 2014 at 0:01
  • 1
    I've updated the answer with a link to apple support page regarding the issue. Nov 7, 2014 at 0:02
  • 1
    @NicolasMiari I've had other notifications show up at the same time I plug in my phone causing it disappear, or accidentally dismissing the prompt on my Mac... as well, if you've used mobile configurator there is a chance it's causing some weird issues as the device could be configured to only respond to one machine. Perhaps that handshake got messed up the first time you plugged it in? Jun 7, 2018 at 21:13
  • 3
    Ah ... another one of those "jiggle the switch" solutions.
    – Zmart
    Sep 19, 2018 at 16:09
122

I recently ran into this issue with XCode 8 just after updating my device from iOS 9 to 10. The exact error I received was:Development cannot be enabled while your device is locked. Please unlock your device and reattach. I received this error even when my phone was unlocked, and after unplugging and re-plugging in the device.

As is mentioned in several answers, the device is locked message is actually referring to the device not trusting the MacBook. In my case, I think my phone defaulted to not trusting my computer after updating to iOS 10. Here are the steps that worked for me to reset the settings (this is the same process that is mentioned in the Apple support page in tehprofessors' answer):

  1. Disconnect your device from your MacBook and close Xcode.
  2. On your device go to Settings > General > Reset, then tap Reset Location & Privacy
  3. Plug your device back into your computer, and on the device you will be prompted to trust the computer. Tap trust.
  4. Now reopen Xcode and rebuild the project.
  5. The device locked error should disappear.
8
  • yep unfortunately only this worked for me on from Xcode 8 on iOS 10 :( Oct 25, 2016 at 3:41
  • @BishalGhimire Yeah, it's definitely not ideal. I actually just had to do this reset again as XCode started giving me the device is locked message again without any noticeable changes to any of my iPhone's settings or XCode's settings. Somewhere along the way my trust settings for my computer are being reset, but I'm not sure when and where. Oct 25, 2016 at 19:16
  • 3
    you should wait for a while to processing symbol files Nov 20, 2016 at 7:22
  • Hmm... this fixed the "Device Locked" error ... but has replaced it with a "Could not save the pairing record." error ...
    – kris
    Dec 20, 2016 at 4:22
  • 2
    this worked for me after iOS 11 software update on device / Xcode 9
    – Ben
    Oct 18, 2017 at 10:22
88

From the Window Menu in top bar of Xcode, select Devices and Simulators.

(or Press SHIFT + COMMAND + 2)

Then select your device, right click and select Unpair.
Once you do this Trust or Don't trust will appear on your device.
Trust the device again and it will begin preparing it for Development.
Wait for Xcode to pair device for development and then you are good to go!

4
  • The problem usually is not waiting for xcode to prepare iPhone to debug :) this worked Apr 24, 2018 at 4:02
  • detailed instructions for unpair can be found in forums.developer.apple.com/thread/52048
    – Atara
    May 15, 2019 at 13:36
  • I'm having this problem in Xcode 11 beta and iOS 13 beta, and this worked to solve the issue of "Passcode Required" Xcode prompt when enabling wireless debugging. Thank you! :)
    – KarenAnne
    Sep 4, 2019 at 3:55
  • This solution worked for me after I have tried to enable wireless. The rest of the answers did not help. Sep 18, 2020 at 6:45
47

I ran in to the same issue even though i selected "Trust this computer" option first time.

This worked for me

  1. Lock the device
  2. Remove cable from device.
  3. Unlock the device
  4. Connect again to Mac
2
  • 4
    Abhi Beckert's answer above worked for me before, this worked for me now. I spend a ridiculously large amount of my time tap-dancing around Apple's inept developers.
    – amergin
    Jun 16, 2017 at 9:44
  • thats aApple for you! changing some value in IB's attribute inspector will make your xcode faster. lol.
    – Itzdsp
    Jun 16, 2017 at 15:59
43

2018

The fastest way for now i found is:

1) Go to Window -> devices (changed the hotkey in xcode to CMD+P for me)
2) Press unpair on the device. enter image description here
3) Press trust in iPhone.
4) Build again or Run without building (Ctrl+CMD+R)

1
  • 1
    It works. And now I know Cmd + Ctrl + R to run without build Sep 17, 2019 at 6:46
25

I have a very simple solution which worked for me instantly. Takes some 10 sec to do:

1) Go to Window -> Devices & Simulators and untick Show as run destination

enter image description here

2) Unplug the cable and plug it back in.

3) Run the project.

This should be solving your problem!

5
  • 1
    Thanks, this worked for me with XCode 10.2 when the other advice didn't. May be related to having previously ticked to be available over network then being on a rather slow wifi.
    – Andy Dent
    Oct 1, 2019 at 5:30
  • Thanks. This worked for me. Xcode 11.3. Funny because unplugging the cable and plugging it back in didn't work, when I didnt open Devices & Simulators window.
    – Lazy Ninja
    Jan 23, 2020 at 5:51
  • Um, that seems to just make it not be available to select as the destination. What am I missing?
    – Dronz
    Feb 13, 2020 at 5:57
  • Most probably you forgot to follow the 2nd step: 2) Unplug the cable and plug it back in. Run the project.
    – Starsky
    Feb 13, 2020 at 8:03
  • Not working for Xcode 13.4.1 on MacBook Monterey
    – us_david
    Aug 31, 2022 at 21:01
24

Rebooted my iPhone, and that fixed it for me.

I tried every answer on this page (7 at the time, though 2 are duplicates) and they were all unsuccessful for getting rid of this Xcode error for me.

6
  • This saved my day! Thank you!
    – Fangming
    Oct 19, 2017 at 1:05
  • 1
    This is the best answer which save my lot of time. Thanks
    – Gaurav
    Nov 14, 2017 at 11:26
  • 1
    Didn't helped for me. Only setting untrusted and trust again helped.
    – Nike Kov
    Feb 17, 2018 at 10:48
  • You don't need to reboot or restart every time..check my answer: stackoverflow.com/a/50023756/9623144
    – Amber K
    Jun 20, 2018 at 3:43
  • It's a waste of time to reboot the phone every time.
    – Nike Kov
    Jul 27, 2018 at 10:01
21

For anyone who need a logical answer..

  1. Go to Window -> Devices & Simulators. Right click on your device & unpair it.
  2. Disconnect from cable & reconnect.
  3. Wait for it & let Xcode detect you device.
  4. Run the project.
  5. Make sure you TRUST on your iOS device and enter any passcode.
1
  • This worked. Make sure your device is UNLOCKED when you initially pair it. If not then follow these instructions to repair.
    – Wizkid
    May 14, 2018 at 15:29
12

For those who has this issue in Xcode 9: Simply restarting Xcode should solve the problem.

1
  • 3
    This is correct and especially true in the case of wifi debugging in Xcode 9. Nov 12, 2017 at 0:02
12

This happens at times while using Xcode 9.

Screenshot

There are multiple solution to this as mentioned below :

Note : Make sure that your device is not locked when Xcode is trying to install app.

Solution 1 :

i. Disconnect device and connect again

Solution 2 :

i. Restart you device

Solution 3 :

i. Disconnect device

ii. Quit Xcode (Shortcut key : cmd + Q)

iii. Open your project

iv. Clean project (Shortcut key : cmd + shift + K)

v. Now connect device

vi. Run your project

For me Solution 3 worked perfectly

1
  • Tried just about everything in the book. Restarting my phone was the only thing that worked in the end. Thanks for posting that idea here! Oct 22, 2020 at 15:04
11

There is a simple way to resolve that. At least it works for me. In your iPhone Device Go to Setting > Developer > click in “Clear Trusted Computer” Type the passcode required And done!!!

The simplest way that I found.

4
  • What if there is no Settings > Developer visible?
    – Dronz
    Feb 13, 2020 at 6:09
  • @Dronz This is usually only visible when you had the device at least once connected. Apr 25, 2022 at 17:36
  • This is the only thing that works for me. Xcode 13.3.x here. Apr 25, 2022 at 17:36
  • This is the way! It should be the selected answer.
    – aryland
    Jan 3, 2023 at 21:30
10

A simple solution:

  1. First, unplug your device.

  2. Now, unlock your device and plug it in again. Be sure that the device is unlocked.

  3. Now run the Xcode project by selecting the device as target.

2
  • 1
    The same for me. With addition that I was able to debug wireless. Dec 23, 2017 at 12:29
  • @MykhailoLysenko Oh, It means you have to shutdown your iPhone's network for a moment thanks for Steven Jobs. : ) Mar 18, 2020 at 15:41
8

When you plug in your iPhone, it will ask you to trust the computer. If you already trust and unlocked but still said your device was locked (bug). Just unplug and plug again then it will work

8

These steps worked for me in iOS 10.

  1. Remove the cable from device.
  2. Plug in the device.
  3. Clean and build the Xcode project.
8

I run into this problem quite often (at least like 5 times a week). Almost every time this happens, a Xcode restart fixes it. But this time nothing seemed to work including:

  • Restarting Xcode;
  • Unplugging and re-plugging the iPhone;
  • Cleaning the project (cmd+shift+k);
  • Cleaning derived data (cmd+option+shift+k)

Done dozens of times in all sorts of different orders.

What fixed the issue for me this time was simply:

✅ Rebooting the Mac.

1
  • 1
    This one worked for me, Though, I killed the Xcode too.
    – Yash Bedi
    Apr 29, 2019 at 9:59
7

Recently I have met the Xcode shows "development cannot be enabled while your device is locked, Please unlock your device and reattach. (0xE80000E2).

If your iOS device is already unlocked and connected to mac and still get the error from Xcode 8.1 after upgrading to iOS 10.1.1, then the mac is not trusted by the device.

To fix it, first disconnect device to mac and then go to iOS settings app, and open general->reset->Reset Location & Privacy.

Then connect device to mac and when prompted, set select trust the mac.

Then wait the processing symbol files within your device and mac. After it finished, you can run the project to your device. It will be working.

0
7

I spent hours trying to fix this issue with no luck.

BE SURE TO DISABLE ANY VPN SERVICES FROM YOUR IPHONE. Just like magic, it started working properly.

1
  • that's F ed up a hole week and I didn't try that, its working now after I disabled VPN
    – mhdjazmati
    Nov 7, 2022 at 11:09
6

This issue is not about "Trust" or not. It's a bug in Xcode.

Just follow these steps.

When Xcode is running and your device is connected:

  1. Lock your device.
  2. Unplug your device from Mac.
  3. Unlock your device.
  4. Plug your device back to Mac.
0
4

Solution: Switch target device to some other (e.g. Generic iOS Device),

enter image description here

then unlock you physical device and switch back to it again.

4

there are two solution worked for me. 1) disconnect your device from the mac and reattach it. 2) disconnect your device from the mac and restart it and then connect it with mac it'll work

4

What solved the issue for me was unplugging the phone, then going to Devices and Simulators:

enter image description here

Then right click on the device and select Unpair. enter image description here

Then plug your phone back in, Select "Trust this computer" and you should be golden.

3

Generally just unplugging/replugging seems to work for me. But today it didn't and something else seems to have worked: I have enabled network debugging on the device in question and it almost looked like it remembered an old network "lock" setting, while not seeing that the device was actually connected via USB. After (temporarily) de-selecting "Connect via Network" and replugging, it got things working again.

2
  • Yeah- disabling and re-enabling network debugging often fixes it for me, when even restarts failed. Jul 9, 2019 at 23:16
  • So wifi debugging is the problem. Mar 18, 2020 at 15:48
1

sometimes your device stops trusting your PC for no reseaon. go to your settings then general > reset > reset location and privacy. and replug your device to your PC again and press "trust this device" prompt that shows up in your phone.

1

Lots of answers, but the one that worked for me (El Capitan, Xcode 8.2) was to close iTunes. If that has a connection to the IOS device then although Xcode can load the app components it will still fail to run it.

1

On your device (iPhone/iPad) goto: Settings -> Developer -> Clear Trusted Computers worked for me.

1
  • this is what I had to do as well to get the 'trust this computer?' prompt to appear when I connected to my computer
    – Nunchucks
    Jun 26, 2018 at 20:31
1

I found that by shutting down a Console and a running Simulator allowed XCode to see my iPhone again. I'd make sure other related programs aren't running if you don't need them.

1

This can also happen due to pending update on your device. This also means you need to update your phone, connect to the MacBook (trust it if needed). This how I found my problem and solution.

1
  • I had the same problem (update was waiting on device) but I didn't have time to update it. Asfand Shabbir's answer worked. (in case readers don't have time to update) May 6, 2018 at 10:55
1

One possibility worth checking, if none of these other solutions work, is that there is no space left on the device. Xcode will not give you a helpful "device full" error to tell you that your device has no storage space left, but it will also not be able to deploy an app build to a device whose storage is full. The only solution in that situation is to delete media or other apps/data to free up enough space.

1

Bizare, but I hope it helps someone. I was connected to a VPN (Pro XPN) and that was causing the issue! Disconnected and it worked.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.