Skip to main content
Participant
January 7, 2026
Answered

Did ExportAllStories script break in InDesign 2026? (Mac running Sequoia)

  • January 7, 2026
  • 4 replies
  • 519 views

Background:  I have used the ExportAllStories applescript, and variations of the ExportAllStories applescript, since InDesign 2017 with no surprises.  I have not had any problem with it until today when I used it inside InDesign 2026. 

 

Context: I'm running Sequoia and InDesign 2026.  Does anyone know if Sequoia security somehow blocks the scripted export function of InDesign?  I know it's a long shot, but I cannot get any version of this ExportAllStories script to export an RTF or text file, and in addition, I cannot see why using scriptdebugger.... All its variables set up properly, I verified this, but the export function doesn't work.

 

Has anyone else experience this fail to export problem?

 

Thank you!

Correct answer Mike Witherell

I don't believe there have been any recent changes to AppleScript that will have affected this but

  forum.latenightsw.com

and

 www.macscripter.net

are fairly active if you find yourself stumped.

 

 


It was that change to POSIX that I recalled reading about. I think the way forward has been found.

4 replies

Mike Witherell
Community Expert
Community Expert
January 8, 2026

Not sure I recall correctly, but didn't I read lately that Apple has changed something fundamental about how AppleScripts work just this past year?

Mike Witherell
Participating Frequently
January 8, 2026

I think the problem is that InDesign now insists on POSIX file paths but the AppleScript version of this script is using HFS paths.

Participant
January 8, 2026

That is interesting, and I hope you're right:-)  I mean, it's something I can set right (or at least I think I can:-)  You folks have given me two more pointers to investigate and I appreciate your help a tremendous lot!  My last two days with Applescript were disappointing, but thanks to your suggestions, perhaps my horizons will begin to clear.  Thanks again.

Community Expert
January 8, 2026

Maybe it is an access permission issue. Try by providing "Full Disk Access" to InDesign. You can experiment by changing the export location as well

-Manan

-Manan
Participant
January 8, 2026

I had tried changing the export location with no change in results.  However, based on your suggestion, I added Full Disk Access to InDesign 2026 then my results changed.  The good news is the javascript version of the ExportAllStories appears to behave properly while the applescript version of the script still fails to export as before, without visible error.  The bad news for me is I know how to modifiy, and have modified the applescript version of the ExportAllStories script to meet my needs using scriptdebugger.  Unfortunately, I have not learned enough javascript to modify the javascript version so that it solves my export problem.  Thank you for your suggestion!  I am still stuck, but feel optimistic now that my problem is not my setup.  It appears InDesign's export function in applescript is broken in InDesign 2026.  Please correct me if you think I missed something, and thank you again for your help.

rob day
Community Expert
Community Expert
January 8, 2026

Have you tried the UXP version? It works for me using CC2025— its copyright date is 2022 vs. 2009 for the JS and AS versions .

rob day
Community Expert
Community Expert
January 7, 2026

Also the .jsx version works for me but the applescript throws this error:

 

Screen Shot 2.png

 

 

Participant
January 7, 2026

Hello Rob,

From inside InDesign 2026 with a single book file open, neither the applescript nor javascript versions of ExportAllStories display any error, and neither exports anything to my destination directory.  I wish it were otherwise, but I can't see what's not happening or why... Thank you for your help.

rob day
Community Expert
Community Expert
January 7, 2026

Hi @billbuchanan , Does the ExtentScript version (ExportAllStories.jsx) also fail? Do you get any alert dialogs telling you what line throws the error?