Though it's definitely not an ideal solution, manually removing the container corresponding to the application's bundle identifier in "~/Library/Containers", and then relaunching the application causes the corresponding Application Scripts subfolder to get created.
Thinking more about it, I realise the API for creating the subfolder would probably not be consistent, especially since the application is granted just read-only access to the scripts subfolder, but it would really be useful if the subfolder is created (if it doesn't exist) the next time the application launches regardless of whether corresponding container folder exists or not. For now I can only hope users won't manually mess with folders "hidden" inside "~/Library", so this won't be a big issue. If the fourth parameter is "NO", only the plain file-path URL is returned, which can't be revealed (as the subfolder doesn't exist) and the application does nothing as a result of user action. Therefore I will set the fourth parameter to "YES". That way, users will be presented with an error at least, and if they report it I'll know what the issue is and how to fix it. -- Dragan _______________________________________________ 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
