80 results found

1. Illustrator 30.8: ExtendScript debugger cannot attach — ESTK endpoint never responds

   Summary

   In Illustrator 30.8.0, the Adobe ExtendScript Debugger extension for VS Code (v2.1.0) can no longer attach to or launch scripts. Rolling back to 30.7.0 fixes it completely, with no other change to VS Code, the extension, or the launch configuration — so this is a regression introduced between 30.7 and 30.8.

   The failure is narrow and specific: in 30.8, Illustrator's ExtendScript debug (#estk) channel accepts the debugger's <connect/> handshake but never sends any response. The message is delivered successfully — the core library returns status: 0 with a valid serial number — and then nothing comes back, indefinitely.

   In 30.7 the identical request returns the engine list in ~600ms.

   Everything else about Illustrator scripting is healthy in 30.8:

   • Scripts run normally from File > Scripts and via AppleScript do javascript.
   • Illustrator answers ordinary BridgeTalk messages in well under a second.
   • ScriptingSupport.aip is loaded, and the debug API is still present in the binary.

   Only the debugger's channel is dead.

   Regression Range

   Illustrator version Debugger attaches?
   30.7.0 Yes — engine list returned in ~604ms
   30.8.0 No — no response, indefinitely

   Environment

   Illustrator (broken): 30.8.0
   Illustrator (last known good): 30.7.0
   InDesign (control, works): 21.5.1.73
   macOS: 26.6.2 (build 25G83)
   Hardware: Apple M1 (arm64)
   VS Code: 1.135.0 (arm64)
   ExtendScript Debugger extension: 2.1.0
   ExtendScript engine (both apps): $.version 4.5.6, $.build 80.1060872
   BridgeTalk specifier: illustrator-30.064 (unchanged across 30.x)

   Steps to Reproduce

   1. On macOS with Illustrator 30.8 installed, launch Illustrator.
   2. In VS Code, install the Adobe ExtendScript Debugger extension (v2.1.0).
   3. Use this launch configuration — the exact configuration that works correctly under 30.7:

      {
          "type": "extendscript-debug",
          "request": "attach",
          "name": "Attach--transient",
          "hostAppSpecifier": "illustrator",
          "engineName": "transient"
      }
   

   1. Start the debug session..

   Also reproduces with:

   • "request": "launch" instead of "attach".
   • hostAppSpecifier omitted entirely (choosing Illustrator from the extension's host-application picker).
   • An explicit "hostAppSpecifier": "illustrator-30.064".
   • A freshly generated, otherwise-default launch.json.

   Expected Result

   The debugger attaches and Illustrator returns its engine list, as it does under 30.7:

   <engines engine=""><engine name="main" state="active"/><engine name="transient" state="active"/></engines>
   

   Actual Result

   Under 30.8 the debug session never establishes. Illustrator sends no response of any kind to the <connect/> request. The request does not error — it simply never completes.

   ---

   Evidence

   All probes below were run through the extension's own native core (esdebugger-core/mac/esdcorelibinterface.node, from ExtendScript Debugger 2.1.0), loaded into VS Code's Electron runtime and driven with the same esdSendDebugMessage / esdPumpSession calls the extension itself makes. This removes VS Code, launch configurations, and the extension UI from the picture entirely.

   1. The <connect/> handshake — 30.7 vs 30.8

   Illustrator 30.7 — works:

   === connect illustrator-30.064 ===
   send -> {"status":0,"serialNumber":10}
     [605ms] {"target":"vscesd_45522-2.0#dbg",
              "sender":"illustrator-30.064#estk",
              "type":"ExtendScript",
              "body":"<engines engine=\"\">
                        <engine name=\"main\" state=\"active\"/>
                        <engine name=\"transient\" state=\"active\"/>
                      </engines>",
              "serialNumber":10,"resultSerial":3}
   

   Illustrator 30.8 — no response:

   === connect illustrator-30.064 ===
   send -> {"status":0,"serialNumber":2}
     NO RESPONSE after 15093ms
   

   Identical machine, identical VS Code, identical extension build, identical call. The only variable is the Illustrator version.

   2. InDesign as a same-machine control

   InDesign, probed in the same session while Illustrator 30.8 was failing, responds immediately:

   === connect indesign-21.064 ===
   send -> {"status":0,"serialNumber":1}
     [759ms] {"sender":"indesign-21.064#estk",
              "body":"<engines engine=\"\">
                        <engine name=\"main\" state=\"active\"/>
                        <engine name=\"ConvertURLToHyperlinks\" state=\"active\"/>
                        <engine name=\"ConvertFootnoteToEndnote\" state=\"active\"/>
                      </engines>", …}
   

   So the debugger core, the native module, and the host-side protocol all work on this machine — just not with Illustrator 30.8.

   3. Application discovery is not the problem

   Under both 30.7 and 30.8 the core reports Illustrator as installed and running, under the same specifier:

   installedSpecifiers: {"status":0,"specifiers":[
       "illustrator-30.064","indesign-21.064","bridge-16.064",
       "aftereffects-26.0","audition-26.0","photoshop-200.064"]}
   
   illustrator-30.064 installed: {"status":0,"isInstalled":true}
   illustrator-30.064 running:   {"status":0,"isRunning":true}
   

   BridgeTalk.appSpecifier, queried from inside Illustrator, returns illustrator-30.064 in both versions. The specifier does not change across the 30.x line.

   4. Illustrator's ordinary BridgeTalk messaging is fine in 30.8

   A full BridgeTalk round-trip sent from InDesign to Illustrator 30.8 succeeds normally:

   illustrator-30.064 [916ms] -> OK: illustrator-30.064
   illustrator-30.064 [842ms] -> OK: main|30.8.0|4.5.6
   

   Illustrator is reachable and responsive on the normal messaging channel. Only the debug channel is silent. (Round-trip latency rises to 8–18s when Illustrator is backgrounded, which appears to be ordinary background throttling and is not the cause — the debug channel returns nothing even with Illustrator frontmost.)

   5. The ExtendScript engine is identical to InDesign's

                                    Illustrator 30.8             InDesign 21.5.1
   

   $.version 4.5.6 4.5.6
   $.build 80.1060872 80.1060872
   $.engineName main main

   Not an engine-version mismatch between app and debugger.

   6. The debug API is still present in Illustrator 30.8's binary

   AdobeExtendScript.framework inside Illustrator 30.8 still exports the full debug surface — ScScript::DebugAPI::command, setBreakpoints, getStackTrace, getContextInfo, debugBreak, enterDebugMode / leaveDebugMode, and others. Illustrator exports more debug symbols than InDesign (60 vs 35).

   ScriptingSupport.aip is present and confirmed loaded into the running process:

   /Applications/Adobe Illustrator 2026/Adobe Illustrator.app/Contents/
       Required/Plug-ins/Extensions/ScriptingSupport.aip/Contents/MacOS/ScriptingSupport
   

   The capability is compiled in and loaded; it simply does not answer.

   7. Not a "no active engine" condition

   The handshake was repeated while a script was actively executing inside Illustrator 30.8 (a 25-second $.sleep), in case the debug endpoint only materialises alongside a live engine:

   send -> {"status":0,"serialNumber":1}
     NO RESPONSE while script running (20076ms)
   

   Still silent.

   ---

   Impact

   In 30.8, ExtendScript debugging is completely unavailable — no breakpoints, no stepping, no variable inspection, no watch expressions. For anyone maintaining non-trivial Illustrator scripts this removes the only real debugging tool, leaving $.writeln logging and alert-based tracing as the only options.

   The Adobe ExtendScript Debugger is the officially supported successor to the ExtendScript Toolkit, so there is no alternative debugger to fall back on.

   Workaround

   Roll back to Illustrator 30.7 (Creative Cloud → Other Versions).

   ---

   AI notice: the troubleshooting and research was heavily facilitated by Claude Code Opus 5.

   Summary

   In Illustrator 30.8.0, the Adobe ExtendScript Debugger extension for VS Code (v2.1.0) can no longer attach to or launch scripts. Rolling back to 30.7.0 fixes it completely, with no other change to VS Code, the extension, or the launch configuration — so this is a regression introduced between 30.7 and 30.8.

   The failure is narrow and specific: in 30.8, Illustrator's ExtendScript debug (#estk) channel accepts the debugger's <connect/> handshake but never sends any response. The message is delivered successfully — the core library returns status: 0 with a valid serial number — and then nothing… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Done (Available in Beta)  ·  AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

   Expected to be fixed in the lates Beta Build 31.0.0.29 — please verify

2. [ExtendScript] Cannot set Document.rulerUnits

   There is no way via scripting to set a document's rulerUnits (pts, mm, inch, etc) because the property Document.rulerUnits is—erroneously, surely—read only.

   If Document.rulerUnits was writable, we would simply do this:

     var doc = app.activeDocument;
     doc.rulerUnits = RulerUnits.MILLIMETERS;
   

   This is important because there is literally no way to set this via script, except to create a new document.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Incorrect word count via script

   At some point (I think v27) Illustrator has changed its word counting/division algorithm.

   So, where previously the results were sensible:
   "This.Was.Four.Words" — word count: 4
   "This.Is.3.Words" — word count: 4
   "I.WF05f.07.AB.000" — word count: 5
   "I.WF05f.AB.07.000" — word count: 5

   In version 27.4 the results are now confused:
   "This.Was.Four.Words" — word count: 1
   "This.Is.3.Words" — word count: 3
   "I.WF05f.07.AB.000" — word count: 4
   "I.WF05f.AB.07.000" — word count: 2

   For a discussion on the topic, and a testing script, see this thread.

   Note: maybe this bug was introduced while fixing this bug.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. [ExtendScript] TextFrame cannot be selected after creating

   In script, after creating a new TextFrame it cannot be selected the first time.

     (function () {
   
       if (0 === app.documents.length)
           return alert('Please open a document and try again.');
   
       var doc = app.activeDocument,
           results = ['Results:'];
   
       // experiment 1
       var tf1 = doc.textFrames.add();
       tf1.contents = '1. created, selected:';
       tf1.selected = true;
       results.push(tf1.contents + ' ' + (tf1.selected ? 'PASS' : 'FAIL'));
   
       // experiment 2
       var tf2 = doc.textFrames.add();
       tf2.contents = '2. created, selected twice:';
       tf2.selected = true;
       tf2.selected = true;
       results.push(tf2.contents + ' ' + (tf2.selected ? 'PASS' : 'FAIL'));
   
       alert(results.join('\n'));
   
     })();
   

   Expected results: both tests would pass.
   Actual results: only the second test passes.

   See the discussion at this forum post.

   Note: this only seems to happen with a TextFrame. PathItems, for example don't show this bug.

   In script, after creating a new TextFrame it cannot be selected the first time.

     (function () {
   
       if (0 === app.documents.length)
           return alert('Please open a document and try again.');
   
       var doc = app.activeDocument,
           results = ['Results:'];
   
       // experiment 1
       var tf1 = doc.textFrames.add();
       tf1.contents = '1. created, selected:';
       tf1.selected = true;
       results.push(tf1.contents + ' ' + (tf1.selected ? 'PASS' : 'FAIL'));
   
       // experiment 2
       var tf2 = doc.textFrames.add();
       tf2.contents = '2. created, selected twice:';
       tf2.selected = true;
       tf2.selected = true;
       results.push(tf2.contents + ' ' + (tf2.selected ? 'PASS' : 'FAIL'));
   
       alert(results.join('\n'));
   
     })();
   

   Expected results: both tests would pass.
   Actual results:… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Bug: exporting SVG's via exportFile(fileObjSingle, ExportType.SVG, svgOptions). has completely changed since 28.4

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program over many years that depends on special characters in the SVG ID's, and it is now completely broken.

   Does anyone know how to get back the previous SVG export format?

   Does anyone know if this is a bug that will be fixed?

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add Bleed setting / reading value in Illustrator JavaScript

   I checked illustrator JavaScript Scripting Reference
   In 2017, only the document bleeding documentbleedoffsetrect can be set, but the bleeding size that has been set in the document cannot be obtained. Is it because the document is incomplete or this method is not provided? Now how can I get the bleeding size of the current document. thank you!

   Examples code:
   //set bleed
   docPreset.documentBleedOffset = [10, 10 10,10];

   But there is no way to get the value that has been set

   •  

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Scripting window keeps appearing and no way to remove it

   Uninstalling/Reinstalling does not remove prompt. Starting appearing after most recent update to with the new ipad features. Going back to older version, the window doesn't appear.

   •  

   •  

   •  

   •  

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   7 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminRama (Mgr, Software Development, Adobe Illustrator) responded

   This issue is happening due to a security feature added in Illustrator to inform the user if any external application tries to execute a script in Illustrator.

   Solution: Update your Logitech options app to the latest version – https://www.logitech.com/en-in/product/options

   https://helpx.adobe.com/illustrator/kb/fix-scripting-error.html

   We heard from some users that above solution is not working for them, we are investigating this issue. Meanwhile users can try the below workaround

   Create a JSX file with the following content:
   app.preferences.setBooleanPreference(“ShowExternalJSXWarning”, false);
   Save the above JSX file. Now, go to File > Scripts > Other Script, and choose the newly saved jsx file.

   This will suppress the warning dialog and run the script.

8. ExtendScript gives && and || equal precedence

   The below is from u/Ales-78 on Reddit:

   https://www.reddit.com/r/AdobeIllustrator/comments/1x0idoa/extendscript_gives_and_equal_precedence_confirmed/

   "I found this while debugging something that made no sense, and because I once reported a "bug" to Adobe that turned out to be my own syntax error, I checked it on several versions before posting.

   ExtendScript evaluates && and || at the same precedence level, left to right. So a || b && c is parsed as (a || b) && c instead of the correct a || (b && c). ECMAScript requires && to bind tighter.

   Two lines, no document needed:

   alert(true || false && false);

   // prints "false", should print "true"

   Confirmed on:

   Illustrator 30.8.1, ExtendScript 4.5.6, Windows

   Illustrator CS6 16.0.0, ExtendScript 4.2.12, Windows

   Illustrator 30.8.2, macOS (confirmed by Monika Gause)

   Line for line identical across all three. Other precedences are fine, I tested ternary, arithmetic, bitwise, typeof, in and instanceof. It really is just these two operators.

   Both readings agree almost all the time. They diverge only when the first operand is truthy and the last one is falsy, which is how it can sit in a codebase for years without surfacing.

   What made it visible for me was minification. I write a || (b && c) in the source. Closure Compiler ADVANCED removes those parentheses, because in standard JavaScript they genuinely are redundant, and its output is correct JS. ExtendScript then reads it the other way round and the conditional logic silently inverts.

   So Closure is not at fault either. Two individually correct things meeting in the wrong place.

   My workaround is a post-compile pass that re-adds parentheses around any && that is a direct operand of ||, then verifies the standard JS AST has not changed.

   If you ship minified ExtendScript, this is worth checking."

   The below is from u/Ales-78 on Reddit:

   https://www.reddit.com/r/AdobeIllustrator/comments/1x0idoa/extendscript_gives_and_equal_precedence_confirmed/

   "I found this while debugging something that made no sense, and because I once reported a "bug" to Adobe that turned out to be my own syntax error, I checked it on several versions before posting.

   ExtendScript evaluates && and || at the same precedence level, left to right. So a || b && c is parsed as (a || b) && c instead of the correct a || (b && c). ECMAScript requires && to bind tighter.

   Two lines, no document needed:

   alert(true || false && false);

   // prints "false", should… more

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Plugins Disappeared

   after updating to version 25.1
   the plugins in the "plugins folder"
   don't Load up
   when downgrade back to version 25.0.1
   Its work fine

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Failure to create artboards when reading file with SDK in CC 2018

    Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

    In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems to be based on the documents the user has been working with.

    This means that if you have two users, one who uses small documents and one who uses large documents and they both open the same medium size file using your plugin, it works for the user who has been using large documents but not for the user who has been using small documents. As there is no AIDocument::SetDocumentMaxArtboardBounds function, there seems to be no way the plugin can overcome this issue.

    Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

    In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    10 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. [ExtendScript] Cannot set TextRange.justification to value in ParagraphStyle

    We cannot successfully set textFrame.textRange.justification to the value in the applied ParagraphStyle.

    For example, if the text has [Normal Paragraph Style] applied, which for me has Justification.LEFT, then I cannot set that text to have Justification.LEFT in cases where the justification has been changed.

    (Tested on MacOS 15.4.1 Adobe Illustrator 29.5.1, but this appears to be an old bug.)

    Steps to reproduce:
    1. Create new document
    2. Run the below script

    Expected Result: all tests passed and no alert message appears.

    Actual result: Failed to set textRange.justification to LEFT.

    Script:

    (function () {
    
        var doc = app.activeDocument,
            textFrame = doc.textFrames.add();
    
        textFrame.textRange.contents = 'Hello.';
    
        // prepare for the test, ensuring - due to the bug - that the justification won't match the applied paragraph style
        textFrame.textRange.justification = Justification.RIGHT;
        textFrame.textRange.justification = Justification.CENTER;
        textFrame.textRange.justification = Justification.LEFT;
    
        // test RIGHT justification
        textFrame.textRange.justification = Justification.RIGHT;
        if (textFrame.textRange.justification !== Justification.RIGHT)
            alert('Failed to set textRange.justification to RIGHT.');
    
        // test CENTER justification
        textFrame.textRange.justification = Justification.CENTER;
        if (textFrame.textRange.justification !== Justification.CENTER)
            alert('Failed to set textRange.justification to CENTER.');
    
        // test LEFT justification
        textFrame.textRange.justification = Justification.LEFT;
        if (textFrame.textRange.justification !== Justification.LEFT)
            alert('Failed to set textRange.justification to LEFT.');
    
    })();
    

    Additional note: in the link above, users discovered that performing a resize on the textFrame somehow removes the blockage and Justification.LEFT can be set afterwards. Perhaps it breaks the link to the paragraph style?

    Edit 2025-05-23: to add details about the possible link to the applied paragraph style.

    A possible temporary workaround:

    // set LEFT justification
    textFrame.textRange.justification = Justification.LEFT;
    
    // now check it
    if (
        Justification.LEFT !== textFrame.textRange.justification
        && Justification.LEFT === textFrame.textRange.paragraphStyles[0].justification
    ) {
        // bypass a bug where we can't set the attribute that matches the applied paragraph style:
        //  - change the applied paragraph style's justification
        //  - then change the textFrame's justification to the style's previous value,
        //  - then return the paragraph styles original setting
        textFrame.textRange.paragraphStyles[0].justification = Justification.CENTER;
        textFrame.textRange.justification = Justification.LEFT;
        textFrame.textRange.paragraphStyles[0].justification = Justification.LEFT;
    }
    

    We cannot successfully set textFrame.textRange.justification to the value in the applied ParagraphStyle.

    For example, if the text has [Normal Paragraph Style] applied, which for me has Justification.LEFT, then I cannot set that text to have Justification.LEFT in cases where the justification has been changed.

    (Tested on MacOS 15.4.1 Adobe Illustrator 29.5.1, but this appears to be an old bug.)

    Steps to reproduce:
    1. Create new document
    2. Run the below script

    Expected Result: all tests passed and no alert message appears.

    Actual result: Failed to set textRange.justification to LEFT.

    Script:

    (function () {
    
        var doc = app.activeDocument,
            textFrame

    … more
    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Applescript—cannot save Illustrator file if embedding ICC profiles

    This is a bug, as verified by this post (https://community.adobe.com/t5/illustrator-discussions/there-is-a-problem-with-saving-as-illustrator-using-applescript/m-p/15287552) and this post (https://community.adobe.com/t5/illustrator-discussions/applescript-cannot-embed-icc-profiles-in-illustrator-save-options/m-p/15032019#M429674). I cannot save an Illustrator file as part of an AppleScript if ICC profiles are being embedded. This is a problem because I can no longer use my Applescripts for creating versions of logo files.

    The following code will fail with the error "Cannot get document 1". The error occurs when the save command’s with options parameter is a record containing a embed icc profile property.

    save document 1 in filePath as Illustrator with options {embed icc profile:true}
    I have verified that a) the ICC profile was already embedded in the source document, and that if I save the file via the GUI, checking the box to save the ICC profile works. Using AppleScript to save the Illustrator file does not retain the ICC profile.

    This fails on macOS 14.5 and Illustrator 27.x and 28.5. It also fails on macOS 15.4 and Illustrator 29.5.0. It also fails on macOS 15.3.2 and Illustrator 28.7.6 and 29.5.

    According to another user, JavaScript works properly. However, JavaScript is not a workaround for me.
    var d = app.documents[0];

    var saveOptions = new IllustratorSaveOptions();
    saveOptions.flattenOutput = OutputFlattening.PRESERVEAPPEARANCE;
    saveOptions.embedICCProfile = true;

    d.saveAs(new File('~/testjs.ai'), saveOptions);

    Please help -- I need to be able to save an Illustrator file with AppleScript, that has an embedded ICC profile.

    This is a bug, as verified by this post (https://community.adobe.com/t5/illustrator-discussions/there-is-a-problem-with-saving-as-illustrator-using-applescript/m-p/15287552) and this post (https://community.adobe.com/t5/illustrator-discussions/applescript-cannot-embed-icc-profiles-in-illustrator-save-options/m-p/15032019#M429674). I cannot save an Illustrator file as part of an AppleScript if ICC profiles are being embedded. This is a problem because I can no longer use my Applescripts for creating versions of logo files.

    The following code will fail with the error "Cannot get document 1". The error occurs when the save command’s with options parameter is a record containing a embed icc profile property.

    save document 1 in filePath as Illustrator with options {embed icc profile:true}
    I have verified that… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. [ExtendScript] Rasterizing group creates two rasterItems

    1. MacOS 15.2.
    2. Adobe Illustrator 29.1
    3. Open demo document (attached) and run script (below).
    4. Should create one RasterItem, but instead creates two.

    Test Script (for use on attached test file):

    
    (function () {
    
        var doc = app.activeDocument;
        var item = doc.groupItems[0];
    
        // Raster Options
        var rasterOpts = new RasterizeOptions;
        rasterOpts.resolution = 192;
        rasterOpts.antiAliasingMethod = AntiAliasingMethod.None;
        rasterOpts.backgroundBlack = false;
        rasterOpts.clippingMask = false;
        rasterOpts.colorModel = RasterizationColorModel.DEFAULTCOLORMODEL;
        rasterOpts.convertTextToOutlines = false;
        rasterOpts.includeLayers = false;
        rasterOpts.padding = 0;
        rasterOpts.transparency = false;
        rasterOpts.convertSpotColors = true;
    
        doc.rasterize(item, item.geometricBounds, rasterOpts);
    
        var count = doc.rasterItems.length;
    
        if (count > 1)
            alert('The rasterization created two images but should have created only one.');
    
    })();
    
    
    

    See also this forum post.

    Edit: Note that the resolution (greater than 191) and the exact position of the group's path items makes a difference.

    1. MacOS 15.2.
    2. Adobe Illustrator 29.1
    3. Open demo document (attached) and run script (below).
    4. Should create one RasterItem, but instead creates two.

    Test Script (for use on attached test file):

    
    (function () {
    
        var doc = app.activeDocument;
        var item = doc.groupItems[0];
    
        // Raster Options
        var rasterOpts = new RasterizeOptions;
        rasterOpts.resolution = 192;
        rasterOpts.antiAliasingMethod = AntiAliasingMethod.None;
        rasterOpts.backgroundBlack = false;
        rasterOpts.clippingMask = false;
        rasterOpts.colorModel = RasterizationColorModel.DEFAULTCOLORMODEL;
        rasterOpts.convertTextToOutlines = false;
        rasterOpts.includeLayers = false;
        rasterOpts.padding = 0;
        rasterOpts.transparency = false;
        rasterOpts.convertSpotColors = true;
    
        doc.rasterize(item, item.geometricBounds, rasterOpts);
    
        var count = doc.rasterItems.length;
    
        if (count > 1)
            alert('The rasterization created two images but should have created only one.');

    … more

    • 

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. [ExtendScript] PageItem.resize doesn't scale Live Paint strokes

    While scaling Live Paint object correctly scales strokes if done via the UI, it fails to scale strokes if done via the PageItem.resize method in the scripting API.

    MacOS 15.0.1 Illustrator 29.0.

    Steps to reproduce:
    1. New document
    2. Create a Live Paint object including stroked areas.
    3. Select the Live Paint object.
    4. Run the following script:

    var item = app.activeDocument.selection[0];
    item.resize(200, 200, true, true, true, true);
    

    Expected result is that the Live Paint object's stroke widths would double. However they remain the same as before.

    See this user post.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. [ExtendScript] Cannot change `underline` value of some text ranges.

    We cannot successfully set characterAttribute.underline to false in some textRanges.

    (MacOS 15.0 Adobe Illustrator 28.7.1)

    Steps to reproduce:
    1. New document
    2. Make a text frame with contents "ab"
    3. Set the "b" to a different fontStyle, eg. "italic"
    4. Run the below script, and check the console output.

    Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

    Actual result, test B on the "b" fails.

    Script:
    ```
    (function () {

    var doc = app.activeDocument,
        tf = doc.textFrames[0];
    
    var results = ['Results:'];
    
    tf.textRanges[0].characterAttributes.underline = true
    results.push('textRanges[0] test A: ' + (true === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
    
    tf.textRanges[0].characterAttributes.underline = false;
    results.push('textRanges[0] test B: ' + (false === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
    
    tf.textRanges[1].characterAttributes.underline = true;
    results.push('textRanges[1] test A: ' + (true === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
    
    tf.textRanges[1].characterAttributes.underline = false;
    results.push('textRanges[1] test B: ' + (false === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
    
    alert(results.join('\n'));
    

    })();
    ```

    See this community forum post.

    Update: User sttk3 discovered that the bug is actually that Illustrator ignores an attempt to set a characterAtrribute property if the value is the same as the applied character style's value for the same attribute.

    We cannot successfully set characterAttribute.underline to false in some textRanges.

    (MacOS 15.0 Adobe Illustrator 28.7.1)

    Steps to reproduce:
    1. New document
    2. Make a text frame with contents "ab"
    3. Set the "b" to a different fontStyle, eg. "italic"
    4. Run the below script, and check the console output.

    Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

    Actual result, test B on the "b" fails.

    Script:
    ```
    (function () {

    var doc = app.activeDocument,
        tf = doc.textFrames[0];
    
    var results = ['Results:'];
    
    tf.textRanges[0].characterAttributes.underline = true
    results.push('textRanges[0] test A: ' +

    … more

    • 

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. [ExtendScript] Line feed \u000A character assigned to text contents is converted to carriage return

    MacOS 13.3.1, Adobe Illustrator 27.4.1
    Also reported on Windows same version of Illustrator.

    Steps to reproduce.
    To see problem, run this script
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Break\u000Ame.';
    alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Break\u0003me.';
    alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
    

    })();
    ```
    I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
    The text on the right is a workaround, using an unexpected character (u+0003).

    There is a discussion here.

    This silent conversion is unexpected, and never wanted by the user (the scripter).

    MacOS 13.3.1, Adobe Illustrator 27.4.1
    Also reported on Windows same version of Illustrator.

    Steps to reproduce.
    To see problem, run this script
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Break\u000Ame.';
    alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Break\u0003me.';
    alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
    

    })();
    ```
    I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
    The text on the right is a workaround,… more

    • 

    •  

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. IUStringUnitsToAIReal doesn't recognize comma as decimal separator

    std::string input_ = "1,5"; // From Adobe header: The string to convert, which uses the localized international utilities (IU) decimal separator.
    AIReal n;
    sAIUser->IUStringUnitsToAIReal(ai::UnicodeString(input_), &n);

    This function interprets the text "1,5" as "15" even when the locale is set to a country where the system uses a comma decimal separator. Related functions IUStringToAIReal recognizes the comma, though.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. AIPaintStyleSuite not found

    Trying to update a plugin to use the Illustrator 2020 SDK on Mac. Previously using the 2017 SDK. The SPBasicSuite AcquireSuite function fails to find the AIPaintStyleSuite when building with the 2020 SDK.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. GetPresetSettings function doesn't work correctly in CC 2017 and later

    In Illustrator CC 2017 (22.x) and CC 2018 (23.x) the AIDocumentList::GetPresetSettings function is broken. It still returns an error if the preset doesn't exist, but if the preset does exist, it returns 0, but doesn't fill in the AINewDocumentPreset structure.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. [ExtendScript] never releases PathPoint objects so scripts slow down.

    ExtendScript never releases PathPoint objects, so scripts slow down until Illustrator restarts

    Versions: Illustrator Beta 31.0.0, macOS 26.7.1. Also reported in Illustrator 2026 on Windows (community thread).

    Summary

    When a script gets a path point (pathItem.pathPoints[i]), ExtendScript creates a PathPoint object, plus a PathPoints object for the collection and an Array for .anchor. None of these are ever released. As they build up, every later script in that engine gets slower, including scripts that never touch path points. Only quitting Illustrator clears them.

    Steps to reproduce

    1. Run the script below from File > Scripts in a freshly launched Illustrator.
    2. Run it again a few more times.

    (function () {
    
        var doc = app.documents.add();
    
        function countOf(type) {
            var match = $.summary().match(new RegExp('^\\s*(\\d+) ' + type + '$', 'm'));
            return match ? Number(match[1]) : 0;
        };
    
        // fixed job that never touches path points: make 1,500 rectangles, read bounds, set stroke, delete them
        function job() {
    
            var t0 = new Date().getTime();
            var layer = doc.layers.add();
            var refs = [];
            var i;
    
            for (i = 0; i < 1500; i++)
                refs.push(layer.pathItems.rectangle(-(i % 50) * 3, Math.floor(i / 50) * 3, 2, 2));
    
            for (i = 0; i < refs.length; i++) {
                var b = refs[i].geometricBounds;
                refs[i].strokeWidth = 0.5;
            }
    
            layer.remove();
            return new Date().getTime() - t0;
    
        };
    
        // make 6,000 rectangles, read every anchor (24,000 points), delete them
        function readPoints() {
    
            var layer = doc.layers.add();
    
            for (var i = 0; i < 6000; i++) {
                var pp = layer.pathItems.rectangle(-(i % 50) * 3, Math.floor(i / 50) * 3, 2, 2).pathPoints;
                for (var k = 0; k < pp.length; k++)
                    var a = pp[k].anchor;
            }
    
            layer.remove();
    
        };
    
        var before = job();
        readPoints();
        $.gc();
        var after = job();
    
        doc.close(SaveOptions.DONOTSAVECHANGES);
        $.gc();
    
        var message = 'Job: ' + before + ' ms before, ' + after + ' ms after.\n'
            + 'Still alive after deleting shapes, closing the document and $.gc():\n'
            + countOf('PathPoint') + ' PathPoint, ' + countOf('PathPoints') + ' PathPoints, '
            + countOf('PathItem') + ' PathItem.';
    
        alert(message);
    
    })();
    

    Expected

    Once the shapes are deleted, the document is closed and $.gc() has run, the PathPoint and PathPoints counts drop back to 0, as the PathItem count does. The job takes the same time on every run.

    Actual

    • The PathItem count returns to 0, but every PathPoint, PathPoints and anchor Array stays alive. Each run adds 24,000 more.
    • Reading the same point twice adds nothing, so each point gets one object, cached and never freed.
    • The fixed job, which never reads a point, gets slower with every run and stays slow:

    | Run | Job | Reading 24,000 points | Live PathPoint objects |
    |---|---|---|---|
    | Control, no point reading | 27–43 ms | — | 1,600 |
    | 1 | 117 ms | 1,070 ms | 25,600 |
    | 2 | 262 ms | 4,095 ms | 49,600 |
    | 3 | 333 ms | 4,728 ms | 73,600 |
    | Control again, no point reading | 294–464 ms | — | 97,600 |

    Things that don't release the objects

    • Deleting the shapes, setting every reference to null, and calling $.gc() repeatedly.
    • Closing the document without saving.
    • Also reported on Windows: undoing back to an empty document, removing the points first (pathPoint.remove() / pathPoints.removeAll()), and waiting 5 to 30 seconds. It happens in CEP panel engines as well as the main engine. Just taking a point (var p = pp[i]) without reading any property creates the object.

    Impact

    This affects any script that reads many path points (cleanup, comparison or measuring tools) and every script run after it in the same session. Today the only fix is to restart Illustrator.

    Requests

    1. Release PathPoint / PathPoints objects when they are no longer referenced, or at least when their path is deleted.
    2. Provide a way to read a path's points in bulk as plain numbers, so no PathPoint object is created for each point. Today there isn't one: toSource(), uneval() and String() don't return coordinates.

    Bug was noticed by forum user Glenn Wilton (link to post above) and report was drafted by Claude Opus 5.5.

    ExtendScript never releases PathPoint objects, so scripts slow down until Illustrator restarts

    Versions: Illustrator Beta 31.0.0, macOS 26.7.1. Also reported in Illustrator 2026 on Windows (community thread).

    Summary

    When a script gets a path point (pathItem.pathPoints[i]), ExtendScript creates a PathPoint object, plus a PathPoints object for the collection and an Array for .anchor. None of these are ever released. As they build up, every later script in that engine gets slower, including scripts that never touch path points. Only quitting Illustrator clears them.

    Steps to reproduce

    1. Run the script below from File > Scripts in… more
    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDK and Scripting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating