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.

[ghost]

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.

[kaznacheev]

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

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

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

[lazurey]

Thank you, gockxml.

Remember to add proxy for HTTPS

[yrom]

@gockxml Thanks!

[taxusyew]

@gockxml that's it!

[zhjuncai]

GFW = Great F*** Wall

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

[sansmash]

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

[bullgare]

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

[Archieeeeee]

@gockxml thanks

[Sawyer51]

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

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]

Great @paulirish

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

[igo903]

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

[paulirish]

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

[mrdumont]

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.

[Hanruis]

It help me a lot ...and I find that if your Inspector has mess layout, or some other things wrong , you yan open chrome://appcache-internals/ and clear the manifest cache , then reload the resource

[ace-han]

@gockxml You save my days in China!!! Very good job, thxxxxxxx!

[khejing]

@Hanruis I use VPN and still get nothing, after I clear all the cache, then it's back again! Really thank you!

[hakib]

I got the same with Chrome Version 48.0.2564.97 (64-bit) on Ubuntu 15.10 trying to inspect a cordova 5.4 app with crosswalk. After removing crosswalk it worked fine. P.S, same version on windows 7 (including crosswalk) work fine as well.

[SystemDisc]

I have this issue. If I open inspector, a blank inspector opens with the following in the titlebar:

chrome-devtools://devtools/bundled/inspector.html?isSharedWorker=true&remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@f87f641eOabefed98578934of1d5ca79651bf82/&dockSide=undocked

macOS Sierra 10.12.3, Chrome 57.0.2987.98 (64-bit)

[EngleVV]

It works, thanks.

[bbuchalter]

Still an issue for me. macOS 10.12.5, Version 59.0.3071.115 (Official Build) (64-bit). This thread is quite long. Is anyone able to summarize the latest on the root causes and workarounds?

[escapedcat]

@bbuchalter the most common solution for this seems to be a VPN. Because the most common reason to this seems to be related to being in China.
I don't know your individual situation, but if you are not in China it might be related to the specific network setup you are working in.

[zdarovka]

@bbuchalter I believe it has nothing to do with network, I was not on VPN and I am not located in China, and I haven't done anything with my network and it just stopped doing that, thank god. believe it is a random problem

[sigsegv8]

I also get the same issue with an Android 7 device with chrome 59.0.3071.125. My mac has OSX 10.12.5 and has chrome browser version 59.0.3071.115 (Official Build) (64-bit).

All I see is popup that is a empty/blank.

[SystemDisc]

@escapedcat This seems to have nothing to do with being in China (or any specific network for that matter).... I'm in the US - this is just a bizarre bug with Chrome that sometimes (and it's hard to reliably reproduce) results in a second, empty inspector window opening when you open inspector.

To quote my earlier message which has more detail:

I have this issue. If I open inspector, a blank inspector opens with the following in the titlebar:

chrome-devtools://devtools/bundled/inspector.html?isSharedWorker=true&remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@f87f641eOabefed98578934of1d5ca79651bf82/&dockSide=undocked

macOS Sierra 10.12.3, Chrome 57.0.2987.98 (64-bit)

The last time this was happening to me, I tried disabling all extensions and it did not resolve the issue.

[bmlyon]

I too am having the issue SystemDisc described, except on a Windows 10 x64 PC from within the US.

[astanb]

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.

[rickyk586]

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

[tperrelli]

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!

[reyx]

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

[datencia]

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

[DrMabuse23]

thx @tperrelli save my day

[NicolasBehra]

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 :)

[iamjoyce]

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

[rasoulmiri]

Check this ways:

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

[Black-Kitten]

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

[LycheeHe]

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

[dccat1]

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

[robberfree]

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

[metinsevindik]

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 ?