cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BAS | Business Application Studio Debugger not working or not attaching

jbibal-pdc
Explorer
4,628

Hi,

As of last night, something weird happened to the SAP Business Application Studio.

The debugger no longer attaches to the debug configurations that I have created:

{
  "version": "0.2.0",
  "configurations": [
    {
      "command": "cds serve --with-mocks --in-memory?",
      "name": "cds serve",
      "request": "launch",
      "type": "node-terminal",
      "skipFiles": [
        "<node_internals>/**"
      ]
    },
    {
      "command": "cds watch --with-mocks --in-memory?",
      "name": "cds watch",
      "request": "launch",
      "type": "node-terminal",
      "skipFiles": [
        "<node_internals>/**"
      ]
    }
  ]
}

My breakpoints are now always "unbound" and the "WATCH" and "CALL STACK" Sections are also empty

Additionally, the terminal now shows as "openvscode-server$":

Before, it used to show the name of the folder / workspace, ie. like "test$":

This problem started around 12-14 hours ago. Was there any updates applied to SAP BAS?
Hoping for any assistance.

Thanks,

John

View Entire Topic
sanjothomas
Discoverer
0 Kudos

I was able to solve it, by first starting cds run in debug mode and then selecting Debug: Attach to Node Process in the command pallate.

jbibal-pdc
Explorer

Hi Sanjo,

This was actually my initial workaround as well, but didn't find it sustainable when using cds watch, as running it automatically redeploys / restarts the CAP server for any new code change.

This creates a new node process that you need to attach again and again; but sometimes it won't attach at all.

So hopefully you were able to make Liat's or Licam's suggestions to work.

Thanks,
John