87 results found

1. Javacript locking embeded image

   In Illustrator 29.1 this script worked just fine. I place an image, move it, name it, lock it and embed it. But in 29.3 this code gives an error message: It says that it cannot operate on a locked layer, BUT it still locks the placed item. If I move the lock to after the embed, the lock does not happen. So this code no longer works in 29.3.

   I think its weird in 29.1 that you were allowed to lock the placeditem before you embed it, but it doesn't work if you lock it afterwards.

   We are using macos 15.1.1 (and 15.3.1). I have verified that this code functions on 29.1 and fails on 29.3. We have verified this across multiple desktop computers.

   We found this issue in a much larger code base, but I was able to extract this down to this code chunk below.

   var doc = app.activeDocument;
   var scriptFile = new File($.fileName);
   var scriptFolder = scriptFile.path;
   var filePath = new File(scriptFolder + "/Golf Ball.png");

   // Place the image
   var placedItem = doc.placedItems.add();
   placedItem.file = filePath;

   // Center the image
   var docBounds = doc.artboards[0].artboardRect;
   var centerX = (docBounds[0] + docBounds[2]) / 2;
   var centerY = (docBounds[1] + docBounds[3]) / 2;

   placedItem.position = [centerX - placedItem.width / 2, centerY + placedItem.height / 2];

   // Embed the image

   placedItem.name = "Golf Ball Texture"; // Name the placed item

   placedItem.locked = true;
   placedItem.embed();

   In Illustrator 29.1 this script worked just fine. I place an image, move it, name it, lock it and embed it. But in 29.3 this code gives an error message: It says that it cannot operate on a locked layer, BUT it still locks the placed item. If I move the lock to after the embed, the lock does not happen. So this code no longer works in 29.3.

   I think its weird in 29.1 that you were allowed to lock the placeditem before you embed it, but it doesn't work if you lock it afterwards.

   We are using macos… more

   •  

   3 votes

   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

   4 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 Prerelease)  ·  AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

   The issue is reported to be fixed in the latest Pre-release build 29.4.130.

   The provided script should now work without any error dialog, as before.

   Please also see the recommended way to achieve locking of embedded art in modified script, in a comment within.

2. 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

   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

3. XMPMeta is not defined on ILST 28.7.1 on MacOS #515

   As of ILST 28.7.1 on MacOS, XMPMeta has stopped working. However, it works fine on:
   - ILST 28.7.1 on Windows
   - ILST 28.6 on MacOs

   The issue also exists on ILST (Beta) 29.1 on MacOs.

   Example code:
   ```
   if (!ExternalObject.AdobeXMPScript) {
   ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
   }

   const xmp = new XMPMeta(app.activeDocument.XMPString); // throws XMPMeta does not have a constructor
   ```

   16 votes

   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
   Completed (Comments Open)  ·  AdminAkshaya Saxena (Admin, Adobe Illustrator) responded

   We have fixed this issue in 29.0 and 28.7.2 releases.

