Hi we got plenty of script in our workflow, and since the 25.1 update the scripts no longer work. (Was working in 25.0.1)
They all have 1 thing in common,
tell application "Adobe Illustrator"
Nothing works and i'm resulted with:
Whatever is inside the quotes, nothing works, we always get the missing value as as result
Thank you for your help!
I might be wrong, just a guess, but could it be Apple's security sandboxes? Make sure the System Preferences are set up to allow the AppleScript to control Illustrator etc... - I've not studied this in detail, but more recent versions of Mac OS X are very picky in what they allow. I'd have a look in 'System Preferences - Security' and make sure allowance is made for the script to control Illustrator. I think it might be under 'Automation'.
Thank you for your Answer,
It might have been a good idea, i've wiped the automation preferences to start from scratch.
I Executed the scripts, it asks me to give permission, I do and the script just don't execute.
I'm unable to use the commands 'export' and 'embed' since the update for what it's worth
haven't tried 'embed' but just also realised 'export' isn't working anymore – were you able to fix it? I went back to 24.3 because of that...
No nothing have worked so far,
I reverted back to 25.0.1
I'm back on 25.0.1 too - hoping it's fixed in the next update
I have spotted a link which has a workaround somebody made which may or may not help here:
Restart your computer, reset Automation security settings, and run your scripts afresh is good basic troubleshooting advice, but it doesn’t sound like that’s the cause.
I’ve not touched AI’s AppleScript interface in over a year (recent projects have all been in JSX), so haven’t been following exactly what’s changed and when, but this may be related (“foo” is me):
Basically, the Illustrator application dates back to Mac OS 7 days, and some parts of its guts use pre-OSX, pre-sandboxing, macOS-defined datatypes and APIs (e.g. Carbon Alias and File Managers) that Apple has long since deprecated and will eventually phase out. Therefore Adobe needs to replace old AI code that uses those old, dying APIs with new code that uses modern, supported macOS APIs. Unfortunately, AppleScript, being another System 7-era technology and long neglected by Apple, is still using some of those old dying datatypes itself, and while it supports some (though not all) of the newer types this support is kludgy, inconsistent, worryingly brittle, appallingly documented. Plus, half of these datatypes don’t play well with the other half.
Now add some current AI engineers, who probably have little-to-no familiarity with AppleScript or Illustrator’s support for it, typing to upgrade neglected quarter-century old code so that it works well with modern macOS sandboxing, and a small but ardent base of heavy AppleScript users who rely on this whole house of cards to keep on working while all this chop and change is going on.
I did observe at the time that while the old AppleScript “file specifier” type still in use in some parts of AI (e.g. “file path” properties) was horrendously obsolete and long overdue for replacement, but using plain old strings to describe file system paths was a really bad idea, precisely because there’s no 100% reliable way to distinguish a string specifically describing a file path from a string that contains any old text. (This is the whole reason for having different datatypes in the first place.) Plus, the way that AppleScript performs string↔︎file type coercions (badly, inconsistently, and non-reversibly) means that older AppleScripts that used “file-like” objects would break where path strings are now expected, and vice-versa.
To be clear, even if the above is the cause of the problem (which it may or may not be), this is Apple’s fault for running AppleScript into the ground over the last 15 years, not Adobe’s for trying (and failing) to make the resulting confusion work. Honestly, I’ve built the most advanced Illustrator automation on the planet, and I did using AI’s AppleScript interface (though not AppleScript itself) because when it works it is incredibly powerful, elegant, and a pleasure to work with (much nicer than JSX!). And even I’m counting the days till Adobe ships UXP for Illustrator now, as AppleScript infrastructure looks increasingly like a bitrotten liability, not a platform on which to build a future.
TL;DR: Working with files in AppleScript is a nightmare, period, and not getting any better.
You seems like a script expert to me!
Our scripts are launched from our internal system, and the only use of AppleScript is
tell application "Adobe Illustrator"
I'd be happy to part ways from applescript but I did not find any solutions.
Alas, Adobe’s Creative Cloud app insists my installed copy of AI 25.0 is the latest version available to me, so I’m unable to upgrade to test it myself.
1. The most obvious solution, assuming this is in-house only, is to revert to an earlier version of AI that you know works (the CC app allows you to install multiple/older versions), file a bug ticket with Adobe describing previous and current behaviors, with test scripts/screenshots/error messages/etc to help them understand the issue, and hope they fix it before your next upgrade.
3. If you’re looking for an alternative anyway, the AppleScript interface is not the only way in. Depends on what you’re trying to achieve and how far you’re willing to go to achieve it. There’s the C++ SDK, of course, but I doubt you want to deal with that. Perhaps the CEP/Adobe Bridge users here can provide some suggestions? (I haven’t looked at how Bridge itself communicates with other Adobe apps.)
I do remember one enterprising AI engineer stuffing a Node-based webserver into a CEP panel:
(Needless to say there are security issues to consider when running any sort of webservice on a desktop; limiting client connections to localhost being an obvious start.)
And once UXP does ship for AI, who knows what options will be available then? Though it’ll be another year (or two, or three?) before we get that.
I really don't understand the concept of using an AppleScript API without using AppleScript?
Ok - but what a shame, AppleScript is not well-documented but it's somewhat like AutoHotKey - at least there's users from 2005 who have answered most pertinent questions and people who seek can find - eventually. And now you say, in addition to the technical knowledge challenges, it's internal support is lacking? That's too bad as Apple keeps making faster and faster machines so users can hurry up and manually do tasks super-fast but manually and taking days and days. But each individual thing is super fast and shiny! But it will take months.. But it's shiny, new apps!
I am wondering if Apple will do something about its own automation, from the looks of it I would recommend Windows setups to people and be very conservative about analyzing and taking on AppleScript work if any comes up...
Python3 + appscript (appscript.sourceforge.net), which I wrote after getting sick of dealing with AppleScript. Basically what JXA should’ve been (in addition to Apple’s answer to Node), had Apple’s Mac Automation team been run by a competent manager, but it failed so hard Apple scrapped that entire department in 2016. Whatever the future of Apple automation may be, it lies with the Siri/Shortcuts team now.
Can you elaborate on how you used AI's AppleScript interface but not AppleScript itself?
I to am having issues using my Applescripts. I have been using my particular ApleScript for over 6 years with no issues. The issue began with the 25.1 update this morning whith script to starting to fail. It worked correctly with 25. Also I am still using Mojave, so it it is not related to a new Operating System. If I try to use the script with in an Illustrator Action I will get a message "Adobe Illustrator got an error: missing value doesn't understand the "concentrate rotation matrix" message. If I run the script out of the Applescript dropdown, the message doesnt come out but it has the same result. It does all of it's funtion except there is a rotate at the end and it doesnt do that part. I have three friends that use this script and they too are now now getting this Issue.
Yeah i'm also on Mojave nothing else changed except update to 25.1,
I've reverted back to 25.0.1 and it's working, there is definitely something wrong in this version
Getting a similar issue with Illustrator 2021, but with the export command. "Adobe Illustrator got an error: current document doesn’t understand the “export” message."
seems like a very basic command to be broken
Copy link to clipboard
It has been fixed in 25.2 Beta
If you have any ideas as for why this isn't working for me that would be great.
I'm no Applescripct expert so I can't really help you on this,
Is your script working on 25.0? I would start there
After Illustrator's last update 25.2, all of my scripts are behaving like well manored children again. Thanks Adobe Team.