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:
Restart macbook and iphone
Trust in Trust This Computer notification
Xcode Version 11.4.1 (11E503a)
IPhone X ios 13.4.1
I finally figure it out
Connect the iphone(cable not wifi)
Unpair device and quit the xcode
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
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:
Unpair the iPhone (as per answer from #Jeff above).
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.
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
Reconnect/pair iPhone in Xcode's Devices window and Trust the computer.
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.
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
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.
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!
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, ...
I had some success turning Bluetooth off and on again on the phone. Still, the watch often disappears.
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.
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.
I rebooted my iPad, and it eventually worked...
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 :)
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.
When ever I run my app in Xcode 4.4 the simulator fails to open, "iOS Simulator quit unexpectedly." It runs on perfectly on the device though.
I solved by installing xcode 4.5 and ios sdk 6. Now all work fine.
You may have had a bad build on the Simulator, which is now messing things up.
Clean your code (Product > Clean in XCode)
Reset your simulator settings (iOS Simulator menu > Reset Content and Settings)
That should do it.
I Had the same problem i just did following steps and it works fine
1) Reset your iPhone simulator
2) Clean Build your code
3) Restart your computer
Its works for me.
Reboot the simulator ..... sometimes some apps remain in the memory.... Otherwise reinstall it ... some data could be corrupt... :)
I had the same issue on Lion.
After upgrade to Mountain Lion I haven't such issue.
I have googled for two days and still no luck. I am running a Mac OS X 10.5.5 and the iPhone SDK 3.1 beta, running the Aspen Simulator.
My problem is that I can not get any app to work on the Simulator. It builds alright but the simulator shows a black screen and then returns to the main menu. I get this error on Xcode:
Error from Debugger: Failed to launch simulated application. See console.
and in console, it says something about "unable to find springboard (bootstrap lookup error".
Can you please help me?
I think you should think about updating your system. Using an old iPhone SDK 3.1 beta nowadays is really strange, you should update to the latest stable iOS SDK 4.3.3 and test backwards compatibility of your app using the built in iOS SDK 3.2 from iPad. This will help you test the app on this older SDK while getting active support from both Apple and developers.
Tell me if updating solves your issues or not. Thank you!
I've updated for xcode 3.2.5 and iOS 4.2 but now everytime I deploy to device (ipod touch 2nd generation with iOS 4.1 installed) it crashes the ipod and forces it to restart.
then it restarts the device and I can go open the application regularly through its icon.
but the real pain here is that everytime I deploy to the device I have to wait for it to crash, restart the device which takes ages and them open the app by clicking on its icon.
I've already changed the target sdk to be less or equal then 3.0, hence the app working after a restart as it should.
Anyone could help me with the reason for crashing the device?
Thanks in advance
There are plenty of issues with Jailbroken devices at 4.2.1; from Xcode not collecting the Symbols for 4.2.1 from the device, to issues with dylib's loading at debug time. Many debugging facilities won't run on a jailbroken device either. Check to see if you've booted in tethered mode in redsn0w, develop on a different device temporarily, or downgrade to 4.1/4.0.1.
In this answer Brian explained how to connect Shark with the device. I do it exactly this way, but Shark never lists my device. Even if Xcode launches my app on it and the app runs. I get console Logs and everything. It communicates with the mac. But Shark doesn't see it. What could cause this? Snow Leopard, btw...
https://stackoverflow.com/questions/1617677/what-can-i-do-when-shark-does-not-find-my-device
solved the problem for me. The device was running iPhone OS 2.2. It worked until I upgraded to Snow Leopard.
I also had to reinstall CHUD tools from the SDK 2.2 package as well (despite having reinstalled them from the CHUD 4.6 package). Then Xcode could not find the device until I rebooted it too.