Chrome remote debugging: empty inspect tab
Asked Answered
B

11

34

I'm using Google Chrome v35.0.1916.114 and followed the steps to enable remote debugging on my Samsung Trend Plus GT-S7580 which runs Chrome v35.0.1916.122.

I can effectively view the opened tabs, close them and all, but inspecting a tab gives me a blank console.

Any reason why it doesn't work?

Burk answered 28/5, 2014 at 14:0 Comment(0)
N
26

I have faced same problem. In my case I have found that version of chrome browser on windows system was 44.x but on android mobile device has 54.x. I just updated my windows chrome. And everything started working fine.

Nowak answered 28/10, 2016 at 6:22 Comment(3)
It was a great help!Skippy
Same problem... device was version 65 and computer was version 64. Updated the computer and it started working.Gonion
This turned out to be true for me, even though it was only a very minor version difference, 94.0.4606.72 v. 94.0.4606.76. On the Android side, I had to specifically go to the app manager in Settings and tap Updates Available; just going to the Chrome app in Google Play did not work.Holman
P
13

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, that's why you're getting an empty window. In this case, maybe you need a VPN.

Pakistan answered 14/4, 2015 at 6:18 Comment(0)
E
5

I had the crasiest workaround:

Press CTRL+SHIFT+I, which opens a new developer tool for the developer tool. Go to console and run: window.location.reload()

This reloads the first developer window and attaches to the original process.

Einhorn answered 27/5, 2016 at 13:36 Comment(2)
Didn't need a new Developer Tool, simply the reload fixed it. Thanks for that!Selfsealing
This is probably the same as clicking the reload icon which looks like a circular arrow. Did not help in my case :-(Nautch
M
2

I have the problem even with Chrome 46, here is my workaround...

On the blank/empty Dev Tools window press 'Ctr+Shift+i'. This opens a 2nd Dev Tools window. You will see an error in the console “Uncaught TypeError: Cannot read property 'addExtensions'” and on the right one of these 2 links :

A) "VM45:72" => bad luck. Close 2nd window and try again.

B) "(program):72" => that’s it. click on the link "(program):72" and the 1st debug window will work again !

It may take one to 10 times before the "(program):72" appears

Mufti answered 1/12, 2015 at 8:35 Comment(0)
A
2

Check with desktop chrome 1) Goto help => About Google Chrome

Check with version number

Check with Mobile Chrome go to Help & feedback 1) right side option => version info

Check with version number

If both are same ... Remote device debugging will work

Atonic answered 20/3, 2018 at 16:26 Comment(0)
M
2

Ignore blank page and first visit

http://localhost:9222/json

then check devtoolsFrontendUrl from the JSON and go to

http://localhost:9222/

I wrote a post about how to setup Chrome Remote Debugging which covers this fix https://devforth.io/blog/chrome-remote-debugging/

Monamonachal answered 16/2 at 10:57 Comment(0)
A
1

Try using chrome Version 37.0.2041.4 canary or latest on your computer. I just had the same issue with the version you have but installed the latest canary and got it working. Hope that helps.

Alvy answered 10/6, 2014 at 15:58 Comment(0)
A
1

open chrome://appcache-internals/ and clear the manifest cache , then reload the resource

Arras answered 2/7, 2018 at 11:52 Comment(2)
When I go there, I see: Application Cache Instances in: ~/.config/google-chrome/Default/Storage/ext/longalphastring/def (0) Instances in: ~/.config/google-chrome/Default/Storage/ext/longalphastring/def (0) Instances in: ~/.config/google-chrome/Default (0) What is the manifest cache, how is it cleared, and what resource do you mean?Holman
404 - seems they've since removed it :/Westernmost
L
1

No cross browsing !

Jumping in quite late here, just had a similar issue. Turns out, in my case, I was using Chrome on my computer and Brave on my cellphone. Important to note that Chrome will allow to inspect Chrome!

Lannielanning answered 22/7, 2019 at 15:15 Comment(0)
T
0

In my case it was enabled proxy settings

Teetotalism answered 16/10, 2018 at 4:25 Comment(0)
N
0

In my case, I can remotely focus and close tabs on the mobile Chrome that were opened directly on the phone. I can also "inspect" those, with a nice screencast on the dev pc.

What does not work is entering a URL on the dev pc and click Open. That new URL is added to the list of tabs on the dev pc, but is not really opened on the phone. The Inspect button on that tab does not show a screencast, or just the blank one that OP asked about.

The solution is to enter the desired URL directly on the phone, then select that tab remotely on the dev pc to get a nice screen cast and debuggin situation.

Nautch answered 24/8, 2019 at 17:18 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.