AppleScript Release Notes

alldritt · December 31, 2022, 1:37am

Ventura - macOS 13

nothing reported

nothing reported

nothing reported

To enhance security, AppleEvents and AppleScripts that target an app on a remote system must authenticate as the same user on the remote system. An AppleEvent that targets an app running as a different user receives a procNotFound error. To allow remote AppleEvents to target apps in any user session, run the following command in Terminal on the server:

defaults write /Library/Preferences/com.apple.AEServer RestrictAccessToUserSession -bool false

Then disable and reenable Remote Apple Events in System Preferences > Sharing. (5353592)

Sending Apple events from an app—including script applets—now requires user approval. The list of currently approved apps can be viewed and edited in the Automation category in the Privacy tab in System Preferences > Security & Privacy. If an event is blocked because the user didn’t approve that app, the event will fail with the error code: -1743 (": Not authorized to send Apple events to "). An event can be preflighted using AEDeterminePermissionToAutomateTarget(_:_:_:_:).
Scripting additions can no longer be globally installed. The /Library/ScriptingAdditions, /Network/Library/ScriptingAdditions, and ~/Library/ScriptingAdditions directories are effectively ignored. Distribute scripting additions as part of a specific app by embedding the scripting addition in the app’s Contents/Resources/Scripting Additions directory and signing both the addition and the app with the same team identifier.