Xcode Device Issue - Failed _shouldMakeReadyForDevelopment check even though device is not locked by passcode

Question

Error and warnigs in devices and simulators Issue :

Details

Failed _shouldMakeReadyForDevelopment check even though device is not locked by passcode.
Domain: com.apple.platform.iphoneos
Code: 5
Failure Reason: allowsSecureServices: 1. isConnected: 0. Platform: <DVTPlatform:0x7fecb76471f0:'com.apple.platform.iphoneos':<DVTFilePath:0x7fecb7647170:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform'>>. DTDKDeviceIdentifierIsIDID: 0
User Info: {
    DVTDeviceDescription = "\Ud83d\Udcf1<DVTiOSDevice (0x7fecb9844570), TakHyun\Uc758 iPhone, iPhone, 13.4.1 (17E262), 8d695f88c5c910974df39462a1815a52376a0fa9>";
}

TRY:

1. Restart macbook and iphone
2. Trust in Trust This Computer notification

Xcode Version 11.4.1 (11E503a) IPhone X ios 13.4.1

Answer 1

I finally figure it out

1. Connect the iphone(cable not wifi)
2. Unpair device and quit the xcode
3. Reconnect the iphone and Trust this computer accept Done. If you cant fix it, go to apple dev site reedit the device and do it again 1~3

check this photos

Answer 2

I started getting the OP's error after updating my iPhone to iOS 13.5.1. Here is what worked for me to resolve the issue:

1. Unpair the iPhone (as per answer from @Jeff above).
2. Upgrade Xcode to latest, in my case 11.5 (which I believe is the first version of Xcode to support building to iOS 13.5.
3. NEW: I launched Xcode after updating to 13.5 which prompted me to "Install additional required components" which I did. Xcode extra step after updating
4. Reconnect/pair iPhone in Xcode's Devices window and Trust the computer.
5. NEW: After pairing the iPhone make sure you check the "Connect via Network" checkbox for the newly paired iPhone. By default Connect via Network is unchecked. Important step after re-pairing device

The "NEW" steps are not steps I've seen in previous answers, so I posted this answer.

Answer 3

Or Xcode is just not smart enough to know that your iPhone iOS version is newer than the one supported by Xcode! I had this issue, been trying all solutions until I updated my Xcode from 11.4 to 11.5

Answer 4

So this started for me after I updated Xcode to version 12, and my iPhone to iOS 14. The fix was as listed above (multiple times) to unpair, reconnect, and trust the computer, BUT only after changing the target to iOS 13 in Xcode did those steps actually work. Once it was reconnected I was able to switch the target back to iOS 14 inside Xcode. This one was frustrating.

Answer 5

In my case, I was using an USB to USB-C adapter which apparently my laptop did not appreciate. Switched to a usb-c lightning cable and poof - everything just works. Now I'm mad that I already reset my network settings!

Answer 6

I had issues with Xcode 11.5 and iOS 13.5.1

Sucessful:

• Remove the Logitech Wireless Mouse USB Receiver that was plugged into the USB-C to USB converter (I use this converter to connect both the Wireless mouse AND my iPhone via USB to Lightning cable). This REPRODUCABLY caused the described error "Failed _shouldMakeReadyForDevelopment check even though device is not locked" to reappear when I repeated the re-pairing procedure with the Logitech adaptor plugged in

Not successful:

• Unpairing (from both Macbook or iOS - Settings - Developers - Unpair)
• unplug, Repkug the USB Connector
• Connect via Network setting
• Restart iPhone, MacBook, ...

Answer 7

I had some success turning Bluetooth off and on again on the phone. Still, the watch often disappears.

Answer 8

None of the above worked for me. With iOS 14.0.1 and XCode 12.0.1. I suspected it is an Apple bug with wireless communication to-from the device. Since my iPhone can be used as a hot spot for my Mac, I found that once I used my iPhone as a hotspot from my Mac, XCode was able to upload the App binary to my iPhone and debug.

So I'd say if nothing else works then try to use your iPhone as a hotspot for your Mac, and then you should be able to wirelessly debug.

Answer 9

For me it was the exaxt opposite of the message. Xcode was up to date, but the iphone I was trying to run on was not updated to the latest version of iOS. 13.7 was the version at this time.

After updating to 13.7 the iPhone, everything went back to normal.

Answer 10

I rebooted my iPad, and it eventually worked...

Answer 11

My problem was building the application with a production provisioning profile. in my case, the solution was to switch to the development provisioning profile. Then it worked :)

Answer 12

Mine got resolved when I updated the Xcode from 12.2 to 12.3 Beta.

My iPadOS version is 14.2.

Even though XCode 12.2 supports OS 14.2, I faced the same issue. It is the XCode bug.