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"

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)

+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

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

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

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

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

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.

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.

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)

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
.

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

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.

@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.

This is happening to me when trying to debug a Cordova web view running on Android 5.0.1 (Chrome 42.0.2311.138) - Other Android versions 6+ are fine.

Updating chrome worked for me. Others have stated that there's an issue when the versions differ between mobile and desktop

Hello guys! I've got this issue today.

I did the following steps to solve:

1. Just open chrome://chrome-urls/
2. Search for "for debug" section.
3. Access chrome://restart/ url

chrome://restart/ might be different from restarting the pc or simple closing and reopening chrome like a normal user (i don't know why).
I believe that this command really force to restart all processes or something like that!?

Anyways, i use Mac OSX and now i'm abble to debug again. See ya!

For me the solution was update chrome to the latest version 65.0.3325.162 (Windows)

same over here... yesterday it was working ok, magically not today. Fixed upgrading chrome to 65.0.3325.162

thx @tperrelli save my day

On ubuntu I just installed google-chrome in BETA:

sudo apt install google-chrome-beta

and the dev-tools work again like a charm
Hope it helps :)

@reyx Thank you. Goodness me, there was no prompt on Google Chrome to say that the version was outdated. I had to download the exe instead.

Check this ways:

1. update chrome in mobile and in windows or mac
2. use VPN for connect to server google (China, Iran,...)

我在检查器里面能够看见dom节点 但是里面都是空的 除了script标签
有大佬能够给我什么帮助吗。。

I know this issue posted long time ago, but I have to say
this answer(Remote debugging with Chrome downloads files from https://chrome-devtools-frontend.appspot.com.
Test your connection: Try to open https://chrome-devtools-frontend.appspot.com
If it doesn't work, thats why you're getting an empty window.
In this case maybe you need a VPN.)
let my confusion go, I try many times to reload my android app and click 'inpect' button from DevTools in chrome.

Thanks a lot

Any solution now? I had tried all solutions i can find on google but got the same blank

@dccat1 No easy way.I tried different ways last week.The easiest way maybe setup a network that can access google service.

FYI, the last step needs to visit https://chrome-devtools-frontend.appspot.com. If you cannot open the link, that's why you got an empty window. 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.

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

I was able to open this url. But still not working.
Is there any solution ?