On pet 09.06.2017., at 14.59, Shane Stanley wrote:
> You will get that error if your app isn't correctly code-signed.
I tried with three signing identities (“Mac Development”, “3rd Party Mac
Developer Application” and “Developer ID Application”) and all three behave the
same. The application also does a lot of other things in accordance with
sandboxing rules/limitations and there weren’t any problems with operations
“not being permitted”. Executing "codesign --verify —verbose=4 —deep” and
"spctl -a -t execute -v” gives expected results ("valid on disk: satisfies its
Designated Requirement” and “accepted: source=Developer ID”), so I don’t think
the issue is related to code signing. I might be wrong though.
> Your app can't do that -- scripts can only be installed in that folder by the
> user.
I know that. What I meant by “installing" is getting scripts subfolder
(creating it if necessary), reveal it in Finder using NSWorkspace’s -openURL:
and ask user to drag particular icon (representing bundled script file) from
the application UI into revealed folder in Finder (the application has
"com.apple.security.files.user-selected.read-write” entitlement defined). It
all works fine if the scripts subfolder exists, it fails if the subfolder
doesn’t exist and I try to create it.
-- Dragan
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
