Inspect opens an empty window

[samhed]

EDIT by admin December 2014: The following information from @gockxml is very helpful for developers in China:

致中国同胞：如果你按照要求操作最后却得到一个空窗口，翻墙后再试试。不用谢。

1. Remote debugging with Chrome downloads files from https://chrome-devtools-frontend.appspot.com.
2. Test your connection: Try to open https://chrome-devtools-frontend.appspot.com
3. If it doesn't work, thats why you're getting an empty window.
   1. In this case maybe you need a VPN.

This is really a problem for people in China because the appspot.com domain is blocked by GFW. So sad.

(original issue follows…)

---

---

---

When clicking "inspect" next to the url of the page open on the Nexus 7 an empty window shows up and nothing happens.

ADBPlugin (0.9.6) in Chrome (Version 28.0.1500.89 beta) running on Fedora 18.

[MichaelRFairhurst]

I am having this issue as well! Please let me know if you find a solution.

On Fedora 17, chrome stable 28, nexus 4 (jellybean), adbplugin 0.9.6

Here is the data being passed to chrome.send('inspect', data); bound to the inspect link's onclick

adbDebugUrl: "/devtools/page/1"
adbFrontendUrl: "https://chrome-devtools-frontend.appspot.com/static/18.0.1025.166/devtools.html?host=&page=1"
adbModel: "Nexus 4
↵"
adbPackage: "Chrome"
adbSerial: "01b6f5d40a61745f"
adbSocket: "chrome_devtools_remote"
attached: false
faviconUrl: "http://192.168.3.50/favicon.ico"
name: ""
pid: 0
processId: 0
routeId: 0
type: "adb_page"
url: "http://192.168.3.50/#fasttrack/1"

[sam3k]

same here. Worked for a few minutes and then i got the blank popup.

Same here. Not one successful debug session yet after a day filled with joy.

Also noticed that it loses connection with the device roughly every minute.

Version 29.0.1547.15 dev on MacOS 10.8.4, targeting Nexus 4 running 4.2.something (sorry, device went out window)

[doochik]

+1
I see some errors in insepct for the remote debug console

Uncaught TypeError: Object #<Object> has no method 'setToolbarColors'
Uncaught TypeError: Object #<Object> has no method 'setDockSide'

OSX 10.8.4, chrome 28.0.1500.71 beta, try to debug nexus 7 4.2.2

[hrussell]

I'm experiencing the same problem. Has anyone figured this one yet?

[ginchly]

Same for me unfortunately - looking forward to trying this out though!
OSX 10.7.5, Version 30.0.1568.0 canary, adbplugin 0.9.6, nexus 4 running 4.2.2

[lukeedmonds]

Same error too, hopefully someone will figure it out soon enough.

[bullgare]

same error. Mac OS X 10.7.5.
I can provide extra data on demand.

[dhharker]

I was experiencing this, linux mint 13, 29.0.1547.22 beta + adb 0.9.6.

FIXED: Installed latest version of Chrome (HTC One S) from Play and it has started working.

[stuartmemo]

Same here on 30.0.1581.2 canary osx 10.8.4 trying to debug Chrome 18.0.1025469 on Nexus 7.

Seen a few reviews on the Chrome Web Store seeing this same bug.

[ericente]

Had this problem on OSX 10.8.4 and Desktop Chrome Beta 29. Resolved by updating to the latest version of mobile Chrome on the Android device (Nexus 10)

[paulirish]

This error will manifest if your Chrome on Android is v18. You will need to
update it from Play to get it working.

On Tue, Aug 6, 2013 at 12:18 PM, Eric notifications@github.com wrote:

Had this problem on OSX 10.8.4 and Desktop Chrome Beta 29. Resolved by
updating to the latest version of mobile Chrome on the Android device
(Nexus 10)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-22203713
.

[ginchly]

Ah of course - thanks Paul, this fixed it for me.

[donaldr]

The instructions (https://developers.google.com/chrome-developer-tools/docs/remote-debugging) categorically state that Chrome on your phone has to be at least version 28. Check the version of your Chrome. If it's anything less then update via the play store.

[paulirish]

@donaldr we updated them recently to be a bit more clear as a result of this issue thread. :)
The docs got other updates that should make all this much easier, but we're still improving things and in a month or so I hope to share some of the improvements to remote debugging we've been working on.