Big Sur – Script no longer works

Hi, i also have the same problem.

I develop Applescript scripts for InDesign that worked in Catalina (on my old MacBook Pro and computers clients) but stopped working on Big Sur (on a new MacBook Pro M1) with the same error as you (Unable to send Apple events to Finder) and the same settings in Security & Privacy > Automation (no InDesign as source and no Apple Events or Finder as target, as my settings in Catalina).

However, those scripts are working if launched inside Script Debugger.

And yesterday i had the same problematic experience with a client iMac with Big Sur. Until then i thought it might be a problem with the Security & Privacy database that could be solved by resetting it (i didn't try it for now), but now i doubt it could be the solution as the same problem arise in at least three different configurations, with Big Sur involved in all three…

To be precise, as i have access to the code of my scripts, the bits that block the execution of the scripts are tell blocks for System Events and Finder (for exemple to get the system user name or getting all files in a folder by file type, move them, etc.). Scripts without those tell blocks launch and work fine inside InDesign… But of course i need them…

What i have understood: what is missing is that at the first launch of the script in a source app, that app should trigger a popup dialog asking you to authorise it to control whatever target app the script needs. It happened when i launched the first script inside Script Debugger on my new computer (it asked for System Events, Finder and InDesign). After that, Script Debugger as source and System Events, Finder and InDesign as targets were added to the Security & Privacy > Automation panel. The thing is that InDesign do not trigger those dialogs and i can't see another way to do it.

So, is it a ponctual glitch in those 3 configurations (yours, mine and my client's) that can be corrected or a general bug with InDesign/Big Sur/Applescript that must be fixed by editors (Apple, Adobe) ?

For now i had to install the editable script on my client computer with a demo version of Script Debugger and instructed him to launch the script form here. Not future proof to say the least…

Thanks for any advice on that matter,

Vincent

I'm no expert on this, but you could try adding Script Editor.app to Full Disk Access. Whether this is an acceptable security risk you must decide yourself. (If it works for you, that is!)