xcode - failed to get reply to handshake packet

K

5

8

When I make a build, the build is installed in the device but XCode is giving this error:

"failed to get reply to handshake packet"

and it won't launch the game, so I'm not able to see the console for debugging. The game runs fine if I manually start it in the device. I need the see the console for debugging.

My XCode version is 5.1 iOS version in the device is 7.1 (iPod Touch 5th gen) Unity is 4.3.3

I really appreciate any solution from you guys.

Thanks in advance.

Keilakeily answered 18/3, 2014 at 7:35 Comment(1)

The error is from Xcode or your server or compiler? – Adcock 18/3, 2014 at 7:45

I

9

This might be a bit late for the op, but I found that my problem was caused by having my app running manually on the device. It seems that if you launch the app on the device then xcode can't connect to the process and the handshake error is reported.

Indoor answered 24/11, 2014 at 14:16 Comment(1)

In my case it also helped. When I removed the app from recent (double 'Home' -> swipe up) Xcode was finaly able to proceed – Adeleadelheid 7/1, 2015 at 14:10

S

7

I know it's a late answer, but in my case a simple Clean command solved the problem.

Suk answered 10/10, 2014 at 14:19 Comment(1)

I can't see how this is not an answer to the question. It seems to me like a perfectly acceptable answer. Please make sure you really do understand an answer before flagging it as not-an-answer. If you don't know the Xcode IDE (which your profile seems to suggest), then please assume you do not understand the answer. – Pycnidium 17/3, 2015 at 15:54

I

6

Cmd+Shift+K solved my issue.

This combination actually cleans the build folder. This way the next build will be fresh and will remove any issues in the previous build(s).

Igneous answered 21/9, 2018 at 7:29 Comment(2)

Could you perhaps elaborate a little what this key combination does and why exactly it solves the problem? Perhaps add a link to the appropriate documentation? – Daliadalila 21/9, 2018 at 8:31

I think it cleans the output/build folder. This fixed the issue for me as well. Always nice to have a shortcut instead of needing to do serial clicking on random icons on the gui – Towardly 15/5, 2020 at 2:20

S

3

Restart of the device solved the problem for me

Skyla answered 10/7, 2015 at 18:7 Comment(0)

S

0

Check that you're not running using a release configuration.

Go to Product Menu > Scheme > Edit Scheme and make sure that the Run item is using the Debug build configuration.

Signac answered 18/3, 2014 at 7:36 Comment(5)

I just checked in the Scheme and it is using Debug configuration. It was working well before updating the iOS (7.0) version and XCode. – Keilakeily 18/3, 2014 at 8:46

It's not just lack of symbols. Release builds set the entitlement get-task-allow to false so the debugger can't connect. The error message is not exactly the same, but it's not crazy either. – Signac 18/3, 2014 at 8:46

I just did the "Reset All Settings" thing in the settings of the device and it's working now. It seems like the problem was with the device. Thanks to everyone for the answers. – Keilakeily 18/3, 2014 at 9:25

@trojanfoe: This is a perfectly acceptable answer, not a comment. – Pycnidium 17/3, 2015 at 15:58

@Pycnidium Agreed; comment deleted. – Swayder 17/3, 2015 at 16:0

Recommended topics

Hot tags