Inspect opens an empty window

[googlearchive]

Inspect opens an empty window

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

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

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

[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

[paulirish]

If you have Chrome 34 on your device you'll need to debug it with a desktop
browser that is at least 34.

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)

[mrzzcn]

使用这个工具: https://github.com/huhamhire/huhamhire-hosts 更新最新的Google IP
下面这个是最近更新的.
64.233.162.83 chrome-devtools-frontend.appspot.com
每次更新完成之后, 查找Google.com对应的IP,把chrome-devtools-frontend.appspot.com这个域对应到那个IP.

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

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

[zhjuncai]

Great @paulirish

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

[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

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

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

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

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

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

[travisholliday]

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

[yangjunjun]

@gockxml Thanks.
And Fuck GFW.

[pauloneves]

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

[MoritzGiessmann]

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]

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 # has no method 'setDockSide'
Uncaught TypeError: Object # has no method 'setAttachedWindow'
Uncaught TypeError: Object # has no method 'zoomFactor'

And I think that for Object # it means InspectorFrontendAPI. I hope this could help.

[kevinorin]

Been troubleshoothing this for way too long. Was working fine, yesterday stopped working so I updated all my Chrome versions on mobile and Macbook and still nothing. SG S3 Chrome version 34.0.1847.114 - It flickers a bit as if it's going to work then nothing.

[AzazelN28]

@paulirish Thanks.

[kevinorin]

But are both desktop + mobile on 34+? - I didn't check desktop version but I did update both to latest just to be sure and still doesn't work.

[timcooper]

The current Windows stable is 33 and Android 34. Windows dev channel is 35 and beta 34, does this mean we need to switch to Windows beta channel? Android Beta is a lower version than Android Stable. I'm struggling to find an easy reference for what version is current in which channel, there doesn't seem to be a clear list anywhere - having to hunt through http://googlechromereleases.blogspot.co.uk/ is a bit of a pain. Found http://omahaproxy.appspot.com/ too but it seems to be out of date, has android stable listed as v33 still.

update: Switching to Chrome Beta channel (currently at v34 which matches android stable) fixes the issue, this is going to keep cropping up though with differing stable releases though.

[MoritzGiessmann]

Thanks @paulirish. Chrome 36 (canary) and Chrome 34 on the mobile device works.

[elboletaire]

I cannot get it working using Windows 7 and the latest versions of google chrome for Windows (33.0.1750.154) and for Android (34.0.1847.114)...

[MoritzGiessmann]

Yup. That was my problem as well. Use at least Chrome 34 on your desktop.

[elboletaire]

I'm not gonna update my chrome to a beta version...

In fact, I think that this should be specified in the official documentation

[kurehajime]

@paulirish Thanks.

[bytesphere]

Thanks @timcooper, switched to Chrome Beta (34.0.1847.116) on OSX. Now remote inspect is working again with Nexus 4 and Chrome 34 stable.

[stroep]

@elboletaire You can have both the stable and the canary version installed on your machine. Works perfectly

[mgenev]

seems to happen when mobile chrome and desktop chrome are out of sync. Apparently version 34 auto-updated on my phone while desktop still had 33 and my dev tools stopped working.

Please fix guys

[paulirish]

Chrome desktop 34 just shipped yesterday. Update and you should be all set.

I apologize for the incompatibility between 33 and 34. We're going to try to avoid that in the future.

[marlencrabapple]

This is a bit of a problem for people using stable Linux distros. Chromium 34 hasn't been added to many repos yet.

[paulirish]

@timcooper Saw your comment then I think you deleted it? Is your Chrome stable on 35?

[timcooper]

Yes my bad, I did delete it. I'm having a one of those 4-30-5pm Friday everything going to hell type moments and my comment came across a bit angrier than I was intending.

It was also incorrect, the issue turned out to be the other problem where it just doesn't see the phone, I ran into it once before but I noticed the version mismatch before I realised and assumed it was that.

As before it was fixed by running adb usb - happy to report that I can debug android v34 from my desktop v35 now.

[hkongm]

@gockxml 牛逼！！

[scoleman2272]

I'm using Chrome V35.0.1916.141 on my mobile (kitkat), and V35.0.1916.153 on my mac and still get the blank screen - very frustrating!

[AdrianTP]

So I'm not clear on one thing here...if I cannot access the internet from my laptop, I cannot run the remote debugger's inspector against my phone's browser? I'm connected to a WiFi network which does not have internet access, and I am running a webserver on my laptop. I can access the website on my phone (which is connected to the same network as my laptop) and my laptop's Chrome lists my device and open tabs in the Inspect Devices page, yet clicking Inspect opens a blank window. I have the newest release of Chrome on both my phone and my laptop. I tried with both Windows and OS X.

[raytaylorlin]

