We Want to Hear From You! What Do You Want to See on the Community? Tell us here!
Forum Discussion
Solved
Creating a folder that already exists (iOS)
I went through this already for Android, and I learned that to create a folder that might already exists I only need to check the exception as follows:
catch (CreateFolderErrorException err) { if(...
In this case, you'd get a DBFILESCreateFolderError in your cfError variable, containing a "conflict" DBFILESWriteError in the path field.
Here's an example of how you'd detect the different error cases, picking out the conflict error:
[[client.filesRoutes createFolder:@"/testfolder"] response:^(DBFILESFolderMetadata *result, DBFILESCreateFolderError *cfError, DBError *error) {
if (result) {
NSLog(@"Create folder succeeded:");
NSLog(@"%@", result);
} else {
NSLog(@"Create folder failed:");
if (cfError) {
NSLog(@"The error is a create folder error.");
if ([cfError isPath]) {
NSLog(@"The error is a path error.");
if (cfError.path.isConflict) {
NSLog(@"Couldn't create folder because there was something in the way.");
} else {
NSLog(@"Other create folder path error:");
NSLog(@"%@", cfError.path);
}
}
} else if (error) {
NSLog(@"The error is a generic error.");
NSLog(@"%@", error);
}
}
}];(Apologies for the poor formatting.)
Thanks Gregory. I had just figured out something like that from the comments in the Dropbox header files (more useful in this case than the HTML docs) and was just about to post something like that:
if(cfError) {
if((cfError.isPath) {
DBFILESWriteError *werr = cfError.path;
if(werr.isConflict) {
NSLog(@"--This error can be safely ignored--");
}
}
}
But I wonder what would happen if there is a "conflict", not because the folder already exists in Dropbox, but because a FILE by that name already exists in Dropbox. Obviously such an error should not be ignored. But will such an error distinguish itself from the folder already existing condition?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
