We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
V2 API's DbxFiles.WriteMode.update() does not created conflicted copy as promised
I am building a sync client based on the V2 API for Java. The documentation for update() states the following:
"If the rev of the file currently on Dropbox doesn't match revisionToReplace, Dropbox leave the original file alone and save your contents to a new file. For example, if the original file path is "/Notes/Groceries.txt", the new file's path might be "/Notes/Groceries (conflicted copy).txt"."
However, when I actually try this, no conflicted copy is created. The upload throws the following exception:
com.dropbox.core.v2.DbxFiles$UploadException: Exception in upload: UploadError.{".tag":"path","reason":{".tag":"conflict","conflict":{".tag":"file"}},"upload_session_id":"..."}
I could of course handle the conflict myself. But is there a way to make update() behave according to specs?
- Greg-DB
Dropbox Staff
Are you setting .autorename(true)? You'll need to do so for it to create the conflicted copy. By default, or if you set .autorename(false), it'll yield the error instead.
That did the trick (and now I also understand that part of the documentation). Thanks!