4. [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

   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

5. [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

   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. Adobe Illustrator 28.7.3 does not load AIBeautifulStrokes

   Adobe Illustrator 28.7.3, at least the macOS version, does not load AIBeautifulStrokes suite in my plugin (error 29550). All other versions, including up to 28.7.2, work fine. I am using SDK build 142, the version of the 2024 SDK now available for download.

   AIErr err = sSPBasic->AcquireSuite (kAIBeautifulStrokesSuite, kAIBeautifulStrokesVersion, (const void**) &sAIBeautifulStrokes);
   

   1 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
   AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

   No longer happens with 29.1

7. Issue with Reading Variable Data from DataSet in Illustrator 29.5

   Dear Adobe Support Team,

   I am reaching out to report an issue with Adobe Illustrator (version 29.5) regarding the inability to read variable data from a DataSet object in a script, even though the dataset is correctly loaded and updates the document content as expected.

   Problem Description
   I have a script that processes a CSV file to generate PDF files using variable data in Illustrator. The CSV file contains columns "Cislo" (number) and "JMENO" (name), and it is correctly loaded into Illustrator as a dataset (via Window > Utilities > Variables > Load Variable Library). The dataset updates the document content correctly—when I call dataSets[i].display(), the text fields in the document update with the correct values (e.g., "1", "URBAN" for the first dataset). However, when I attempt to read the variable values programmatically from the DataSet object (e.g., via dataSets[i].variables[j].content), the script fails to retrieve any values, resulting in empty strings.

   Steps We Tried
   We have tried multiple approaches to read the variable values, but none of them worked as expected:

   Reading via dataSets[i].variables[j].content:
   We iterated through dataSets[i].variables, checked the variable names (e.g., variable.name === "Cislo"), and attempted to read the content property.
   Result: The content property always returned an empty string, even after calling dataSets[i].display().
   Reading via getByName:
   We tried using dataSets[i].variables.getByName("Cislo").content to directly access the variable's value.
   Result: This threw an error ("Error 21: undefined is not an object") if the variable was not found, and even when wrapped in a try-catch block, it returned an empty string.
   Reading via variable.textFrames[0].contents:
   We attempted to access the text frame linked to the variable using doc.variables[j].textFrames[0].contents after dataSets[i].display().
   Result: This approach also returned empty strings, even though the text frames in the document were visibly updated with the correct values.
   Workaround (Successful but Manual):
   As a workaround, we named the text frames in the document ("CisloText", "JmenoText") and read their values directly using doc.textFrames.getByName("CisloText").contents.
   Result: This worked and correctly retrieved the values (e.g., "1", "URBAN"), confirming that the dataset and variables are functioning as expected for updating the document. However, this is not a practical solution as it requires manual naming of text frames, which is not feasible for larger workflows.
   Observations
   The CSV file is correct and properly formatted:

   Cislo,JMENO
   1,URBAN
   2,JIŘÍ
   3,TOMÁŠ
   4,EDA
   5,
   6,NOVOTNÝ
   7,KAREL​
   The dataset updates the document content correctly when dataSets[i].display() is called (e.g., the text fields show "1", "URBAN" in the UI).
   The generated PDF files contain the correct content based on the dataset, confirming that the dataset and variables are working.
   However, all attempts to programmatically read the variable values from the DataSet object (dataSets[i].variables) result in empty strings or errors.
   Sample Script testVariableReading.jsx:

   var doc = app.activeDocument;
   var dataSets = doc.dataSets;

   // Kontrola, zda existují sady dat
   if (!dataSets || dataSets.length === 0) {
   alert("Error: No datasets found in the document. Please load a CSV file with variables.");
   } else {
   for (var i = 0; i < dataSets.length; i++) {
   dataSets[i].display(); // Aktivuje sadu dat (mění proměnné – Cislo, JMENO)

       // Pokus o načtení hodnot z dataSets[i].variables (selhává)
       var currentCisloFromDataSet = "";
       var currentJmenoFromDataSet = "";
       try {
           var variables = dataSets[i].variables;
           for (var j = 0; j < variables.length; j++) {
               var variable = variables[j];
               var varName = variable.name;
               if (varName === "Cislo") currentCisloFromDataSet = variable.content || "";
               if (varName === "JMENO") currentJmenoFromDataSet = variable.content || "";
           }
       } catch (e) {
           alert("Error reading variables from dataset " + (i + 1) + ": " + e);
       }
   
       // Načtení hodnot z pojmenovaných textových polí (funguje)
       var currentCisloFromTextFrame = "";
       var currentJmenoFromTextFrame = "";
       try {
           var cisloTextFrame = doc.textFrames.getByName("CisloText");
           if (cisloTextFrame) currentCisloFromTextFrame = cisloTextFrame.contents || "";
   
           var jmenoTextFrame = doc.textFrames.getByName("JmenoText");
           if (jmenoTextFrame) currentJmenoFromTextFrame = jmenoTextFrame.contents || "";
       } catch (e) {
           alert("Error reading text frames for dataset " + (i + 1) + ": " + e);
       }
   
       // Zobrazení výsledků pro srovnání
       alert(
           "Dataset " + (i + 1) + ":\n" +
           "From dataSets[i].variables:\n" +
           "Cislo=" + currentCisloFromDataSet + ", JMENO=" + currentJmenoFromDataSet + "\n\n" +
           "From textFrames.getByName:\n" +
           "Cislo=" + currentCisloFromTextFrame + ", JMENO=" + currentJmenoFromTextFrame
       );
   }
   

   }
   Request
   It seems there might be a bug in Illustrator 29.5 where the DataSet object's variables property does not correctly expose the content of variables after display() is called. I would appreciate if you could investigate this issue and provide a solution or workaround to programmatically read the variable values from a dataset without relying on manually named text frames.

   Attachments
   I am attaching the following files for your reference:

   The CSV file (data.csv) used to load the dataset.
   A sample file (sample.pdf) with the variables and dataset set up, where the issue can be reproduced. I have saved the file as a PDF because the original .ai file was rejected due to a content type mismatch (application/postscript). The PDF was saved with "Preserve Illustrator Editing Capabilities" enabled, so you should be able to open it in Illustrator and see the variables and dataset. Note that the text frames in this file are already named "CisloText" and "JmenoText" as part of the workaround, so reading via doc.textFrames.getByName("CisloText").contents will work. However, the issue with reading directly from dataSets[i].variables should still be reproducible.
   A test script (testVariableReading.txt) that demonstrates the issue. Please note that I could not attach the script with its original .jsx extension as it is not a supported file type. I have renamed it to testVariableReading.txt. To test the script, please rename it back to testVariableReading.jsx. The script attempts to read variable values both from dataSets[i].variables (which fails) and from named text frames (which works), and displays the results in an alert for comparison.
   Thank you for your assistance! Please let me know if you need any additional information to investigate this issue.

   Best regards,
   Ales Ulrych

   Dear Adobe Support Team,

   I am reaching out to report an issue with Adobe Illustrator (version 29.5) regarding the inability to read variable data from a DataSet object in a script, even though the dataset is correctly loaded and updates the document content as expected.

   Problem Description
   I have a script that processes a CSV file to generate PDF files using variable data in Illustrator. The CSV file contains columns "Cislo" (number) and "JMENO" (name), and it is correctly loaded into Illustrator as a dataset (via Window > Utilities > Variables > Load Variable Library). The dataset updates the document… more

   • 

   • 

   • 

   1 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  ·  Edit…  ·  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

8. [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

   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

9. [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

   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

10. Unable to catch error that occurs when exporting empty artboard to PSD

    en_US

    When exporting Illustrator artboards to PSD using ExtendScript's exportFile, if the artboard does not contain valid PageItems, an error occurs and two alerts are displayed.

    
    

    The problem is that this error cannot be caught by a try syntax. It will stop the batch process with alerts.

    Also, if app.userInteractionLevel = UserInteractionLevel.DONTDISPLAYALERTS is used to prevent the alert, it is not possible to provide detailed information to the script user as to why the artboard was not exported.

    Ideally, the design should be changed so that the error can be caught, or even an empty artboard can be exported.

    Steps to reproduce

    1. open the attached file empty_artboard.ai in Illustrator
    2. execute the script in the Script to execute section or the attached file psd_export.txt (please change the extension to jsx beforehand)

    Expected result

    Errors will be caught and an alert "Caught error" will appear, then safely exit.

    Actual result

    The error penetrates try syntax and the alert is displayed twice. The contents are as follows:
    1. Empty artboard(s) were not exported.
    2. The operation cannot be completed because of an unknown error. [!SEL]

    The error 2 starts to occur in Illustrator 2022 and does not occur in older versions such as Illustrator 2021.

    Workaround

    • Use selectObjectsOnActiveArtboard, etc. to detect empty artboards by myself to avoid the error (to be precise, it is necessary to ignore isolated points and other PageItem that are ignored by the PSD export function by myself).
    • Generate a Rectangle of the same size as the artboard without fill and stroke in advance and export it for avoid the error. An empty image will be successfully exported.

    Environment

    • macOS 12.7.3, 14.3.0(Apple Silicon)
    • Illustrator 2019(23.1.1) to 2024(28.1.0)

    Not sure when this error started, but it reproduces in Illustrator CS6 too.

    Attached files

    Script to execute

    ---

    ja_JP

    空のアートボードをPSDに書き出そうとしたとき起こるエラーをcatchできない

    ExtendScriptのexportFileにてIllustratorのアートボードをPSDに書き出すとき、アートボードに有効なPageItemが含まれていないとエラーが起こり、2つの警告が出ます。

    
    

    問題は、このエラーはtryで囲ってもcatchできないことです。バッチプロセスをアラートで止めてしまいます。

    また、もしapp.userInteractionLevel = UserInteractionLevel.DONTDISPLAYALERTSでアラートを出ないようにした場合、スクリプトのユーザーになぜアートボードが書き出されなかったか詳しい情報を提供することができません。

    エラーをcatchできるようにするか、空のアートボードでも気にせず書き出すよう変更するのが理想的な設計です。

    再現手順

    1. 添付ファイルempty_artboard.aiをIllustratorで開きます
    2. 実行するスクリプトセクションのスクリプトか、添付ファイルpsd_export.txtを実行します（事前に拡張子はjsxに変えておいてください）

    期待する結果

    エラーはcatchされ「Caught error」とアラートが出たあと安全に終了します。

    実際の結果

    エラーがtry構文を貫通し、アラートが2回表示されます。内容は次の通りです。
    1. Empty artboard(s) were not exported.
    2. The operation cannot complete because of an unknown error. [!SEL]

    2のエラーはIllustrator 2022から出始めていて、それ以前のIllustrator 2021などでは発生しません。

    回避策

    • selectObjectsOnActiveArtboardなどを使い、空のアートボードを自力で検出してエラーを回避します（正確に言えば、孤立点などPSD書き出し機能に無視されるPageItemを、自力で無視する必要があります）
    • アートボードと同じサイズの塗り・線なしのRectangleを事前に生成して書き出すことで、エラーを出ないようにできます。ただし、何もない画像が書き出しに成功します

    環境

    • macOS 12.7.3, 14.3.0(Apple Silicon)
    • Illustrator 2019(23.1.1)〜2024(28.1.0)

    このエラーがいつからあるのかわかりませんが、Illustrator CS6でも再現します。

    添付したファイル

    • error1.png
    • error2.png
    • empty_artboard.ai
    • psd_export.txt

    実行するスクリプト

    (function() {
      var doc = app.documents[0] ;
      var psdOptions = new ExportOptionsPhotoshop() ;
    
      try {
        doc.exportFile(new File('~/Desktop/psd_empty_artboard_error.psd'), ExportType.PHOTOSHOP, psdOptions) ;
      } catch(e) {
        alert('Caught error') ;
      }
    })() ;
    

    en_US

    When exporting Illustrator artboards to PSD using ExtendScript's exportFile, if the artboard does not contain valid PageItems, an error occurs and two alerts are displayed.

    
    

    The problem is that this error cannot be caught by a try syntax. It will stop the batch process with alerts.

    Also, if app.userInteractionLevel = UserInteractionLevel.DONTDISPLAYALERTS is used to prevent the alert, it is not possible to provide detailed information to the script user as to why the artboard was not exported.

    Ideally, the design should be changed so that the error can be caught, or even an empty artboard can be… more

    •  

    • 

    • 

    •  

    12 votes

    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

    Resolved (Comments Open)  ·  6 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. Illustrator JavaScript Scripting Reference.pdf Pages 46 (Documents Section)

    "ArtBoard" or "artBoard" ???? There must be consistency in capitalization
    [, numArtBoards]
    [, artboardLayout]
    [, artboardSpacing]
    [, artboardRowsOrCols])

    •  

    1 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. [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.

    3 votes

    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. 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

    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

14. [ExtendScript] Document.artboards wrongly returns artboards of active document

    1. MacOS 14.2.1
    2. Adobe Illustrator 28.0
    3. To reproduce:

    (a) open two documents with differently named artboards

    (b) run this script

    for (var i = 0; i < app.documents.length; i++) {
        for (var j = 0; j < app.documents[i].artboards.length; j++) {
            $.write(app.documents[i].name + ' artboard ' + j + ': ');
            $.writeln(app.documents[i].artboards[j].name);
        }
    }
    

    Expected result:

    demo1.ai artboard 0: ALPHA
    demo1.ai artboard 1: BRAVO
    demo2.ai artboard 0: CHARLIE
    demo2.ai artboard 1: DELTA

    Actual result:

    demo1.ai artboard 0: ALPHA
    demo1.ai artboard 1: BRAVO
    demo2.ai artboard 0: ALPHA
    demo2.ai artboard 1: BRAVO

    Note that Document "demo1.ai" is active. If I make demo2.ai active, I get this:

    demo2.ai artboard 0: CHARLIE
    demo2.ai artboard 1: DELTA
    demo1.ai artboard 0: CHARLIE
    demo1.ai artboard 1: DELTA

    Further links:

    • forum post

    1. MacOS 14.2.1
    2. Adobe Illustrator 28.0
    3. To reproduce:

    (a) open two documents with differently named artboards

    (b) run this script

    for (var i = 0; i < app.documents.length; i++) {
        for (var j = 0; j < app.documents[i].artboards.length; j++) {
            $.write(app.documents[i].name + ' artboard ' + j + ': ');
            $.writeln(app.documents[i].artboards[j].name);
        }
    }
    

    Expected result:

    demo1.ai artboard 0: ALPHA
    demo1.ai artboard 1: BRAVO
    demo2.ai artboard 0: CHARLIE
    demo2.ai artboard 1: DELTA

    Actual result:

    demo1.ai artboard 0: ALPHA
    demo1.ai artboard 1: BRAVO
    demo2.ai artboard 0: ALPHA
    demo2.ai artboard 1: BRAVO

    Note that Document "demo1.ai" is active. If I make demo2.ai active, I… more

    10 votes

    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

    6 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

15. Illustrator Version 28.7.1 - xmpfile does not have a constructor ( using Extendscript with Illustrator )

    OS: macOS Sonoma 14.6.1 (23G93)
    Illustrator version 28.7.1

    Prior to this update I have been able through extendscript to read XMP data from a file. After the update I get an error:
    
    "XMPfile does not have a constructor".
    
    on the line of code:
    var xmpf = new XMPFile(.........

    Reverting to the prior version resolves the issue.

    2 votes

    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
    Completed (Comments Open)  ·  AdminAkshaya Saxena (Admin, Adobe Illustrator) responded

    We have fixed this issue in 29.0 and 28.7.2 releases.

16. The ignoreWhite property of tracingOptions does not work

    Illustrator v 28.0 - Image Trace option check box for Ignore White has been replaced with Ignore Color and an eyedropper option. While I think this is a good addition for manual use, it appears to have somewhat broken the ability to use image trace properly in javascript as the change has made the original "tracingOptions.ignoreWhite = true" no longer work. I suspect there is now an additional option/variable responsible for the color to be ignored's selection but it doesnt appear to be refferenced in any of the current documentation. I've tried adding the method for Abutting (also undocumented) as to enable ignore white option. I've also tried to blindly implement an option for ignorColor to establish a color. but still can no longer use any script that depends on white being ignored from an image trace. This is a fairly sizable setback for my workflow which worked fine before the update. Any feedback on this issue (particularly if someone in the know can provide the options that now need to be set in a script for image trace to ignore white) would be greatly appreciated.

    Illustrator v 28.0 - Image Trace option check box for Ignore White has been replaced with Ignore Color and an eyedropper option. While I think this is a good addition for manual use, it appears to have somewhat broken the ability to use image trace properly in javascript as the change has made the original "tracingOptions.ignoreWhite = true" no longer work. I suspect there is now an additional option/variable responsible for the color to be ignored's selection but it doesnt appear to be refferenced in any of the current documentation. I've tried adding the method for Abutting (also undocumented) as… more

    • 

    10 votes

    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. Error with app.executeMenuCommand('Adobe Stroke Palette')

    en_US

    In the Japanese version of Adobe Illustrator, when I execute a script that selects the Window > Stroke menu, an error occurs. It executes correctly in the English (North America) version.

    

    Script to Execute

    try {
      app.executeMenuCommand('Adobe Stroke Palette') ;
    } catch(e) {
      alert(e) ;
    }
    

    Actual Result

    The following error occurs.
    
エラー: an Illustrator error occurred: 1346458189 ('MRAP')


    Expected Result

    Stroke panel is displayed.

    Steps to Reproduce

    1. Uninstall any non-Japanese version of Adobe Illustrator that is installed
    2. Launch Creative Cloud.app and set "Default install language" to Japanese in the Preferences
    3. Install and launch Adobe Illustrator
    4. Execute the script in the Script to Execute section

    Environment

    • macOS 12.6.7(Apple Silicon)
    • Illustrator 2019〜2024

    Not sure how long this issue has been present, but it is reproduced in Illustrator CS6.

    ---

    ja_JP

    日本語バージョンのAdobe Illustratorで ウィンドウ > 線 のメニューを選ぶスクリプトを実行すると、エラーが起こります。英語版English (North America)だと正常に実行されます。

    

    実行するスクリプト

    try {
      app.executeMenuCommand('Adobe Stroke Palette') ;
    } catch(e) {
      alert(e) ;
    }
    

    実際の結果

    次のエラーが起こる。
    
エラー: an Illustrator error occurred: 1346458189 ('MRAP')


    想定していた結果

    線パネルが表示される。

    再現手順

    1. 日本語版以外のAdobe Illustratorがインストールされている場合はアンインストールする
    2. Creative Cloud.appを起動し、環境設定で「初期設定のインストール言語」を日本語にする
    3. Adobe Illustratorをインストールし、起動する
    4. 実行するスクリプトセクションのスクリプトを実行する

    環境

    • macOS 12.6.7(Apple Silicon)
    • Illustrator 2019〜2024

    この不具合がいつからあるのかわかりませんが、Illustrator CS6でも再現します。

    en_US

    In the Japanese version of Adobe Illustrator, when I execute a script that selects the Window > Stroke menu, an error occurs. It executes correctly in the English (North America) version.

    

    Script to Execute

    try {
      app.executeMenuCommand('Adobe Stroke Palette') ;
    } catch(e) {
      alert(e) ;
    }
    

    Actual Result

    The following error occurs.
    
エラー: an Illustrator error occurred: 1346458189 ('MRAP')


    Expected Result

    Stroke panel is displayed.

    Steps to Reproduce

    1. Uninstall any non-Japanese version of Adobe Illustrator that is installed
    2. Launch Creative Cloud.app and set "Default install language" to Japanese in the Preferences
    3. Install and launch Adobe Illustrator
    4. Execute the… more

    •  

    10 votes

    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. AI 28.0 preferences corrupted by 28.1 with some 3rd party plugins

    When updating from Illustrator 28.0 to 28.1, some preference files may be corrupted if AI is running certain 3rd party plugins. These include any written with Hot Door's CORE and incorporating a WebView widget to display a web page, but I have received reports of this behavior with some SDK plugins as well.

    The problem it creates is that new files are not added to the File > Open Recent Files list, and any change to a different workspace is not saved.

    For my macOS Ventura with AI 28.1, deleting these preference files solved the problem: Plug-in Cache and plugincache.bin.

    For Windows 10 I had to also delete Adobe Illustrator Prefs and Adobe Illustrator Cloud Prefs.

    When updating from Illustrator 28.0 to 28.1, some preference files may be corrupted if AI is running certain 3rd party plugins. These include any written with Hot Door's CORE and incorporating a WebView widget to display a web page, but I have received reports of this behavior with some SDK plugins as well.

    The problem it creates is that new files are not added to the File > Open Recent Files list, and any change to a different workspace is not saved.

    For my macOS Ventura with AI 28.1, deleting these preference files solved the problem: Plug-in Cache and plugincache.bin.

    … more

    2 votes

    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

19. 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.

    6 votes

    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

20. app.preferences.setIntegerPreference() does not work

    app.preferences.setIntegerPreference("rulerType", 0) changes the selection in the GUI but doesn't actually apply the change to the document.

    I still have to go into the GUI preferences, change the units to something else, then back to inches and close for the change to actually apply to the current document.

    3 votes

    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