The answer, if anyone else is thinking of answering this question, is to use
NSFileWrapper - ensuring that "Document is distributed as a bundle" is
unchecked for the folder that you generate.
Simples. And my apologies to all here for not investigating further before
posting a question.
On 18 Sep 2013, at 20:54, Pax <45rpmli...@googlemail.com> wrote:
> Okay, the plot thickens. I've now updated my app for the app store -
> sandboxing is now enabled. Sandboxing breaks the save path modification,
> and particularly my creation of a folder:
>
> if(![fileManager createDirectoryAtPath:directory
> withIntermediateDirectories:NO
> attributes:nil
> error:&error])
> {
> NSLog(@"Failed to create directory \"%@\". Error: %@ - this
> save will most likely fail entirely.", directory, error);
> }
> else
> { ... }
>
> With sandboxing enabled, the creation of the directory always fails - unless
> the user opts to save in the Downloads directory. Most odd.
>
> The user can choose to save an undecoded version of the file wherever they
> like. I have set read/write access for the Downloads Folder - which probably
> explains this. How can I get read/write access to wherever the user chooses
> to extract the files (most likely Documents, loose in their home folder, or
> the desktop?)
_______________________________________________
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
