This is a newbie question to get confirmation of what I have understood.
Could you please confirm that I get it right ?
I purchased Script debugger mainly to allow me to script Aperture, the old Apple photo editing software.
This worked OK until recently, most likely pre-Big Sur upgrade.
Aperture was a 32-bits application. In order to survive the upgrade to 64-bits mandatory status, some smart folks designed an application (called Retroactive) that could replace some 32-bits pieces in the Aperture code and turn it into a 64 bits application.
This went smoothly, prolonging Aperture life in the 64-bits world.
(note that there was no other way to launch the initial 32-bits Aperture anymore)
However, Aperture code having been modified, it is not the same application anymore, and as such is not notarised; and can’t be. Let’s call it ApertureNew.
ApertureNew is still scriptable and can respond to AppleScript events. It has a dictionary that can be displayed. You can still write code with Apple ScriptEditor program and it is functionnal.
With the advent of Big Sur, however, Apple Events needs to be authorized to operate.
By default, being an Apple application, ScriptEditor is authorized, (given maybe the System preferences “system events” authorization ), so this is not a problem. Apple Scripts continue to operate, including on ApertureNew.
However, with other applications relying on Apple events to control ApertureNew, such as Houdah Geo or Script Debugger, they must be explicitly authorized on ApertureNew to work as intended.
And this is were we hit the wall. ApertureNew being non-authorized, there is no way to authorize Script Debugger (or HoudahGeo, or whatever non apple app) 's apple events to control ApertureNew. No option to check in System Preferences/Security/ Confidentiality/Automation interface.
As a consequence, the same Applescript saved as a ScriptEditor document that would work to control ApertureNew, will not work if saved as a Script Debugger document. And cannot either be conceived inside Script Debugger for obvious debugging reasons and lack of dictionary/explorer feature.
So basically Script debugger has become useless for building scripts for ApertureNew.
Not because of Script Debugger fault, but because of Apple.
(Note that I have Script Debugger version 7, but I don’t think it makes a difference)
(Note further, this also applies to other applications 64-bits-enabled by Retroactive, such as iTunes or iMovie, and more generally to any non notarized application)