On 23 Oct 2012, at 23:06, Richard Somers wrote: > On Oct 23, 2012, at 2:43 PM, Kyle Sluder <k...@ksluder.com> wrote: > >> If by "unapproved" you mean "my app's sandbox hasn't been extended to >> include this path" then you are incorrect. The user can choose the >> destination, and the NSURL you get back from the open panel will carry >> the rights to access that location. >> >> If by "unapproved" you mean "the user my app is running as doesn't have >> write permission to this location", then yes that is expected behavior. > > I sandboxed my app in Xcode. In the app target entitlement area there are > access control options for Music, Movies, Pictures, and Downloads folders. > Access to these folders remained the default "No Access". I launched the app > and and saved a new document. In the save panel the Music folder was showing > as a Recent Place. I selected this as the save location and saving was a > success. As a developer, based on the entitlement settings, I was expecting > failure.
If the user can get to it in a save panel, that should override anything else your app has setup. Any other way would be madness. > > Saving a new document to the users home directory (choose the home directory > in the save panel) resulted in failure. "The document could not be saved. You > don't have permission." As a developer this is what I expected. From a users > point of view I was surprised that the save panel let the user choose a > location where a save was not allowed and subsequently would result in > failure. This is the surprising bit. You do have the com.apple.security.files.user-selected.read-write entitlement set, yes? _______________________________________________ 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
