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 (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
