nRF Extension on VScode doesn't doesn't bring compiler errors to PROBLEMS tab

[Dmitry Kr]

Hi, 

Why nRF Extension on VScode doesn't doesn't bring compiler errors to PROBLEMS tab? The issue appears few days ago, reinstalling of extension and vscode at all doesn't help.

PROBLEMS tab imports some issues on IntelliSense output ("online") but doesn't import compiler output as it should. 

Used nCS 2.0.0, toolchain manager was updated to ver. 1.1.3 , nRF Extension was re-installed today.

[Voxar]

Hi! This thread was the first hit when I searched the same issue so I want to let you know that I found a solution in another thread. 

I added a .vscode/tasks.json file 

{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "nrf-connect-build",
      "config": "${activeConfig}",
      "runCmake": false,
      "clean": false,
      "problemMatcher": [
        "$gcc",
        "$cmake",
        "$kconfig",
        "$kconfig_syntax",
        "$kconfig_syntax_files",
        "$dts",
        "$dts_syntax",
        {
          "fileLocation": "absolute",
          "pattern": [
            {
              "file": 1,
              "line": 2,
              "column": 3,
              "message": 4,
              "regexp": "^\\s*(.+):(\\d+):(\\d*):?\\s(.+)$"
            }
          ]
        }
      ],
      "group": "build",
      "label": "nRF Connect: Custom Task: build (active)"
    }
  ]
}

The secret is supposed to be putting `$gcc` at the top of the list of problemMatcher. 

I had to add the custom matcher to get "undefined reference" errors to show up. 

[Marko W]

I added tasks.json in the existing empty .vscode folder but it didn't bring any improvement. No warnings are displayed from the "nRF Connect" terminal!