Debug via extension broken with VSCode 1.20

[andreaboriani]

Cannot run "Launch on android" nor "Attach on Android" after updating Visual Studio Code to version 1.2ù
Any workaround?

[cfirmo33]

waiting for this correction too.

[EddyVerbruggen]

Wondering if this is Windows-only.

Does anyone see this on macOS? I'm running VSCode 1.2 on macOS and extension version 0.7.2 and can attach/launch on Android just fine.

[NickIliev]

@EddyVerbruggen I've experienced this one on macOS as well.
However, the issue is not consistent on Mac while on Windows it is 100% reproducible

[EddyVerbruggen]

Hmm, macOS is rock solid for me (and I don't currently have a Windows machine at hand). For anyone experiencing this issue: I wonder if it would help if you change this in launch.json:

        {
            "name": "Launch on Android",
            "type": "nativescript",
            "request": "launch",
            "platform": "android",
            "appRoot": "${workspaceRoot}",
            "sourceMaps": true,
            "watch": true,
        },

to

        {
            "name": "Launch on Android",
            "tnsArgs": [
                "--debug-brk"
            ],
            "type": "nativescript",
            "request": "launch",
            "platform": "android",
            "appRoot": "${workspaceRoot}",
            "sourceMaps": true,
            "watch": true,
        },

so add that tnsArgs bit.

And if that works (the debugger should stop at the first NativeScript line that's executed), then please also test --debug instead of --debug-brk.

[tedekeroth]

Hey,
running win7, Vscode 1.20.1. Tried both --debug-brk and --debug, no change for me at least.

[andreaboriani]

Just to clarify, the problem is not debugging.
When you click 'Launch on Android' nothing happens. The debug console window remains empty, with no [NSDebugAdapter] nor [NativeScriptCli] shown.

[EddyVerbruggen]

Thanks for the feedback! Knowing that adding --debug(-brk) didn't help made me install a virtual Windows machine on my Mac to reproduce this issue myself.

After some fooling around in the codebase and trying to wrap my head around how the debugger server and client communicate (sockets, in this case) I found the issue and a solution... so expect a PR real soon.

[EddyVerbruggen]

⬆️ PR pending 🎉

[thaoula]

That is great news!!! When can we expect the PR to merged?

Currently debugging with the Chrome Dev tools is not an awesome experience.

[thaoula]

When will a new version of the Nativescript extension with theses fixes be pushed out?