Others have written up more extensive information about this: streamlined automation requires some type of mechanism to have the permissions granted a priori an example would be utilizing AppleScript with Ansible and being unable to preload grants.
the implementation of requesting permission for the scripting action appears to be bugged I've run other scripts that request permission to send events to Safari and the Finder doesn't prompt for permission, it just returns an error.There's two issues that I see at the moment:
Step 3: Search for Adobe Digital Editions 4.5.4 in the /Applications folder, then drag its icon to the Trash icon located at the end of the Dock, and drop it there. Step 2: Launch Finder on your Mac, and click Applications in the Finder sidebar. If you allow it, then terminal will get added to the Automation page in System Preferences > Security & Privacy > Automation: Step 1: Quit Adobe Digital Editions 4.5.4 as well as its related process (es) if they are still running. What is supposed to happen on the first execution is the Finder opens a dialog box informing you that terminal is requesting permission to send events to the Finder. In terminal try osascript -e 'tell application "Finder"' -e 'set _b to bounds of window of desktop' -e 'end tell'Īnd you may receive: 36:42: execution error: Not authorized to send Apple events to Finder. If you have issues opening or downloading a book, you can try deauthorizing Adobe Digital Editions, and then authorize it again. This is definitely a part of Mojave's new security framework.
0 kommentar(er)
