Cannot debug extension (unknown request 'launchVSCode').

[HelloXZX]

• VSCode Version: 1.30.2
• OS Version: MacOS 10.14.2

Steps to Reproduce:

1. Create a new own extension.
2. Debug the extension. Toast 'Cannot debug extension (unknown request 'launchVSCode').'

Does this issue occur when all extensions are disabled?: Yes

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Add code action for unknown debug types (#55742)

[ludorival]

I got also the same issue with similar environment
VSCode Version: 1.30.2
OS Version: MacOS 10.14.1

Try to uninstall and install Vscode and still the same.

Please look at this issue with attention, I cannot debug my extension which is very annoying.

Best,
Ludovic

[weinand]

The error message indicates that you are using the node-debug version from the Insiders release which isn't compatible with VS Code Stable 1.30.2.

What version of node-debug are you using?
It should be 1.30.3:

@roblourens could you please set node-debugs's vscode engine version to 1.31.0.

[ludorival]

Thanks @weinand.
My node debug version is 1.31.3.
Can I set the correct version on my side ?

[ludorival]

Forget it I see where

[ludorival]

Thanks @weinand , your workaround works for me, but I had to disable the auto updating extensions to not have the latest version.

[roblourens]

Done. @ludorival does ~/.vscode/extensions/ms-vscode.node-debug2-1.31.3 exist? Don't know how that would have happened...

[weinand]

@roblourens there seems to be a bug in automatic extension updates: built-in extensions should not be automatically upgraded.

@sandy081 how could that happen?

[ludorival]

@roblourens yes it exits for me.

[daimor]

Faced the same issue, in my case I also had ms-vscode.node-debug2 version 1.31.3
Installing some previous version was not available, while 1.31.0 not listed
install previous version when failed offered to download and install manually
manual install failed due to dependencies from React Native Tools
After removing this extension, I managed to install previous version of Node debug. After reload debug extensions finally started to work. And Node Debug extension disappeared from @installed but visible in @Builtin as version 1.30.4

So, looks like an error because solving extensionDependencies for built-in extensions.

"extensionDependencies": [
		"ms-vscode.node-debug2"
	]

vscode-react-native

[alexeyvax]

Hi everyone!
I have the same issue.

• VSCode Version: 1.30.2
• OS Version: Linux x64 4.15.0-43-generic

Something broken on node debug 1.31.3 version. Extension doesn't launch.
But when I rolled back to node debug 1.31.2 version. Extension launched as expected.

[weinand]

@alexeyvax when using VSCode Version: 1.30.2 you should not be able use a "node debug 1.31.3".

Did you use a manually installed version of "node debug" before this happened?

[alexeyvax]

hmm... It's strange. I don't use manually installed packages, only automatically installed.
Here my extensions list:

If I try to launch my extension, I'll get error(this issue), but if I use node debug 1.31.2, my extension will launch as expected.

[abdel-ships-it]

Downgrading to 1.30.0 as @weinand advised fixed it for me!

[wongjiahau]

Downgrading Node Debug to 1.31.2 works for me.

[humeSnail]

this one is ok.

[roblourens]

@sandy081 "Install another version" should be disabled for builtin extensions.

Did anybody use that feature originally? I think we still don't understand how a new version of the extension ended up installed for you in the first place.

[sandy081]

@roblourens I do not see this action enabled for built in extensions unless if users manage to install it and make it user extension.

[roblourens]

I see it enabled for "node debug" but not "node debug (legacy)"...

[sandy081]

I do not see it for either of the extensions. Can you check if you have it in user extensions folder?

[roblourens]

I'm confused, now I am not seeing it enabled for either.

[roblourens]

You should delete the extension from ~/.vscode/extensions/ms-vscode.node-debug2...

[akrantz]

@roblourens OK, that fixed it for me. Thanks.

[sandy081]

Those who are seeing this error, is it possible to let us know if you have installed the node debug extension manually by getting it from marketplace directly or through a VSIX?

[daimor]

got this error without manual installing this debug extensions, now or any time ago.
After uninstalling some of extensions, and reload I got it worked, without manual installing previous version.

[akrantz]

I did not do anything manually to get the extension. I think it got installed indirectly somehow.

[sandy081]

Strange, May I know if you have an extension installed that sync extensions for eg., Sync Settings extension?

[sandy081]

Only way this can happen is to either

• Manually install the extension using VSIX or from Command Line or
• If there exists an extension that installs it for synchronising extensions for example.

I can block the CLI and have only VSIX way

[akrantz]

I don't have any extensions installed that sync extensions.

[brandondrew]

@sandy081 I can second what @daimor said: I didn't install this manually, but it seems to have been a dependency of React Native Tools (vsmobile.vscode-react-native). I disabled React Native Tools in order to remove the offending version of Node Debug.

[sandy081]

We are planning to implement updates for built in extensions which can fix all such reported behaviours - #68410

[sandy081]

Please let me know if users are still facing this issue? As mentioned, I see this can happen only if built in extension got installed manually or by another extension. So I would close this issue as I do not have any plan of action. It would be great if someone who repro this can provide steps.