Workaround for ExtendScript Toolkit Debugger Error #1116

Ash Ryan Arnwine
Nov 30, 2018 · 5 min read

Updated Monday, Feb. 25: An ExtrendScript Debugger for Visual Studio Code is now available in the Visual Studio Code Marketplace. Read more about it.

Last week, I wrote to let you know about a sudden error that started occurring for ExtendScript Toolkit users on Mac. In that post, I linked to one of a few places where Adobe staff like Bruce Bullis and Erin Finnegan were working with the community to diagnose the issue and establish workarounds.

ExtendScript Toolkit Error #1116

Since then, the community has come to a consensus on how to fix the issue. In this post, I’ll share two ways to accomplish the fix, and you can choose the one you prefer.

First, a big thank you

We appreciate the community of developers, scripters, and Adobe Community Professionals (ACPs) that rallied around the issue and discovered the various workarounds we’ve seen.

In particular, I’d like to acknowledge Japan ACP Ten A and Japan Forum MVP monokano for their work on explaining the situation and providing easy-to-use fixes.

Option 1: Edit the JSX file directly

This option, which is almost a word-for-word rewrite of Ten A’s excellent walkthrough on the Japanese forums, will have you edit the errant JSX file within ExtendScript Toolkit directly.

The fix is simple, and involves deleting three s from a single value in a single file.

[1.] Make sure to quit ExtendScript Toolkit on your Mac.

[2.] Open the ExtendScript Toolkit package.

In your Applications folder, right-click on the app name and select “Show Package Contents”. This will open the app’s Contents folder in the Finder.

[3.] Navigate to and open the file.

The path to the file will look something like this in the Finder:

Open the file in an app other than ESTK by right-clicking on the file name and selecting Open with… > [Editor name]. If you aren’t sure which app to use, go with TextEdit.

[4.] Use your text editor’s Find and Replace tool to search for the value .

It will be the value assigned to . There is only one instance of this exact number in the file.

[5.] Delete the final 3 s from the value, resulting in .

This value is meant to specify the number of seconds in a week, which is 604,800.

[6.] Save the file, relaunch ExtendScript Toolkit, and run a script.

At this point, you should no longer see Error #1116 when you run a script.

Option 2: Use in the command line

If you’re comfortable working with the command line, the same thing can be accomplished much more quickly with . The steps explained below are inspired by Ten A's original blog post in Japanese.

Note that the commands below assume you have ExtendScript Toolkit installed in the default location. If you have it installed in a custom location on your machine, you’ll need to revise the commands accordingly.

[1.] Make sure to quit ExtendScript Toolkit on your Mac.

[2.] Open Terminal (Applications > Utilities > Terminal).

[3.] Run the following command to create a temp file with the fix*:

sudo sed s/604800000/604800/g /Applications/Adobe\ ExtendScript\ Toolkit\ CC/ExtendScript\ > /Applications/Adobe\ ExtendScript\ Toolkit\ CC/ExtendScript\

[4.] Run the following command to replace the original file with the temp file:

mv /Applications/Adobe\ ExtendScript\ Toolkit\ CC/ExtendScript\ /Applications/Adobe\ ExtendScript\ Toolkit\ CC/ExtendScript\

At this point, you should no longer see Error #1116 when you run a script.

How to stay in touch

We want to make sure you’re able to stay in touch with us to get the latest news from the CC developer platform and ecosystem.

All the latest CC developer news

  1. Sign up for the CC Developer Newsletter
    We started the CC Developer Newsletter in stealth mode a few months ago, and it’s getting a great response from the developers who have early access. Sign up to get monthly updates about CC APIs, developer tools, events, and more.
  2. Follow the Adobe Tech Blog
    We post content for CC developers on this blog at least once a week, approaching 50 articles for this year so far. Follow the blog to make sure you get the latest info.

Prerelease programs

To get early information on CC products along with their related APIs and developer tools, our various prerelease programs are the place to be.

Go to and sign up for the prerelease programs that relate to what you’re working on.

The future of ExtendScript Toolkit

ExtendScript Toolkit has been a hot topic in the CC developer community for some time now. While a bug like the one described in this article makes it seem otherwise, we have heard you loud and clear that developer tools for ExtendScript are still incredibly important to you.

As many have guessed, a new version of ExtendScript Toolkit is not in the works. However, we have something coming up for you that will replace ESTK for many of its most popular use cases.

Earlier this year, we gave a brief overview of our plans to a room of CC developers at Creative Developers Summit, but since then, we haven’t been communicative enough about our plans and progress.

We’ll be back on this blog soon to share more information.

*If you get a password prompt, you’ll need to enter the admin password for your Mac (note that the password won’t show up as you type). If this doesn’t work, it may be that you’re not an administrator of your computer (for example, your computer is managed by your workplace). In that case you’ll need to get someone with admin privileges to help out.

For more stories like this, subscribe to our Creative Cloud Developer Newsletter.

Adobe Tech Blog

News, updates, and thoughts related to Adobe, developers…