VSCode Pristine Build changes from sysbuild to no sysbuild on generate failure

RE: VSCode Pristine Build changes from sysbuild to no sysbuild on generate failure

geoff — Wed, 21 Jan 2026 16:30:57 GMT

Thanks! Yeah I wasn't too worried about it, but just unfortunately confused me one too many times I figured It'd be good to report it!

RE: VSCode Pristine Build changes from sysbuild to no sysbuild on generate failure

Vidar Berg — Wed, 21 Jan 2026 10:40:21 GMT

Hello,

Thank you for reporting this. I can confirm that I’m seeing the same issue here, and it’s something that should be fixed. I’ll report this internally.

Best regards,

Vidar

Update: the extension team believe they have found a fix for this and will include it in the next release of the extension.

RE: VSCode Pristine Build changes from sysbuild to no sysbuild on generate failure

geoff — Tue, 20 Jan 2026 20:34:36 GMT

Hey!

This is selecting the build (so the whole config) and not an individual one. We have the app and mcuboot.

It only happens on first generation if there is a build error, so it's just a bug in detection given not all of the config is generated due to the error.

Just a weird issue I saw that caused me pain while trying to figure out mcuboot params.

If there is no error in the config, and the first generation completes successfully, then there is no issue.

Geoff

RE: VSCode Pristine Build changes from sysbuild to no sysbuild on generate failure

Turbo J — Tue, 20 Jan 2026 19:39:50 GMT

Check and compare the actually used build dirs.

VS code looves to compile the app (sub) project instead of the main sysbuild depending on which build folder was selected. Extremely annoying on the NRF5340 which always has at least the net core in the sysbuild active - you can't flash the partly build project onto the MCU properly, it usually crashes in Ozone.

The west flash command does not have this problem usually - but takes forever compared to flashing via Ozone.