Inspect opens an empty window

samhed commented 11 years ago

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

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

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.

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.

screenshot from 2013-07-03 12 22 35

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

MichaelRFairhurst commented 11 years ago

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 commented 11 years ago

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

ghost commented 11 years ago

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 commented 11 years ago

+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 commented 11 years ago

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

ginchly commented 11 years ago

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 commented 11 years ago

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

bullgare commented 11 years ago

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

dhharker commented 11 years ago

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 commented 11 years ago

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 commented 11 years ago

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 commented 11 years ago

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/GoogleChrome/ADBPlugin/issues/14#issuecomment-22203713 .

ginchly commented 11 years ago

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

donaldr commented 11 years ago

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 commented 11 years ago

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

kaznacheev commented 11 years ago

Good news everyone! This problem is fixed in Chrome 31.0.1616.0.

gockxml commented 11 years ago

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.

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

lazurey commented 11 years ago

Thank you, gockxml.

Remember to add proxy for HTTPS

yrom commented 10 years ago

@gockxml Thanks!

taxusyew commented 10 years ago

@gockxml that's it!

zhjuncai commented 10 years ago

GFW = Great F*\ Wall

Thanks @gockxml It helps but the ajax couldn't access my server behind proxy :-(

sansmash commented 10 years ago

Same issue here. But I'm having version 32 in both mobile and computer as well.

bullgare commented 10 years ago

@sansmash they say you don't need it in chrome 32 anymore - http://youtu.be/gZH1d2Co1X0?t=1m48s

Archieeeeee commented 10 years ago

@gockxml thanks

Sawyer51 commented 10 years ago

@paulirish I am developer in China, with VPN, I still got a blank window after inspect? I used the updated versions of Chrome canary and Chrome Beta. Please, help. Thanks.
I seems like all the contents that supposed in the windows stay in the title.

paulirish commented 10 years ago

quoting @gockxml …

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.

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

Unfortunately this is still the case. We're looking at solutions.

zhjuncai commented 10 years ago

Great @paulirish

I hope one day in China we don't need VPN at all to use google services, that will be awesome!!

igo903 commented 10 years ago

@gockxml Thank you for finding the root cause. Goagent can help on this.

paulirish commented 10 years ago

@igo903 can you write up a guide on how to use goagent to resolve this problem?

mrdumont commented 10 years ago

The remote debugger had been working perfectly for me until an update to chrome beta v34.01.1847.36 yesterday. Now I'm experiencing the blank screen. I am able to open https://chrome-devtools-frontend.appspot.com/ but tried a VPN anyway just in case. No change, still not working.

travisholliday commented 10 years ago

Sadly, I am having this issue now as well. In the same boat as @mrdumont .

yangjunjun commented 10 years ago

@gockxml Thanks. And Fuck GFW.

pauloneves commented 10 years ago

Same has @mrdumont Failed with Chrome Beta, but is working with the default chrome. My host machine is Ubuntu 13.10

MoritzGiessmann commented 10 years ago

Same here. Chrome 33.0.1750.154 m on Win7 and Chrome 34.0.1847.114 on my Nexus 5. It worked some versions ago.

AzazelN28 commented 10 years ago

Yep, same here. Chromium 33.0.1750.152 Ubuntu 13.10 and Chrome 34.0.1847.11 on Nexus 4. This morning it was working fine, so I tried to fix this by my self (yup, I'm very optimistic) and in the Developer Tools of the Developer Tools it shows me these errors:

Uncaught TypeError: Object #

googlearchive / ADBPlugin

Inspect opens an empty window #14

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