On Tue, Jan 31, 2012 at 7:21 AM, April <developm...@fornextsoft.com> wrote: > Thanks a lot for the reply. > When it is not using iCloud everything works like a dream. It all functions > exactly as expected. I only get the permission error with autosave and > iCloud. I have reached a point where if I use writeSafely: etc... it will > save to iCloud, but I cannot use autosave, I have to set up a timer to fire > every x seconds and save if there are changes.
Okay, that doesn't sound normal to me. If you're able to write to to the ubiquity container using -writeSafelyToURL:, but not using a higher-level function like -saveDocument:, then you should really investigate anything custom that you're doing. - What other NSDocument methods have you subclassed? - If you wrap the -writeSafelyToURL: call in the appropriate NSFileCoordinator methods, does it fail with the same error? (You might want to try this from a Foundation tool rather than within your NSDocument-based app.) - Can you confirm that the file is actually getting pushed to the cloud? - What does ~/Library/Logs/Ubiquity/$USER/ubiquity.log say? You can increase the logging verbosity using the ubcontrol(1) command. --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
