21
votes

I'm developing an iOS 8 app in Xcode 6.0.1 and running it on my iPhone 5 (which has iOS 8.0.2 on it). Before I updated to iOS 8.0.1 and Xcode 6.0.1, I never got the error I'm getting. However, now, sometimes when I try to run my app from Xcode onto my iPhone, this error message pops down from the top of the Xcode window:

Could not launch "[app name]". Process launch failed: 4294967295

It appears that this error only occurs when I first run the app from Xcode onto my device (i.e. if I close the error message in Xcode, but I don't close the app on my phone--so the app's still up on my phone--I don't get this error when I click the run button again in Xcode). However, there doesn't seem to be a whole lot of consistency because sometimes the error message doesn't drop down even when I launch the app onto my phone for the first time from Xcode (i.e. without the app already being up on my phone).

Also, I have tried several solutions, none of which have completely fixed the error:

  1. Clean out the build, clear out DerivedData, restart my mac, and reopen Xcode.
  2. Get a new certificate for the app from apple after accepting their new iOS 8.0 license agreement.
  3. Make sure that, when I install 3rd party Cocoa pods, the Podfile specifies iOS 8.0 platform.
  4. Set the app's deployment target and build settings for iOS 8.0

I can't seem to figure out how to get this error to consistently stay away even after trying the above-mentioned solution attempts. Again, I can still run the app on my phone normally sometimes, but every couple of runs it displays the strange error message in Xcode and only opens the app on my phone but won't link it with Xcode (for console output, etc).

Any help would be much appreciated. Thanks!

3
I'm having the same error as you. I've checked my provisioning profiles, code signing and also that I'm compiling for Debug but nothing seems to fix the problem. Did you find any solution to this? In my code, I'm calling a huge C source code and, the error disappears when I comment some function calls, but I don't know why. I didn't found anything special inside the functions.Octan
In case it helps you. My problem was that I was defining a huge array in the C code: integer big_array[150000000]. The required memory for this array was reserved when launching the application and the iPad run out of memory. Making it smaller fix my problem.Octan
Thanks. I only have the issue occasionally and rather inconsistently. It seems to have mostly gone away now.Ethan G
I'm just doing some basic stuff with Security.framework (keychain).Nicolas Miari

3 Answers

26
votes

We have encountered this before. The cause was we were using Distribution provisioning profile on Development.

You need to use a Development provisioning profile if you want the debugger to link to your XCode.

Hope this helps!

3
votes

Have you tried disconnecting the device and rebooting it?

When I have seen this, the app was always running, but Xcode was not able to attach the debugger to the process (or attach it quickly enough.)

0
votes

For me the fix was opening the Device Manager (Window -> Devices) and deleting the installed app (select the app and click the "-" button). On the next run the error went away.

XCode 7.3.1