Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Using file revs in API 2
In API 1, whenever a file was uploaded, a file rev was provided in the meta-data's .rev property in the "did upload" delegate methods. In API 2, DBFILESFileMetadata has an equivalent .rev property - ...
Hmm, actually, looking more at DBFILESWriteMode, is the rev what you are supposed to pass into -initWithUpdate:?
So, e.g.:
NSString *rev = ... // rev cached from a previous upload or listFolder: result. DBFILESWriteMode *update = [[DBFILESWriteMode alloc] initWithUpdate:rev]; DBUploadTask *uploadTask = [self.dropboxClient.filesRoutes uploadUrl:dropboxPath mode:update autorename:@NO clientModified:localModDate mute:@NO inputUrl:localFileURL];
Is this correct, or is the rev added a different way?
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThat's correct.
Thanks. I think there's a minor documentation mistake in the DBFILESWriteMode.h file that is what makes this unclear. For -initWithUpdate:, it says this:
/// @param update Overwrite if the given "rev" matches the existing file's
/// "rev". The autorename strategy is to append the string "conflicted copy" to
/// the file name. For example, "document.txt" might become "document
/// (conflicted copy).txt" or "document (Panda's conflicted copy).txt".This is a duplicate of the paragraph above it which explains the purpose of the method. Presumably this paragraph should instead state that a file rev should be passed in as the update parameter. (Likewise in the documentation page on the site.) Because of this, I was looking elsewhere to find where I needed to input the "given 'rev'".
- Greg-DBI see, thanks for pointing that out!
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
