Re: Trying to understand a permissions failure when writing to ~/Desktop
Re: Trying to understand a permissions failure when writing to ~/Desktop
- Subject: Re: Trying to understand a permissions failure when writing to ~/Desktop
- From: Kyle Sluder <email@hidden>
- Date: Wed, 27 Jan 2016 22:07:31 -0600
On Wed, Jan 27, 2016, at 09:57 PM, Graham Cox wrote:
> Well, the OS definitely believes the app is sandboxed. The full URL I get
> for ~/Documents/ is in fact ~/Library/Containers/<bundle id>/…. blah blah
>
> I did a clean build and changed the bundle ID as well as discarding the
> container, but no, it just makes a new container with the new bundle ID.
> This is exasperating, I can’t see where it could be getting such a notion
> from.
>
> Sandboxing is OFF in Xcode’s ‘Capabilities’ section, and AFAICS no
> .entitlements file is added to the build. Th eonly ‘funny’ I have in my
> info.plist is an entry for NSUbiquitousContainers, since I wanted to
> allow access to the user’s iCloud documents. I thought that setting
> allowed this without sandboxing, not that it snuck sandboxing in by the
> back door. I will check and see whether that’s a red herring.
Any app on OS X can open documents from iCloud Drive—the user just has
to navigate to iCloud Drive in Finder.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden