ADBPlugin icon indicating copy to clipboard operation
ADBPlugin copied to clipboard

Published 20 hours ago • verified publisher icon googlearchive

Inspect opens an empty window

Open samhed opened this issue 11 years ago • 113 comments

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.

screenshot from 2013-07-03 12 22 35

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

samhed avatar Jul 03 '13 10:07 samhed

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"

MichaelRFairhurst avatar Jul 03 '13 17:07 MichaelRFairhurst

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

sam3k avatar Jul 09 '13 01:07 sam3k

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)

ghost avatar Jul 11 '13 03:07 ghost

+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

doochik avatar Jul 11 '13 08:07 doochik

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

hrussell avatar Jul 16 '13 14:07 hrussell

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

ginchly avatar Jul 18 '13 18:07 ginchly

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

lukeedmonds avatar Jul 22 '13 10:07 lukeedmonds

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

bullgare avatar Jul 22 '13 16:07 bullgare

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.

dhharker avatar Jul 24 '13 00:07 dhharker

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.

stuartmemo avatar Jul 31 '13 10:07 stuartmemo

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)

ericente avatar Aug 06 '13 19:08 ericente

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 [email protected] 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 .

paulirish avatar Aug 08 '13 13:08 paulirish

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

ginchly avatar Aug 14 '13 16:08 ginchly

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 avatar Aug 22 '13 18:08 donaldr

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

paulirish avatar Aug 22 '13 20:08 paulirish

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

kaznacheev avatar Sep 03 '13 07:09 kaznacheev

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.

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

gockxml avatar Oct 29 '13 04:10 gockxml

Thank you, gockxml.

Remember to add proxy for HTTPS

lazurey avatar Nov 01 '13 06:11 lazurey

@gockxml Thanks!

yrom avatar Nov 22 '13 03:11 yrom

@gockxml that's it!

taxusyew avatar Dec 16 '13 06:12 taxusyew

GFW = Great F*** Wall

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

zhjuncai avatar Dec 19 '13 14:12 zhjuncai

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

sansmash avatar Dec 22 '13 06:12 sansmash

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

bullgare avatar Dec 23 '13 08:12 bullgare

@gockxml thanks

Archieeeeee avatar Jan 12 '14 02:01 Archieeeeee

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

Sawyer51 avatar Jan 15 '14 09:01 Sawyer51

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.

paulirish avatar Feb 17 '14 08:02 paulirish

Great @paulirish

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

zhjuncai avatar Feb 17 '14 14:02 zhjuncai

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

igo903 avatar Feb 28 '14 04:02 igo903

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

paulirish avatar Mar 04 '14 19:03 paulirish

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.

mrdumont avatar Mar 05 '14 14:03 mrdumont