failed to send the qLaunchSuccess packet

Question

I am using XCode 4.3.2 and trying to open an already existing project based on the Facebook SDK sample Project for XCODE and run it on a target IPhone with IOS 4.2. Although it runs on the simulator it crashes on the IPhone printing this error on the console:

failed to send the qLaunchSuccess packet

I really do not know what could be the problem

possible duplicate of [failed to send the qLaunchSuccess packet, can't debug in the device](http://stackoverflow.com/questions/9834708/failed-to-send-the-qlaunchsuccess-packet-cant-debug-in-the-device) — CodaFi, Apr 07 '12 at 14:12
it is actually the same problem but I have already looked at that question's answers and they do not apply or fix my issue — Andrea Sindico, Apr 07 '12 at 14:17
Then you have a privileges issue. Restart your phone and try again. — CodaFi, Apr 07 '12 at 14:19
Restart your phone. You know that long list of privilege options in the build settings tab? Those. They break occasionally. — CodaFi, Apr 07 '12 at 14:21
you got it! thank you it was driving me crazy, answer the question so that I can accept it — Andrea Sindico, Apr 07 '12 at 14:28
I get this all the time, really annoying, restart the iOS device is the only 'fix' I have found — Adam Waite, May 08 '12 at 13:39
Restart device and Xcode not help. I found that I'm using distribution provision profile. Hope this help. :) — TK189, Jun 12 '12 at 03:03

score 22 · Answer 1 · answered Jun 15 '12 at 11:52

22

This happened to me when I accidentally tried to do a device debug using a distribution profile. As soon as I noticed and switched it to a dev profile, the issue went away.

answered Jun 15 '12 at 11:52

Bek

2,206
20
35

CodaFi · Accepted Answer · 2012-06-11T16:05:45.190

16

You might have some broken privileges or a hung debugger process (one that didn't quite exit fast enough). Restart Xcode or restart your phone, either way, it's not as bad as it's more annoying cousin, Processes That Can't Be Registered To The BootStrap Server

If all else fails, restore it from a backup.

edited Jun 11 '12 at 16:05

answered Apr 07 '12 at 14:35

CodaFi

43,043
8
107
153

changed nothing for me unfortunately – Holger Frohloff Apr 20 '12 at 09:01
3

Well it helped the OP. the 3 downvotes were completely of of character. – CodaFi Apr 20 '12 at 15:46

score 6 · Answer 3 · edited May 23 '17 at 11:58

In Xcode 4.3.3, this is caused by re-running the app (command+R) or stopping it (command+.) while halted on a breakpoint. To fix the error once you've gotten it, it usually works to stop the app, (command+.), unplug the device, plug it back in, and run the app again.

To avoid the issue in the future, remember to continue (command+control+y or hit the play button near the debugger output) before stopping. If you have many breakpoints or are in a loop, you can deactivate one breakpoint by going to that line and hitting command + \ or you can deactivate all breakpoints by hitting command + y.

If you eventually get the error ending in "This generally means that another instance of this process was already running or is hung in the debugger," you need to reboot the device.

I submitted a bug report to Apple. I suggest you all do the same so that this gets the attention it deserves.

Edit: the "qLaunchSuccess packet" bug doesn't happen in Xcode 4.4 or 4.5 as it did in 4.3. However, 4.4 and 4.5 experience "Timed out waiting for app to launch" instead--possibly the same issue with a new message. See this question for some possible solutions. Nothing works for met yet. The behavior seems different than 4.3.3 because the error doesn't come up every time I stop while halted on a breakpoint. I will experiment and see if my workaround for 4.3 also fixes the 4.4/4.5 issue.

mahboudz · Answer 4 · 2012-05-03T12:41:57.473

3

I get this every time my app crashes, and I restart it by doing a Run. If I hit the Stop button before doing a run then I don't get this.

After some time, if I keep hitting Run instead of Stop first, the iPhone will only show the above error message and the only solution is to restart the iPhone. Quitting and restarting Xcode does not help.

This may be an Xcode bug.

edited May 03 '12 at 12:41

answered May 03 '12 at 09:45

mahboudz

39,196
16
97
124

score 0 · Answer 5 · answered Jul 11 '12 at 15:29

A slightly quicker way to resolve this issue without restarting the device is to change the language.

Settings - > General - > International (4th from bottom) - > Language (top)

Alternatively If you have a bugged News stand app (in a folder) just tap it to restart springboard.

score 0 · Answer 6 · answered Sep 26 '12 at 20:51

0

I had this error when I was trying to install over a bad version of the app that had been crashing on launch. Restarting Xcode and the device did not make the error go away, but deleting the app fixed the problem.

answered Sep 26 '12 at 20:51

user1139733

986
9
14

failed to send the qLaunchSuccess packet

6 Answers6

Linked