<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: V2 API's DbxFiles.WriteMode.update() does not created conflicted copy as promised in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133341#M3945</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Sat, 06 Feb 2016 04:46:02 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2016-02-06T04:46:02Z</dc:date>
    <item>
      <title>V2 API's DbxFiles.WriteMode.update() does not created conflicted copy as promised</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133340#M3944</link>
      <description>&lt;P&gt;I am building a sync client based on the V2 API for Java. The documentation for update() states the following:&lt;/P&gt;
&lt;P&gt;"If the rev of the file currently on Dropbox doesn't match &lt;CODE&gt;revisionToReplace&lt;/CODE&gt;, 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"."&lt;/P&gt;
&lt;P&gt;However, when I actually try this, no conflicted copy is created. The upload throws the following exception:&lt;/P&gt;
&lt;P&gt;com.dropbox.core.v2.DbxFiles$UploadException: Exception in upload: UploadError.{".tag":"path","reason":{".tag":"conflict","conflict":{".tag":"file"}},"upload_session_id":"..."}&lt;/P&gt;
&lt;P&gt;I could of course handle the conflict myself. But is there a way to make update() behave according to specs?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:36:07 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133340#M3944</guid>
      <dc:creator>Christoph L.2</dc:creator>
      <dc:date>2019-05-29T09:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: V2 API's DbxFiles.WriteMode.update() does not created conflicted copy as promised</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133341#M3945</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2016 04:46:02 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133341#M3945</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2016-02-06T04:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: V2 API's DbxFiles.WriteMode.update() does not created conflicted copy as promised</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133342#M3946</link>
      <description>&lt;P&gt;That did the trick (and now I also understand that part of the documentation). Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 07 Feb 2016 17:33:09 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/V2-API-s-DbxFiles-WriteMode-update-does-not-created-conflicted/m-p/133342#M3946</guid>
      <dc:creator>Christoph L.5</dc:creator>
      <dc:date>2016-02-07T17:33:09Z</dc:date>
    </item>
  </channel>
</rss>

