I figured it out. I was watching the session video Secure Automation Techniques in OS X when Chris Nebel got to the part about sending Apple Events from one app to another. His example uses com.apple.security.temporary-exception.apple-events instead of com.apple.security.scripting-targets. From the docs, it sounds like the first is older and the second is newer and preferred. But then the docs also say:
Note: Before you can use this entitlement, the scriptable app must provide scripting access groups. If it does not, you can still control the app, but you must use a temporary exception, as described in Apple Event Temporary Exception. So even though I provided the scripting access group for com.apple.finder, it didn't work. Either that or I used the wrong actions within that group. But nowhere does it list the actions Finder provides. "man 5 sdef" shows "access-group" as a way to provide entitlements to sandboxed apps, yet when I list the sdef for Finder.app (or iTunes.app, which is specifically mentioned in the video), I see no access-group anywhere. Mail.app (also mentioned in the video), however, *does* have such things. So this must be a new thing that they didn't feel the need to implement everywhere. In the end, I deleted the com.apple.security.scripting-targets entitlement and kept the com.apple.security.temporary-exception.apple-events. I can now trash the files, it makes the *krish* sound when the files land in the trash, and *I can go to Finder and Undo or Put Back exactly like I should be able to do*. -- Steve Mills Drummer, Mac geek _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
