Vscode-php-debug: Version 1.12.0 seems to have broken Debugging

[mwidmann]

I've been debugging in VSCode this morning, but since launch break the Debugger doesn't work anymore. Doesn't matter if I try to debug using the local php installation (7.1.1) or a remote one inside a Docker container, starting the debugger throws a "Debug adapter process has terminated unexpectedly".

There's no information in any of the output channels or the debug console. The error on the Console does not give any further information either.

my launch.json has not yet been updated to the newest Code workspace settings, but as I said, it worked this morning.

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Local auf Port 9001",
      "type": "php",
      "request": "launch",
      "port": 9001,
      "log": false
    },
    {
      "name": "Launch currently open script",
      "type": "php",
      "request": "launch",
      "program": "${file}",
      "cwd": "${fileDirname}",
      "port": 9000
    },
    {
      "name": "Listen for XDebug in Docker Webserver Container (OVB)",
      "type": "php",
      "request": "launch",
      "port": 9000,
      "serverSourceRoot": "/var/www/wordpress-custom/ovb/wp-content",
      "localSourceRoot": "${workspaceFolder}/wp-content",
      "log": false
    },
    {
      "name": "Listen for XDebug in Docker Webserver Container (VN,...)",
      "type": "php",
      "request": "launch",
      "port": 9000,
      "serverSourceRoot": "/var/www/wordpress-custom/webpapers/wp-content",
      "localSourceRoot": "${workspaceRoot}/wordpress-custom/wp-content",
      "log": false
    },
    {
      "name": "Listen for XDebug in Importer Docker Container (OVB)",
      "type": "php",
      "request": "launch",
      "port": 9000,
      "serverSourceRoot": "/opt/app-root/src/wordpress-custom/ovb/wp-content",
      "localSourceRoot": "${workspaceRoot}/wp-content",
      "log": false
    },
    {
      "name": "PHPUnit",
      "type": "php",
      "request": "launch",
      "port": 9001,
      "program": "/usr/local/bin/phpunit",
      "cwd": "${workspaceRoot}",
      "args": ["${file}", "-c", "${fileDirname}/../../phpunit.xml"]
    }
  ]
}

Using Code 1.18.1 on macOS 10.12.6 Sierra

[mixman68]

Same issue here

[rabbit-93]

Same here

[Qocotzxin]

Same issue here

[vitorsemeano]

The same is happening here. Early this morning it was working, then after the recent update, it does not work, even after a restart of the system.

[piqoni]

Same Issue

[Zeph33]

Same Issue :(

[mwidmann]

@stereoit posted the following workaround

from this page https://github.com/felixfbecker/vscode-php-debug/releases/tag/v1.11.1 download the 1.11.1, uninstall the 1.12 extension from VCSode, disable extension autoupdate "extensions.autoUpdate": false," open extension panel, install from VSIX, locate the 1.11.1.vsicx file, install

[Zeph33]

Only node_modules and image folders in v1.12.0
no source, no folder out

[Qocotzxin]

@mwidmann solutions works great. Hope they fix the issue with 1.12

[Zeph33]

maybe this change ... replace compile by build in package.json
https://github.com/felixfbecker/vscode-php-debug/commit/a8e61435b07cca6aecd9ea88f2cee9a176321695#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

[mrbianchi]

same error, hours wasted trying fixed it , finally I tried with 1.11.1 and no problems

[DekiChan]

Same error. Happened on three machines running Windows 10 Pro, on one of the VS Code installations there were no other extensions except PHP Debug.

Reverting the version to 1.11.1 works as expected.

[anibalsanchez]

Confirmed.

I have disabled "extensions.autoUpdate", uninstalled 1.12, installed https://github.com/felixfbecker/vscode-php-debug/releases/download/v1.11.1/php-debug-1.11.1.vsix from the Extension Manager and it works again.

[camflan]

Same

[efcribeiro]

Same

[jmperro]

Please revert the update v1.12 and put again the v1.11.1

[lmarcelocc]

Same here. Reverting to 1.11 works fine.

[YLivay]

Works in 1.12.1 - thanks for the quick fix :D

[felixfbecker]

I apologise for the inconvenience. I automated the release process yesterday night but forgot the build step in the release stage.

[felixfbecker]

Also just added automatic uploads of vsix files as part of the release process. Seems to have helped a lot of folks today keep working despite the technical difficulties :)

[mixman68]

Thanks you very much for quick fix

Le 21 nov. 2017 à 21:17, Felix Becker [e-mail] a écrit :

Also just added automatic uploads of vsix files as part of the release process. Seems to have helped a lot of folks today keep working despite the technical difficulties :)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[efcribeiro]

Thanks Felix! It’s perfect.

[troyporter]

Yeah definitely an issue with 1.12. Installed 1.11 and issue was resolved. instantly.

Debian Jessie