As I recall, under Lion I was able to use a script compiled as an .app as an action in a Mail rule; as of Mountain Lion, with scripts required to be placed in ~/Library/Application Scripts, applications are no longer recognized.
Sorry, I wasn’t clear. In Lion and previous, a script.app could be used as a Mail rule action. In Mountain Lion and Mavericks, that is no longer the case—Mail does not see the applet in ~/Library/Application Scripts/com.apple.mail, but does see script.scpt and script.scptd. Is this change documented? Would code signing the applet change this behavior?
application scripts must be in format .scpt oder .scptd.
Apple introduced application scripts to be able to run user scripts without restrictions from sandboxed applications.
The executing Cocoa class NSUserAppleScriptTask does not accept AppleScript applets and returns a The file “Applet” couldn’t be opened because it isn’t in the correct format.
error
Thanks, I suppose it doesn’t really matter. Script bundles give me pretty much what I wanted, anyway, except that I can’t get past the privilege violation error when I include an osax in the bundle.
Yup! My reason for deleting/moving the osax out of /Library/Scripting Additions (where it’s needed so Script Editor can see it) is to make sure that my script is using the bundled osax. It does appear to be, but each call to my osax-provided function now generates the privilege violation.