• State Not Answered
  • Replies 12 replies
  • Subscribers 71 subscribers
  • Views 886 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 327176
Options

Always "The build configuration is stale. Run a pristine build" in newer versions of nrf connect for vs code

Maos

hi!

I get the message "The build configuration is stale. Run a pristine build" even after rebuilding in all versions of nrf connect for vs code after 2023.7.129.

I have tried to remove the workspace and start over but the problem is still there.

I also tried the 2024.5.37 pre-release version to see if the problem is still there.

I tested create a new application based on the "hello world" sample with the same result.

As soon as I switch back to 2023.7.129 the source folder/files show up as expected.

BR,
Mårten

Parents
  • 0

    Same problem this morning, chasing this issue now for a couple of hours. vscode crashed during some editing, after restarting vscode I got stuck with this ""The build configuration is stale. Run a pristine build" issue. After cleaning caches and build directories for some time I stumbled across the fact that the "nRF Connect for VS Code" extensions has been auto-updated to "Version 2024.11.22" and likely got active at the vscode restart. Issue seems related to that vscode now determines that something changed during the build and always considers the build stale. Forcing the extension back to "Version 2024.9.31" solves my problem.

    I have these two config variables in my prj.conf:

    CONFIG_SOC_NRF52832_ALLOW_SPIM_DESPITE_PAN_58=y
    CONFIG_NRFX_PPI=y
    Extensions "Version 2024.11.22" emits a warning that these two config options changes to "n" during the build, which I believe is false. At least there is no sign in build output that this would be the case and the working version of the extension "Version 2024.9.31" does not detect this either. I'm just guessing this might be the reason why this "The build configuration is stale. Run a pristine build" appears all the time.
    I really don't understand why defaults in this environment is set to auto-update, who actually wants a development environment that self-updates silently in the back throwing the developer into new issue like this? This is really frustrating and non-productive.
Reply
  • 0

    Same problem this morning, chasing this issue now for a couple of hours. vscode crashed during some editing, after restarting vscode I got stuck with this ""The build configuration is stale. Run a pristine build" issue. After cleaning caches and build directories for some time I stumbled across the fact that the "nRF Connect for VS Code" extensions has been auto-updated to "Version 2024.11.22" and likely got active at the vscode restart. Issue seems related to that vscode now determines that something changed during the build and always considers the build stale. Forcing the extension back to "Version 2024.9.31" solves my problem.

    I have these two config variables in my prj.conf:

    CONFIG_SOC_NRF52832_ALLOW_SPIM_DESPITE_PAN_58=y
    CONFIG_NRFX_PPI=y
    Extensions "Version 2024.11.22" emits a warning that these two config options changes to "n" during the build, which I believe is false. At least there is no sign in build output that this would be the case and the working version of the extension "Version 2024.9.31" does not detect this either. I'm just guessing this might be the reason why this "The build configuration is stale. Run a pristine build" appears all the time.
    I really don't understand why defaults in this environment is set to auto-update, who actually wants a development environment that self-updates silently in the back throwing the developer into new issue like this? This is really frustrating and non-productive.
Children
Related