Android debugger failure - Debugging connection was closed. Reason WebSocket disconnected

[alexziskind1]

I am attempting to debug an Android hello world app using chrome at the address specified by the CLI
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=localhost:40000

I'm getting the error in the title show up in Chrome and the message "Unfortunately, has stopped" alert in the Android UI.
There are no console errors.

I've tried this on 2 Macs and 1 Windows machine with the same results.
I've tried this with CLI version 2.5.0 and with CLI 3.0.0-2017-02-09-7977

Android emulator via Genymotion as well as built in emulator are having the same issue

[petekanev]

Hey @alexziskind1!

Can you please verify that you are using the android 2.5 runtime.

Thanks!

[alexziskind1]

Hi @Pip3r4o
Yes this was tested with 2.5.0 AND the @next version (3.0.0-2017-02-09-7977)

I've created a short video of me creating a project with 2.5.0 and then trying to debug with Chrome and Genymotion Android:

https://youtu.be/wpv5P4-DL4M

Alex

[alexziskind1]

Here is the same thing happening with the built in Android emulator:

https://youtu.be/qKZVah6uE9Q

Alex

[petekanev]

@alexziskind1
What version of Chrome are you using?

I've tested the debugger on both current stable Version 56.0.2924.87, as well as on Canary Version 58.0.3010.0 canary (64-bit)

I also noticed that you have DevTools extensions installed. Could you verify that no Chrome extension modifies the DevTools experience, runs a script on page load, etc. to try to narrow down the possible causes.

Additionally it'd be great if you could provide a logcat log, see if we can find anything useful there.
adb logcat -d > log.txt

[alexziskind1]

Thanks! Problem solved!
React Developer Tools Extension was causing this problem.

Chrome version is Version 56.0.2924.87 (64-bit)

I've turned off and on all the extensions one at a time and the one that was causing the problem is React Developer Tools.
I've also repeated this on the Windows machine and the same problem was solved there as well.

Thanks!

[Liooo]

Having the same issue. chrome version and android runtime version are the same as above, and cli version is 2.5.1. Turned off all chrome extensions, but still getting the error.

Here's the output of adb logcat -d
log.txt

Could somebody help me?

[DannyFeliz]

I had the same issue and as @Pip3r4o said an extension could causing the issue, in my case was Vuejs devtools, I just disabled it and everything works like a charm.

[Liooo]

@DannyFeliz Thanks for the response.
But as I mentioned, I turned off all chrome extensions but still getting this error..

[terreb]

Having the same issue. Genymotion 2.8.1. Chrome v. 56.0.2924.87. All extensions are disabled. Any updates on that?

[AbdallahBedir]

same issue guys ? All extensions are disabled !

[petekanev]

@AbdallahBedir @terreb Unfortunately this crash isn't something that we can reproduce, so we can't help unless you provide more information about your setup.
What versions are you using?
What browser are you using? chrome://version/
What are your installed extensions?
What device is the app being ran on?
Is it a hello-world tns app?
What is the console log?
What's in the adb logcat at the time of the application crash? adb logcat