Thanks for new info, but no, unfortunately, this NSURLIsWritableKey cannot discriminate between "not writable due to file permissions” and “not writable due to sandbox” cases. The both cases are "not writable" for the NSURLIsWritableKey.
I’ve found another workaround but not sure how reliable it is, because the bookmark data is an opaque object and its implementation is not clear. Namely, when I need to test a URL for writability, I create two bookmark datas from the url using the -[NSURL bookmarkDataWithOptions:…] method. The first is created with NSURLBookmarkCreationSecurityScopeAllowOnlyReadAccess option, and another one without it. Then I test whether the two NSData objects that I obtain are byte-by-byte identical (-[NSData isEqualToData:]), and if yes, then I assume this is a read-only bookmark. Otherwise, I assume this bookmark is writeable, from sandboxing point of view. The weak point of this method is the assumption that the obtained bookmark NSData is always identical if the path and its sandbox access mode do not change. I could theoretically get a false positive if I get a different NSData object while the url is still read-only. The false negative seems less likely (that I get an byte-by-byte identical NSData object while the URL is not read-only any more.) If I could be sure that bookmark data doesn’t involve any changeable data (like time stamps etc.), this could be a reliable method. Ideas? On Sat, Nov 9, 2013 at 6:04 PM, Mike Abdullah <mabdul...@karelia.com> wrote: > Does querying for NSURLIsWritableKey give you any more info? > > On 8 Nov 2013, at 16:31, Oleg Krupnov <oleg.krup...@gmail.com> wrote: > >> I’m trying to use -[NSFileManager isWritableFileAtPath:], but when it >> returns NO, I’d like to know if it’s “no” because the app simply >> doesn’t have access to this path due to sandboxing, or is it “no" >> because the file doesn’t have write permissions set in its file >> attributes? >> >> Is there a way to discriminate these two cases? >> >> Or more generally, is there a way to tell that an app does or does not >> have access to some file because of *sandboxing* (as opposed to file >> attributes)? >> >> Thanks! >> >> _______________________________________________ >> >> 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/mabdullah%40karelia.com >> >> This email sent to mabdul...@karelia.com > _______________________________________________ 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
