This is a quick post for developers using ExtendScript Toolkit for scripting Creative Cloud applications.
Updated Friday, Nov. 30: Two workarounds are explained with step-by-step instructions in this article. You can now skip this article, unless you’re curious.
Updated Wednesday, Nov. 21: Fix added. See the “Workaround” section below.
Starting today, ExtendScript developers are reporting the following error when running scripts in ExtendScript Toolkit:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
We are aware of this problem and are investigating it.
Updated Friday, Nov. 30: Two workarounds are explained with step-by-step instructions in this article.
Updated Wednesday, Nov. 21: We’ve posted a fix in the forums. The fix is manual, but we’ve heard from a number of developers that it gets the job done.
- On Mac, open this file:
“/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800, and save
- Quit ExtendScript Toolkit and relaunch.
See the forum thread for further info on the root cause of the issue.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to Nov. 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
For updates regarding this issue, stayed tuned to this thread on the Adobe forums.
For more stories like this, subscribe to our Creative Cloud Developer Newsletter.