VS Code was not detected on your system.

[AndreKR]

Well, clearly something is not right here. :)

How exactly does it try to "detect" VS Code?

I have now installed the Extension Pack from inside VS Code which worked without any issues.

[AndreKR]

Silly me, I just realized that of course the Toolchain Manager is open source, so it's easy to see that the "detection" actually just tries to run code --list-extensions. I confirmed with Process Monitor that this command is executed with an unmodified PATH, so VS Code would actually have to be in PATH. Since of course on my machine it is not, this mechanism will fail.

[ChrisInAtl]

I'm seeing the same symptom on my macos install of nRF Connect for Desktop, v3.12.0.

I've tried mucking around with the PATH to shorten (per the other comment below) and to try to make sure it is set somewhere fundamental to running processes like .zshenv.  No luck.

How did you view the PATH of the executing Toolchain Manager?  I'm unfamiliar with Process Monitor, is that the app by the same name in the App Store?  Thank you for any help.

[AndreKR]

Can you run the command code from a shell? Does it open VS Code? Then your PATH should be correct and the command that Toolchain Manager runs should succeed.

Process Monitor is a Windows thing, on MacOS you could try execsnoop.

[ChrisInAtl]

Yes, code works fine from the command line.  I've used that to launch VS Code for years.

I'll play around with execsnoop, though.  Thanks.