On Aug 18, 2011, at 21:24 , Sixten Otto wrote: > That method returns NO for failure, so I check the error... but it's nil. > There's nothing there to tell me what the heck is failing. (In fact, when I > wasn't initializing my error pointer to nil, it was left as a garbage > pointer, and crashed my app.) My app put the original file there, so > (presumably) that path is writable. The file manager does return true from > -fileExistsAtPath: for both files.
a. What version of iOS did this fail on? b. Can you assert that the receiver of the 'replace…' method is not nil? (If it was nil, the method call would behave exactly as you describe.) c. Can you show us the actual line of code that does the replacement? _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
