-
-
Notifications
You must be signed in to change notification settings - Fork 197
Android debugger failure - Debugging connection was closed. Reason WebSocket disconnected #2542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey @alexziskind1! Can you please verify that you are using the android 2.5 runtime. Thanks! |
Hi @Pip3r4o 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: Alex |
Here is the same thing happening with the built in Android emulator: Alex |
@alexziskind1 I've tested the debugger on both current stable 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. |
Thanks! Problem solved! 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. Thanks! |
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 Could somebody help me? |
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. |
@DannyFeliz Thanks for the response. |
Having the same issue. Genymotion 2.8.1. Chrome v. 56.0.2924.87. All extensions are disabled. Any updates on that? |
same issue guys ? All extensions are disabled ! |
@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. |
Here is the info you requested:
Web Store,
BUILD SUCCESSFUL Total time: 57.674 secs Using /Users/user/Documents/dev/NativeScript/hello-world-ts/platforms/android/build/outputs/apk/helloworldts-debug.apk NativeScript Debugger startedTo start debugging, open the following URL in Chrome: Executing before-watch hook from /Users/user/Documents/dev/NativeScript/hello-world-ts/hooks/before-watch/nativescript-dev-typescript.js 05-01 04:45:49.042 2626 2626 I TNS.Native: NativeScript Runtime Version 2.5.0, commit 95dd12d69eba88755158987d8c4666a9c5aa5e07 |
With regards to device, same happens when ran on a real device. |
@terreb I would ask you to disable/remove the |
@Pip3r4o Thank you for your prompt reply and actually for the help:) It works now! Feeling myself dumb now. I've already tried to disable all the extensions before, but it didn't work for me. This time I disabled the extensions closed and opened Chrome again, made sure they are still disabled, only then tried and bingo. Many thanks again! |
@Pip3r4o May I ask you another related question here, please? I read you guys want to get rid of Safari based NativeScript inspector and switch completely to Chrome web-tools for both platforms (please correct me if I'm wrong). But the thing is debugging in Safari based inspector is much more convenient now rather than in Chrome web-tools in the current state, since the latter is not much different from Node inspector. The former shows more info in the console like function or event name. It allows to expand and collapse objects. Honestly so far, I don't see any upgrades over Node inspector. Probably this is my first impression and I haven't discovered hidden gems. |
@terreb We have no plans to replace the Safari Web Inspector for iOS debugging until we can ensure that the Chrome counterpart can provide all functionalities available in Safari. As for the android debugging experience - we made the switch from the old Node inspector just recently (version 2.5), and have since made many improvements to stabilize it and make it as useful as possible. Version 3.0 will also feature showing of the network requests, allow previewing of all files in the app being debugged, support for the missing Variables tab, and more bug fixes. Very little of that was possible with the now old Node inspector, so the move to Chrome DevTools was the logical thing to do. |
Ok got it. Will be toying with the version 3 then. Thank you guys for all your hard work! |
I was facing the same issue. In short, creating a new profile on Chrome (People -> Add Person) and debugging from the person fixed the problem for me. I tried to invalidate ALL extensions from my primary profile then rebooted the machine, but nothing changed. Btw when the error was happening, logcat was showing the following error repeatedly forever even after closing the debug tab in chrome. Hope it helps identifying the issue.
Other version stuff when the problem was occuring:
package.json
Chrome version
|
@Liooo the adb logcat error you've been seeing is the socket connection from/to the chrome devtools being interrupted abruptly (by means of restarting the application, or sometimes when the chrome devtools tab is closed). |
@Pip3r4o Probably was missing the time axis
So I didn't restart the application nor closed the tab. |
I am also facing the same issue, any pointers previously with tns version 3.1.3 it wad working. |
@VimalKumarS how and when does the issue occur? In order for us to try and help you, we need a bit more than what you've provided. What browser are you using? chrome://version/ |
I have exactly the same problem as here described |
@NishanChakma @usmanghanidev have you fixed it yet? |
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
The text was updated successfully, but these errors were encountered: