Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Scripting with VSCode ExtendScript Debugger - Breakpoints don't hit

New Here ,
Jul 12, 2022 Jul 12, 2022

I'm on a Mac using Mojave 10.14.6, trying to write some Scripts for InDesign. I can't get the VSCode ExtendScript Debugger to react to any of the breakpoints I set in any script, though my scripts do run as expected and work. I also have the "old" ExtendScript Toolkit installed and breakpoints work there. I have tried setting the debug level, and also using $.bp() in my scripts, still, I can't get VSCode to break on my breakpoints. I'm using version 2.0.2 of the ExtendScript Debugger and everthing worked fine for me a few weeks ago.

 

Here's an example script (named test.jsx) I was using to test this problem adapted from this answer :

var doc = app.activeDocument;
var test_number = 1;
var textFrame = doc.pages[0].textFrames.add();
if (test_number == 1) {
    $.bp()
    textFrame.properties =
    {
        geometricBounds : [ 0,0,100,100 ],
        strokeWidth : 0,
        fillColor : "None",
        contents : "Hello World!"
    };
} else {
    textFrame.properties =
    {
        geometricBounds : [ 0,0,100,100 ],
        strokeWidth : 0,
        fillColor : "None",
        contents : "Hello Mars!"
    };
}

This is my launch file for the VSCode Debugger:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [

        {
            "type": "extendscript-debug",
            "request": "launch",
            "name": "Launch my Script",
            "script": "${workspaceFolder}/test.jsx",
            "hostAppSpecifier": "indesign-16.064",
            "engineName": "com.adobe.ccx.sharesheet.dialog_Engine_Id",
            "debugLevel": 2,
        }
    ]
}

The problem first occured yesterday and I have been trying to figure out what's wrong for hours.

I would be very happy if anyone could offer suggestions on how to fix this. I would also like to know where/ how I can submit a bug report for the VSCode Debugger. Thank you for reading!

TOPICS
Bug , Scripting
934
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , Jul 12, 2022 Jul 12, 2022

I uninstalled the ExtendScript Debugger plugin in VS Code and uninstalled VS Code with AppCleaner . Then I did a fresh install with the most recent version of VS Code and added the ExtendScript Debugger plugin and finally debugging works as expected again! I tested it on several different Indesign Scripts.

I still don't know what went wrong but I am glad doing a completely fresh install worked.

Translate
New Here ,
Jul 12, 2022 Jul 12, 2022
LATEST

I uninstalled the ExtendScript Debugger plugin in VS Code and uninstalled VS Code with AppCleaner . Then I did a fresh install with the most recent version of VS Code and added the ExtendScript Debugger plugin and finally debugging works as expected again! I tested it on several different Indesign Scripts.

I still don't know what went wrong but I am glad doing a completely fresh install worked.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines