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
I do not understand what is going on with an application's sandboxed container
or Data directory.
NSHomeDirectory for an OS X sandboxed app points here.
~/Library/Containers/bundle_id/Data
The sandbox Data directory is pre-populated with items.
Data/Desktop (Alias)
On 23 Oct 2012, at 19:13, Richard Somers wrote:
I do not understand what is going on with an application's sandboxed
container or Data directory.
NSHomeDirectory for an OS X sandboxed app points here.
~/Library/Containers/bundle_id/Data
The sandbox Data directory is pre-populated
On Oct 23, 2012, at 1:29 PM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
The sandbox is intended to limit what an *app* can do by itself, not what a
*user* can do. Users are free to save things wherever they like; the only
entitlement that plays a role in that is
On Tue, Oct 23, 2012, at 01:05 PM, Richard Somers wrote:
On Oct 23, 2012, at 1:29 PM, Mike Abdullah cocoa...@mikeabdullah.net
wrote:
The sandbox is intended to limit what an *app* can do by itself, not what a
*user* can do. Users are free to save things wherever they like; the only
On Tue, 23 Oct 2012 12:13:31 -0600, Richard Somers said:
~/Library/Containers/bundle_id/Data
*SNIP*
A lot of this simply does not make sense. What am I missing?
Are you aware that, by default, all of ~/Library is hidden from the user, and
it's basically expected that he won't go in that
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
