"iOS true Machine Debug error Rollup" Could not executable permissions on the application.

This chapter no longer describes how to debug the real machine, but constantly summarize the real machine debugging errors encountered, record down, we learn progress together.

Error 1:could executable permissions on the application.

This error means that the same bundle identifier can not be reused, and then, in layman's terms, we have debugged and installed COM before we actually debug the device. XXX.ABC identifier application, and now a new project, in order to lazy, and use this identifier, and then debug on this device, will prompt this error.

Workaround: Then remove the previous application from this device, and then debug, no problem.

Error 2: A Valid provisioning profile for this executable is not found.

For this error, first select the project--targets--build settings-code sign identity-see if the Debug option has developer certificate selected.

If the debug certificate is not a problem, open the Organizer panel, look at the device Provisioning profiles there is no corresponding provision file, if you have to import it, debugging again, there is no problem.

If import when found local provision file imported error, which may be your current developer certificate has been revoke dropped, login developer.apple.com

Check to see if the certificate is invalid.

If it is not valid, click on this line, edit

If your device is not checked, please remember to tick on, then save, save the successful download this file, in the Organizer Panel import this file, it should be no problem.

"iOS true Machine Debug error Rollup" Could not executable permissions on the application.