Assistive Access

Scripting Forums AppleScript | Mac OS X
#1

Could anyone kindly help with Assistive access?

• I have an AS app that runs dependably and consistently in Script Editor.
• I launch it directly I get the error that AA not allowed.
• Except that it is. The app is checked in Accessibility.
• The app talks to Filemaker and Acrobat which are also checked in Accessibility.

• It has run directly in the past under a different name, which brings up another question:
Why do I get the message for a different app? What I mean is, I’m running “My app” and the message is “My previous app is not allowed Assistive Access”.

• Also, when I try to add the new app to AA, it allows me to select it but it never appears in the AA list.

???

Any info would be very greatly appreciated.

Thanks.

#2

This thread doesn’t arrive at a solution, but may shed some light on the nature of the problem:

https://www.macscripter.net/viewtopic.php?id=46466

#3

It certainly doesn’t. But thanks.

I went through the process again. Deleted from the AA window, made a new AS app. Added it to AA. Same error.

I’m left wondering what the point of writing Applescript is if it’s never allowed to do anything.

It seems busted.

#4

Hi.

Does the script contain any persistent variables — ie. properties, globals, and/or variables set in the run handler? If so, these and their values will be saved back to the script file when the script finishes running, which will alter the file, which in turn will cause the Security system to treat the app with suspicion.

You may find these pages on Late Night Software’s site helpful:

Mojave brings in big security changes
Mojave and AppleScript Applets
Mojave and AppleScript Applets (discussion)

I always try to use local variables myself, putting all the code into ordinary handlers, where they’re local by default.

#5

LouK. After upgrading to Mojave, I experienced many of the same issues, and there doesn’t appear to be any easy fix. One script, which used properties and I ran with Fastscripts, required a complete rewrite to eliminate the properties. Another script simply would not run and oddly insisted on keeping its prior name in Accessibility. That one was easily fixed by a simple copy and paste from the old to a new script with a previously-unused file name.

Hopefully some of this will be fixed in the next version of Mojave. Sorry I don’t have an easy solution, but you have company.