The problem with 1.Xcode running occurs:
Please verify that your device ' s clock be properly set, and that your signing certificate are not expired.
This is the expiration of your certificate.
Solutions
In Xcode, went to Preferences--> Accounts--> View Details, there is a download all at the bottom left, just reconfigure it.
2.couldn ' t be completed. (launchserviceserror error 0.)
Solution: Choose iOS Simulator, reset.
3.could not launch "" Process launch failed:security
Workaround: Set-> General-> description file and Device Management-> Developer Application-> Trust the application you run
4.
Go to the/users/victor/library/mobiledevice file, delete all your previous configuration files, and add it again, OK.
5.
iOS true machine debugging
Solutions
In Xcode, went to Preferences--> Accounts--> View Details, there is a download all at the bottom left, just reconfigure it.
There are also errors after downloading the certificate here. Here's a further look at how the error occurred.
Since the certificate is wrong, you must look into the Keychain Access management tool.
See the keychain-certificate, found the following questions, screenshots are as follows:
The problem is quite clear.
This way through the Xcode download certificate, is actually installed a new certificate, but the same certificate did not cover the previous.
This side will directly delete the same, expired certificate.
Then run the project again, OK.
Summary: All certificate problems, most of them are in the keychain certificate multiple duplicates, and there is no coverage, you need to delete the certificate before the expiration.
6. "(null)" is of the ' model ' is ' not ' supported by this version of Xcode. Use a different device
Today the real machine run ran into this problem ("(null)" is of a model, is not supported by this version of Xcode. Ple), found that the Xcode will be restarted after the real machine can run, meet this problem friend can try
7.
Problem: Running a new device for the first time, no trust
Workaround, unplug reconnect, select Trust.
8.
Mobile phone system updated, need to download new packages into the Xcode
The steps are as follows:
Open Finder
Locate the Application Folder
Find Xcode in there.
Click Xcode, right button, display package content
Contents-->developer-->platforms-->iphoneos.platform-->devicesupport
/applications/xcode.app/contents/developer/platforms/iphoneos.platform/devicesupport
And then you can see some of the system models for your Xcode-supported real-machine tests. corresponding files
9. The project on the iOS running to the real machine prompts the device to be locked for resolution development cannot be-enabled while your device is locked.
Solution: After the mobile phone was upgraded to iOS 10, the development cannot was enabled while your the device is locked.
Here is you to this computer set up distrust;
The solution is: Open mobile phone settings-> General-> restore-> restore location and privacy;
Then there will be a window to indicate whether you trust this computer, click Trust, restart Xcode, and then run the project to the phone 10.
Workaround:
1, try to reseat the test equipment.
2, if "1" does not work, restart Xcode try.
3, if "2" does not work, restart the phone, and then try.
4. If the former Sandu does not work, use the question 5 method.
11.iOS true Machine debugging problem-app installation failed
Problem with real machine debugging free app ID
The maximum number of apps for free development profiles has been.
Free Application Debugging Maximum
Apple's free app ID can only run 2 applications, when the third debugging will report this error, must be removed before the application to debug new problems
The free ID can hold up to 2 applications, and when it comes to the third, it will be reported as the wrong solution.
Connect iphone Open xcode->window->devices
Open Xcode->window->devices and then the interface appears.
There are currently three applications, including one that was deleted by the application running this time, not the application running this time
Select the application you want to delete, click the-number and then the frame
Directly select Delete to run again, workpiece 12. This application are modifying the AutoLayout engine from a background thread after the engine being accessed from the M Ain Thread. This can leads to engine corruption and weird crashes. From the above error information can be seen, the main thread at the time of operation, the child threads modify the main thread UI layout constraints, in iOS development, all the interface UI update operation must be done in the main thread. Such errors can easily occur when block is used, because block is done in child threads.
The solution is to put the action on the UI update into the main thread in the code that you just wrote.