IPhone SDK - error from the debugger: the debugged program does not start

I followed the exact instructions on the iPhone SDK Developer Portal by running the assistant found on the first page.

But I still get the same error, although I deleted the training profile, certificates many times and repeated the same process more than once.

Please, help.

+7
iphone xcode
source share
8 answers

If you used them before ... check that NSDebugEnabled, NSZombieEnabled, MallocStackLogging and MallocStackLoggingCompact are disabled in the Executable Information panel. You cannot work with them on the device.

+3
source share

This can happen if you create using a special training profile. If you followed the steps from Creating an application using Xcode for Distribution , you create a special Entitlements.plist in which you disable get-task-allow - this prevents the debugger from connecting to the application.

Try creating a different provisioning profile (for example, a development profile).

+3
source share

Reboot the device and Xcode - this usually clears it for me

+1
source share

When you create the distribution, make sure that the "Active SDK" has the SDK installed on the iPhone and not the iPhone Simulator SDK. By installing it in Simulator, you can still create the application, but it will give you this error when you try to run it on another device.

In addition, make sure that whenever you plan to install a new assembly, you first change the current version of the project in the project settings to a new version number.

-Drew

0
source share

Make sure that you uninstall and reinstall all training profiles in Organizer and on your device (also using Organizer). Profiles exist in 2 places.

0
source share

I had the same problem. My solution was to close Xcode, run it again, and then do a clean build. It works for now.

0
source share

Restart the dam device! it worked for me. I was performing the extensive frenzy of deleting backups.

0
source share

Removing the debugged application from the phone and restarting the X-Code resolved this for me.

0
source share

All Articles