Objective-C API 2 - dealing with error codes

Hi Keith,

1. What you have already is the right way to start this, but you can continue drilling down into the error object, e.g.:

        [[client.filesRoutes createFolder:@"/test/path"] response:^(DBFILESFolderMetadata *result, DBFILESCreateFolderError *routeError, DBError *error) {
            if (result) {
                NSLog(@"%@\n", result);
            } else if (routeError) {
                NSLog(@"%@\n", routeError);
                if ([routeError isPath]) {
                    if ([routeError.path isConflict]) {
                        if ([routeError.path.conflict isFolder]) {
                            NSLog(@"Could not create folder because a folder already exists at path.");
                        }
                    }
                } // and so on for other errors
            } else if (error) {
                NSLog(@"%@\n", error);
            }
        }];

You can make your error handling as general or specific as you like this way.

2. Similarly, you can check the specific error returned to see if a delete call failed because nothing was found at the path, e.g.:

        [[client.filesRoutes delete_:@"/test/path"] response:^(DBFILESMetadata *result, DBFILESDeleteError *routeError, DBError *error) {
            if (result) {
                NSLog(@"%@\n", result);
            } else if (routeError) {
                NSLog(@"%@\n", routeError);
                if ([routeError isPathLookup]) {
                    if ([routeError.pathLookup isNotFound]) {
                        NSLog(@"Nothing found at path.");
                    } // and so on for other errors
                }
            } else if (error) {
                NSLog(@"%@\n", error);
            }
        }];

3. Yes, you can just use one or the other.

4. When using the SDK, you don't really need to worry about the actual HTTP error codes, as the SDK translates everything into objects and errors for you, like in the sample snippets above. For higher level errors, there's a good example here.

5. Attempting to upload to an over quota account will result in an route-specific insufficient space error. E.g., in the SDK that would look like:

        [[client.filesRoutes uploadData:@"/test/path" inputData:fileData]
          response:^(DBFILESFileMetadata *result, DBFILESUploadError *routeError, DBError *error) {
              if (result) {
                  NSLog(@"%@\n", result);
              } else if (routeError) {
                  NSLog(@"%@\n", routeError);
                  if ([routeError isPath]) {
                      if ([routeError.path.reason isInsufficientSpace]) {
                          NSLog(@"Could not upload because the account is over quota.");
                      } // and so on for other errors
                  }
              } else if (error) {
                  NSLog(@"%@\n", error);
              }
          }];

Hope this helps!