Intellisense stops working when installing new nRF Connect for VS Code extension

[MaxRuben]

Intellisense in VS Code stops working after updating nRF Connect for VS Code to 2023.4.148 or 2023.4.179.

Downgrading the extension to 2023.2.56 and doing a pristine build it works again.

[JamesDougherty]

Still the same with v2023.7.129.

I'm pretty sure this is the change that broke it:

Intellisense works before building an application

The nRF Connect extension configures the C/C++ extension's IntelliSense context based on the active build configuration. When there was no active build configuration, the nRF Connect extension would previously leave the IntelliSense configuration blank, which caused a lot of errors in applications that were not built yet.

To provide a useful editing experience for C files ahead of the initial build, we have introduced a configuration that the IntelliSense engine can fall back to until the application is built for the first time. As the nRF Connect SDK's build system is completely dependent on the generated build output, some errors will still show up in the source files until the application is built, but most autocompletion and symbol location information should now be available.

[MaxRuben]

I have noticed that too. I think it might have to do with a setting in my vs code (perhaps for an extension) cause most people can't have this problem, right?

[JamesDougherty]

Hey Max - It you roll back to v2023.2.56, then it works fine. I would like to upgrade the extension, but it makes it difficult to develop when all you see are false errors. Hopefully they can provide a solution soon.

[MaxRuben]

Yes, I am using 2023.2.56, but still hope with every update that this has been fixed, but not yet, for me anyway. 

But as I said, everyone can't have this problem with the later releases because you really can't do any serious software development when this problem still exists...

[JamesDougherty]

Yeah, I agree and I'm in the same boat. I get my hopes up every time I see a new updated. Makes me wonder if there is something odd about my setup causing it, but I can't be certain.