[polisurgist]

The docs say to launch a “debug-enabled” Cordova app to begin debugging. I can launch the app from a file signed with my developer certificate, though nothing changes on the dashboard once I do so.

I’m guessing I’m building this incorrectly, though I’m kind of an Apple dunce, so that’s not surprising. Anyone know?

[support-michael]

> “debug-enabled”

This refers to an ipa file signed with a developer provision profile.

>…. nothing changes on the dashboard once I do so.

A few questions:
1) what ios device are you working with and its os version?

2) are you on windows or mac? What os version (win7, win8, mavericks osx, …)?

3) does your device appear in the GapDebug device panel?

4) is the device connected to the workstation by usb cable? Make sure the device is not asleep when you connect it.

5) when you connected your device by usb cable did you approve the dialog that ask if you Trust or Do Not Trust the GapDebug connection. You should have selected “Trust”. You must pay close attention and do not delay in accepting Trust. If you miss the dialog then unplug the usb cable and reconnect to see the “Trust” dialog again. If it does not appear then try restarting GapDebug.

6) Did you enable webkit inspector option under the Settings>General>Safari>Adavanced?

7) If you are running GapDebug on windows, is itunes installed. GapDebug uses the itunes windows usb driver for device connectivity.

[polisurgist]

I believe the problem with this was that I signed the package with the wrong certificate and now it’s working. But for the record:
Device: iPad 2
iOS 7.1.2
Workstation: Macbook air, 10.9.4
I was connected by cable, the device showed up, my workstation was trusted, webkit inspector was on.

Thanks for the quick response!

[support-michael]

>now it’s working

sweet! If you find GapDebug helpful please help us spread the word with a tweet or other social callout. All help appreciated.

[Author]

Posts