Hello!
I would like to report a bug with the nRF Connect for VS Code extension.
My setup
- VS Code v1.98.0
- nRF Connect for VS Code Extension Pack v2024.9.5
- nRF Connect fo VS Code v2025.1.127
- nRF Connect SDK V2.9.0
- Ubuntu 22.04 LTS
Bug description
The bug is that after building a project, the extension can spontaneously change build configuration.
For example, I have two configurations. One for building the project for a nrf54l15dk and another for nrf52840dk.
I build both configurations. 2 build contexts appears for each configuration (mcuboot and application). I activate a certain context, I want to use (for example, the build_nrf54). Then I go to the Explorer tab and browse some files. After that, I go to the nRF Connect tab back again, and I see, that the build context is not what I selected (it can be build_nrf52->mcuboot or build_nrf52->zephyr_sysbuild_issue).
This means, that each time I want to build or flash my project, I need to check if it is the correct build context selected. And it is very annoying to work with more than one build configuration - you can accidentally build or flash not what you wanted in the first place.
To reproduce:
- Create more than two build configurations, each one with mcuboot as a bootloader
- Build both configurations
- Select a certaing build context and remember, what you have selected
- Go to the Explorer tab and open some files
- Go to the nRF Connect tab and check the selected build context
Expected behavior:
Active build context is the same, as you have selected in the step 3.
Actual behavior:
Active build context is not the same, as you have selected in the step 3.