@gockxml Thank you very much! Exactly the GFW!

[paulirish]

@AdrianTP the inspector gets cached in appcache after first request, so typically folks are fine. If you can't access internet on your laptop then we don't have a good solution for that right now.

[laosiaudi]

@gockxml seems not for my situation......It still opens an empty window when opening an Android-Crosswalk App, but succeeds when opening an Android-Cordova App

[jimmyxu0311]

I'm using Chrome V38.0.2125.102 on my mobile (kitkat), and v38.0.2125.101 m on my win7 and still get the blank screen - very frustrating!

[hkongm]

@jimmyxu0311 哥们，上面提到了，需要翻墙哦

[gooooloo]

@gockxml 你救了我

[Perlesvaus]

The same for me (W7 x64) address instead of title: chrome-devtools://devtools/bundled/devtools.html?&remoteFrontend=true&remoteFrontendUrl=chrome-devtools

[p2227]

@gockxml 除了翻墙真的没有其他方法了吗？其实访问那个网站是要什么信息，能不能本地搭建相关的服务器。

[juliogc]

I'm using Chrome 39.0.2171.71 and Chrome Canary 41.0.2243.0 in Mac OS 10.10.2 and still getting the blank screen in both.

[Perlesvaus]

juliogc, try to "revoke" the USB debugger inside Settings and re-pair it. Let me know if it works!

[juliogc]

Perlesvaus, in Canary back to normal, but in Chrome still blank.

[michalliu]

@gockxml Thank you
Debugging chrome browser is okay now, But I got a blank page when debugging webview on the same phone, xiaomi 3, why?

[keepeye]

i have the same problem.Even though i used shadowsocksx on osx,it is still so slow,it costs about 10 minutes when inspect one page

[vaenow]

@gockxml Thank you for saving my life!

[martin-s]

Any news on debugging webviews yet? I still recognize requests to "https://chrome-devtools-frontend.appspot.com/" which obviously are not going to work in an offline environment.

[paulirish]

@martin-s

Any news on debugging webviews yet?

Been working for a while! https://developer.chrome.com/devtools/docs/remote-debugging#debugging-webviews

I still recognize requests to "https://chrome-devtools-frontend.appspot.com/" which obviously are not going to work in an offline environment.

There's an appcache so after you access the files for the first time, the frontend will come from there. Works fine offline.

@rlynd3

Anyway to host the front-end "locally"?

There's a good new solution for that. http://sandipchitale.blogspot.com/2014/07/devtoolsapp-now-works-with-chrome-360.html offers a Chrome app where you can chose which frontend to attach to your debugging target. You can supply one locally or use another host.
cc @sandipchitale

[rosone]

I still recognize requests to "https://chrome-devtools-frontend.appspot.com/" which obviously are not going to work in an offline environment.

this is the answer.

after I connect America vpn, it works.

[bmwertman]

Just installed Chrome Canary Version 42.0.2283.5 on Mac OSX Yosemite 10.10.1 I'm getting the blank page when I click inspect device.

[landys]

Thanks, it solved my problem. :)

[qiushilee]

@mrzzcn Thank you very much!

[g8up]

能不能把 chrome-devtools-frontend.appspot.com 这个请求返回的 JSON 在本地搭建 http server + hosts 来模拟一下？

[jhilmar-sergio]

it is working with the default chrome (after install canary, I don't know wy)

[bguiz]

I'm still experiencing the same issue, on the current versions.

• Not working on Chromium 42 on Mac OSX
• Working on Chrome 43 on Mac OSX
• Working on Chromium 41 on Ubuntu Linux

Both using the same Android phone, using the same app (phonegap/ cordova)

appspot.com is not blocked for me.

[luke-j]

Can confirm this issue is still present for me.

• Not working on Chrome 43, Mac OSX.
• Working on Chome 45, Mac OS X.

Android device is up-to-date and appspot is not blocked.

[jcuenod]

Likewise not working:

• Chromium 43.0.2357.81 on FC22

[liuyanghejerry]

Thanks for the fix. It works for me.

43.0.2357.132 dev-m (64-bit)

[escapedcat]

omg @gockxml thx a bunch! that was fun... m(

Still had it with:

Version 44.0.2403.61 beta (64-bit)
Linux Mint 17

But after opening it one time using a VPN it seems to be fine after even without a VPN.

[1e0ng]

👍 @gockxml

[Tyguy7]

I have this issue as well. I'm shocked at how shoddy the chrome debugging tools are. I can't get them to work on Yosemite, or Windows 7, with either my android tablet OR my android phone.... real failures here Google.

[lifei]

@gockxml 作为身处墙内的大陆同胞，非常感谢。

[pallyoung]

@gockxml 墙内人民发来问候

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

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

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

[bmlyon]

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

[alexstanbury]

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.