VS Code Having Trouble With Project Created From Asset Tracker Version 2 Sample

RE: VS Code Having Trouble With Project Created From Asset Tracker Version 2 Sample

Jared — Thu, 14 Oct 2021 08:24:30 GMT

Hi,

I don't think this issue is directly related to the VS code extension but maybe is a more general VS code issue, so consider posting this issue at a VS code forum or similar. Have you made sure that all relevant paths are included in c_cpp_properties.json ?

regards

Jared

RE: VS Code Having Trouble With Project Created From Asset Tracker Version 2 Sample

Zeedel — Wed, 13 Oct 2021 13:16:03 GMT

Hi Jared,

Thanks for taking a look. I tried the following:
- CMD + Click - A message shows saying: "cannot open source file "../certs/DSTRootCA-X3.pem"C/C++(1696)"
- Right Click and selecting "Go To Definition" - A message shows saying: "No definition found for XXXX"

XXXX in the second point above differs with where in the line you click, but generally maps to the word clicked on, e.g. 'include' and 'certs'.

However, building seems to work fine.

RE: VS Code Having Trouble With Project Created From Asset Tracker Version 2 Sample

Jared — Wed, 13 Oct 2021 12:38:11 GMT

Hi,

What happens if you right click the #include statement and press "Go to definition". Is it able to find the file?

regards

Jared

RE: VS Code Having Trouble With Project Created From Asset Tracker Version 2 Sample

DamoL — Tue, 12 Oct 2021 16:10:32 GMT

I also find the same issue with some functions. Mainly the logging functions that don't have any placeholders. When I added in a %d in a string within the LOG_INF() function and just a null char the error was gone, quite annoying to do that in every part of the project though. Hoping there is a simple fix.