<?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: Polling for metadata changes results in conflict files in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Polling-for-metadata-changes-results-in-conflict-files/m-p/136460#M4207</link>
    <description>&lt;P&gt;That would certainly be unexpected from the metadata call. Are you making any other API calls around the same time?&lt;/P&gt;
&lt;P&gt;Also, are you sure this only happens when you're making this metadata call? Is it possible the people with the file are (perhaps not intentionally) saving new versions and causing the conflicts, unrelated to the API use?&lt;/P&gt;
&lt;P&gt;Conflicted copies can also occur when a file is left open on another computer, especially when using applications with an auto-save feature. Closing the file from within the application on either computer should prevent further conflicts.&lt;/P&gt;
&lt;P&gt;For more information on conflicted copies, see the Help Center article here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/help/36" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/help/36&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;One good thing to check would be the version history for the file(s) in question to see who and what client made the new versions:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/help/11" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/help/11&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Oct 2015 00:45:56 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2015-10-28T00:45:56Z</dc:date>
    <item>
      <title>Polling for metadata changes results in conflict files</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Polling-for-metadata-changes-results-in-conflict-files/m-p/136459#M4206</link>
      <description>&lt;P&gt;I'm using the Dropbox Ruby api to download the metadata for a specific file every five minutes. When I see the file's revision change:&lt;/P&gt;
&lt;P&gt;file_metadata = client.metadata(SOME_FILE_PATH)&lt;BR /&gt; current_revision = file_metadata['revision']&lt;/P&gt;
&lt;P&gt;I download the file, parse it, and then do something with that data.&lt;/P&gt;
&lt;P&gt;My issue is that if other people have that document open while I perform the above we end up with a bunch of "conflict" documents (i.e. Dropbox creates copies of the original document).&lt;/P&gt;
&lt;P&gt;I don't understand why this is happening since I am not modifying the document - all I do is download it. Am I missing something obvious?&lt;/P&gt;
&lt;P&gt;Thanks in advance!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:39:01 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Polling-for-metadata-changes-results-in-conflict-files/m-p/136459#M4206</guid>
      <dc:creator>Reed M.2</dc:creator>
      <dc:date>2019-05-29T09:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Polling for metadata changes results in conflict files</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Polling-for-metadata-changes-results-in-conflict-files/m-p/136460#M4207</link>
      <description>&lt;P&gt;That would certainly be unexpected from the metadata call. Are you making any other API calls around the same time?&lt;/P&gt;
&lt;P&gt;Also, are you sure this only happens when you're making this metadata call? Is it possible the people with the file are (perhaps not intentionally) saving new versions and causing the conflicts, unrelated to the API use?&lt;/P&gt;
&lt;P&gt;Conflicted copies can also occur when a file is left open on another computer, especially when using applications with an auto-save feature. Closing the file from within the application on either computer should prevent further conflicts.&lt;/P&gt;
&lt;P&gt;For more information on conflicted copies, see the Help Center article here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/help/36" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/help/36&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;One good thing to check would be the version history for the file(s) in question to see who and what client made the new versions:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dropbox.com/help/11" target="_blank" rel="nofollow noreferrer"&gt;https://www.dropbox.com/help/11&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2015 00:45:56 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Polling-for-metadata-changes-results-in-conflict-files/m-p/136460#M4207</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2015-10-28T00:45:56Z</dc:date>
    </item>
  </channel>
</rss>

