Skip to main content
migueld83371718
migueld83371718
Inspiring
July 4, 2019
Question

Extendscript debugger stopped working after a vscode update

  • July 4, 2019
  • 2 replies
  • 2145 views

Vscode has just been updated to v1.36.0 (on Windows 10) and the debugger has stopped working. I can not select a target engine in the debug bar and if I start a debug session, I don't see the alert to select a target engine. It seems that the debug session runs for a couple of seconds and stops without any apparent problem. I have rebooted Vscode, the hosts and the pc, but it's still the same. Is there any way to solve this?

This topic has been closed for replies.

2 replies

erinferinferinf
Adobe Employee
erinferinferinf
Adobe Employee
July 10, 2019

Hi Miguel, and everyone in the thread!

The engineering team released ExtendScript Debugger 1.1.2 this morning, and it's now available in the VSCode Marketplace. It ought to now run on Windows and VSCode 1.36. Please let us know if it doesn't!

Here's the Changelog for this version:

Fixed:

  • The extension breaks on Windows OS because of major electron and node version changes in Visual Studio Code Release 1.36.0.
  • Can't run debugger with Adobe Bridge.

Changed:

  • Minimum Visual Studio Code version required to run the extension is now 1.36.0.

Best,

Erin

    migueld83371718
    migueld83371718Author
    Inspiring
    July 10, 2019

    Great! Now it works on V1.36

    Thanks for the job

    erinferinferinf
    Adobe Employee
    erinferinferinf
    Adobe Employee
    July 6, 2019

    Hi Miguel,

    That's not great... It'd be helpful if anyone reading this who is having the same trouble could confirm the issue.

    VSCode 1.33 also broke things a bit, too, but fortunately we got a fast turnaround from the engineering team in India (less than 48 hours, if I remember correctly).

    Everyone on my team is on a week-long North American Adobe shutdown, so I didn't read your message until Friday night.   Hopefully we can get a new build or a patch early next week. When we do, I'll update you here.

    Best,

    Erin

    thba
    thba
    Participant
    July 7, 2019

    Hi Erin, hi Miguel,

    i encountered the exact same issue as Miguel after updating VS Code to 1.36 (June 2019) on two Windows 10 machines (running win 10 version 1903 (Build 18362.175).

    On macOS Mojave 10.14.4 with VS Code 1.36 there seem to be no problems with the ExtendScript Debugger.

    Cheers

    Thomas

    thba
    thba
    Participant
    July 7, 2019

    As a workaround, i downgraded to VS Code 1.35.1 and everything worked again.

    You can download the older version at May 2019 (version 1.35) (I chose the "Windows" "User" version) and simply install it after you uninstalled 1.36.

    Be sure to un-check option "Enable Windows Background Updates" in VS Code right after installing 1.35.1 (to do so, click "File" -> "Preferences" -> "Settings", then go to "User" -> "Application -> "Update"

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices