[jazzhammer]

hi.

using: gapdebug 2014 EA3, cordova 3.5.0, on iOS 10.8.5, and specifying debug <application android:debuggable=”true” />, the build successfully compiles a -debug.apk.

i installed the apk using adb on a nexus 10: android 4.4.2 and it runs.

gapdebug is running on port 8081 without complaints and the debugger detects my device and and app. ie:

“R32D400GHTB, Nexus 10, Android 4.4.2”
“com.casebank.lantern – Lantern”

when i click on the app in debugger, the debugging pane in the ‘Lantern’ tap remains blank, and there is a “Waiting for localhost…” status at the bottom. things are obviously hanging, but i don’t know what. and i’m just dying to do some sweet debugging here.

my chrome is Version 37.0.2062.94

tips to overcome this hurdle would be highly appreciated.

[jazzhammer]

and.. a little update.

tried all the same steps with a simple helloworld app. same result: debugger is just waiting for localhost… when i click on the helloworld app under the device’s entry in the list of devices.

[support-michael]

@jazzhammer
Thanks for sharing this issue.
Do me a favor an in your chrome browser please attempt to load this URL:
https://chrome-devtools-frontend.appspot.com/serve_rev/@169177/devtools.html

You should seem a page similar to that shown below. Let me know if it loads or fails. See attachment chrome-dev-tools.png

Attachments:

You must be logged in to view attached files.

[jazzhammer]

yup. it loads. with one error:
GET https://savingsslider-a.akamaihd.net/loaders/1036/l.js?aoi=1311798366&pid=1036&zoneid=92250 net::ERR_FAILED

[support-michael]

Thx for that info. I asked another dev to give this a look, which will not be avail until early tomorrow (tue).

One more question, are you behind a firewall?
I’m wondering if something is blocking GapDebug’s network access.

[jazzhammer]

i definitely am behind a firewall. if you have a list of things to open up, i can hand it over to the IT guys and keep trying.

[support-michael]

>i definitely am behind a firewall

That’s the issue. See the screenshot for accessing the GapDebug network settings (this is windows ver).
We are working on a revised architecture that will generally not required network setting for standard proxy servers. See attachment GD-networksettings.png

Attachments:

You must be logged in to view attached files.

[jazzhammer]

okay, thanks. that’s helpful.

in the interest of making the documentation better, please consider making a change to the explanation of the network settings in the user manual. it currently states :

“The network connection settings are relevant for checking for application updates, which is done automatically.”

it didn’t occur to me from this that the connection settings were relevant for any other purpose than app updates, such as base functionality.

i’ll try running less securely from outside the firewall to confirm this is the issue.

[support-michael]

Opps! That’s definitely goofed.

Another dev and I discussed this morning revamping the architecture to completely get rid of this network settings hassle. You situation reinforced the need to get this in place soon.

Request: when we impl the update would you be open to test driving it behind your firewall. It will not do anything tricky. It’ll just run over the browser’s std firewall settings that most organizations setup automatically on their networks.

[jazzhammer]

yup, i’ll try it out.

you have me curious though: why does gapdebug require a connection inbound ?

[support-michael]

>why does gapdebug require a connection inbound

Here’s the scoop (I’ll ask lead dev to chime in if I goof this up). Internally the GapDebug device connector runs a private web server that serves the connector api. The debugger UI is implemented as web app and runs in chrome connecting back to the device connector’s web services api. The GapDebug inspectors load the device/android version specific chrome developer tools from google over the web. In the first couple of early-access releases we were loading the tools directly from the chrome browser into an iframe. But with goggle’s move to https everywhere we hit a snag just before going live with EA3 that necessitated a quick workaround. We had to reimplement and migrate the loading logic down into the device connector’s java core. The ripple effect of this is that the java core is temporarily handling connections with google’s servers to access dev tools until we have a bit more time to properly move the functionality back to the browser. Until then user have to configure the network settings to tell the device connector how to work with any http and https proxies that may lie between it and the web.

I hope this make sense.

[jazzhammer]

hi again.
i’ve been debugging with both my dev machine and the mobile outside our firewall.
i need resources inside the firewall and it’s really inefficient, not to mention annoying, having to bounce back and forth between the two.

i want to give our IT group some instructions regarding what to open up on the firewall so i don’t have to do this.
as well, i don’t have much description about the fields in the settings panel, just this description in the manual:

“Network Settings – If you are restricted to specific port numbers, you can specify a port by selecting the User Assigned Port option. If you make a port change, you must restart the debugger because the connection is lost.”

ie. if IT can open up an inbound port and route it to my ip, what values do i put in what fields in the debugger and network connections fields ? eg. what active provider do i pick ? what does each of the active provider settings mean ? does “system assigned port” refer to a port my dev machine assigned if i’m running a firewall on the local machine ? or is that the port that IT opened up ? are they the same thing ?

[nonsense]

Hello,

I am Win 8.1 user get same problem like OP.
I am using “User assigned port (8088)” for network setting and Active Provider set to “Native”. How I can fix it?

[Author]

Posts