Since upgrading to version 2023.4.148, I am unable to select a local nrf-connect.topdir.
When I come back to version 2023.2.56, it works.
This is a bug in version 2023.4.148.
Context:
VSCode
Version: 1.77.3 (Universal)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:19:37.325Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin x64 19.6.0
Sandboxed: Yes
nRF Connect for VS Code 2023.4.148 (or 2023.4.179)
To reproduce:
- copy /opt/nordic/ncs/v2.1.3 to XXX/v2.1.3 (XXX being somewhere in your user folder)
- Open VSCode/nRF Connect :
- Open Welcome Page
- "nRF Connect SDK" => Browse
- select XXX/v2.1.3
- close Welcome Page
- open Welcome Page
- the nRF Connect SDK is back to "/opt/nordic/ncs/v2.1.3"
When checking the workspace settings file, one can notice that the nrf-connect.topdir is not set to XXX/v2.1.3 indeed, but to ${nrf-connect.sdk:2.1.3}.
{
"folders": [
{
"name": "xxx",
"path": "xxx"
}
],
"settings": {
"nrf-connect.toolchain.path": "${nrf-connect.toolchain:2.1.3}",
"nrf-connect.topdir": "${nrf-connect.sdk:2.1.3}",
"git.ignoreLimitWarning": true,
"nrf-connect.applications": [
"${workspaceFolder}"
]
}
}
This is problem when working on a local variation an nRF SDK for example, which is my case.
