and yes, it was an error in the toPath, it was missing its first path
component.
And duh, the userInfo gives the offending path ..
On Apr 13, 2010, at 12:55 PM, Jens Alfke wrote:
On Apr 13, 2010, at 11:43 AM, Kevin Perry wrote:
It's referring to the source path. The documentation specifica
On Apr 13, 2010, at 11:43 AM, Kevin Perry wrote:
> It's referring to the source path. The documentation specifically states that
> no file should exist at the destination path. So, one can deduce that
> NSFileManager wouldn't report a "no such file" error if there was no file
> there
It would
On Apr 13, 2010, at 11:31 AM, k...@highrolls.net wrote:
> Using NSFileManager I get the error messaged referenced in the Subject Line.
> But, which is it referring to ... the copyItemAtPath or the toPath
Does the NSError’s info dict have a key that gives the offending path?
(If not, it should —
Not true. I did bool exists = [[NSFileManager defaultManager]
fileExistsAtPath:prefsrcpath];
on the source path and it returned true. I found the error though, my
destination path was in error!
-koko
On Apr 13, 2010, at 12:43 PM, Kevin Perry wrote:
It's referring to the source path. The
It's referring to the source path. The documentation specifically states that
no file should exist at the destination path. So, one can deduce that
NSFileManager wouldn't report a "no such file" error if there was no file
there, since that is what is expected.
-Kevin
On Apr 13, 2010, at 11:31
