debugger wont start with a device (works with Xcode)

when trying to start a debug session on a connected device, i get this :

Screen Shot 2014-08-29 at 3.13.01 PM.png

When opening the same projetc with Xcode, it somehow is able to deploy the app and start the debug session. What gives ?

ps : i have done the obligatory wtf incantations : clean project, invalidate caches and restart, and an incantation to the AppCodeWarriors on mount Fuji.

pps. version 3.0.4, exCode 5.1, iPhone 4S (7.1.2)



Attachment(s):
Screen Shot 2014-08-29 at 3.13.01 PM.png
2 comments

Oh, there are so many things that can go wrong here :)

Here are several of them out the top of my head:
— Check provisioning profiles. Xcode sometimes can get them automagically, AppCode requires them to be set correctly.
— Try restarting Mac/iOS device. I know that it sounds stupid, but it really helps sometimes.
— Check that you do not use AdHoc profile instead of Debug
— I've had problems when there were two versions of the same app on the device (with different bundle ids).

I use AppCode a lot and sometimes get stuck for hours not being able to do simple things like debugging. Xcode may or may not work at the same time.

(I agree that this is possibly a bug in AppCode)

0

ok , it is a bug. I had done all the know AppCode rituals before posting. Here is one to add to you long list of reasons. Turns out it is in the info.plist

was

 
<key>CFBundleDisplayName</key>
<string>Battles</string>
<key>CFBundleExecutable</key>
<string>Battles</string>


changed to

 
<key>CFBundleDisplayName</key>
<string>battles</string>         <---- NOTICE THE case of BATTLES 
<key>CFBundleExecutable</key>
<string>battles</string>


somehow (i think) appCode does not use that property when launching the debugger, but the product name variable (${PRODUCT_NAME} ... i think. This all began after i had to rename the project with Xcode (my mistake), it mangled the .xcodeproject file very badly, and everything got fugazzi for a while. I fixed the file, as well as the info.plist by hand , and ended up with this. Still, even though xcode did its usual thing ... a total mess ... in this instance i think it is correct in the debugger launch.

0

Please sign in to leave a comment.