<?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 Syncing on Background - Best Practice in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Syncing-on-Background-Best-Practice/m-p/3226#M117</link>
    <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I'd like to implement simple sync functionality into my App. The goal is to read JSON data from file (On Dropbox) and update my SQLite data and vice versa. Users must be allowed to use App during sync process. I consider to use Dropbox Sync API and call syncing from (Intent)Service.&lt;/P&gt;

&lt;P&gt;I see a few problems which could appear:&lt;/P&gt;

&lt;P&gt;1.) App is minimized (paused) while syncing&lt;BR /&gt;
 2.) App is closed (killed) while syncing&lt;BR /&gt;
 3.) In some cases, sync scenario needs User input (for example: "Do you want to replace data in your device?" dialog)&lt;/P&gt;

&lt;P&gt;Is there any "Best practice" or recommendation how to implement this functionality? It would be greatly appreciated if somebody could help with this problem.&lt;/P&gt;

&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:46:53 GMT</pubDate>
    <dc:creator>Check S.</dc:creator>
    <dc:date>2019-05-29T09:46:53Z</dc:date>
    <item>
      <title>Syncing on Background - Best Practice</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Syncing-on-Background-Best-Practice/m-p/3226#M117</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I'd like to implement simple sync functionality into my App. The goal is to read JSON data from file (On Dropbox) and update my SQLite data and vice versa. Users must be allowed to use App during sync process. I consider to use Dropbox Sync API and call syncing from (Intent)Service.&lt;/P&gt;

&lt;P&gt;I see a few problems which could appear:&lt;/P&gt;

&lt;P&gt;1.) App is minimized (paused) while syncing&lt;BR /&gt;
 2.) App is closed (killed) while syncing&lt;BR /&gt;
 3.) In some cases, sync scenario needs User input (for example: "Do you want to replace data in your device?" dialog)&lt;/P&gt;

&lt;P&gt;Is there any "Best practice" or recommendation how to implement this functionality? It would be greatly appreciated if somebody could help with this problem.&lt;/P&gt;

&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:46:53 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Syncing-on-Background-Best-Practice/m-p/3226#M117</guid>
      <dc:creator>Check S.</dc:creator>
      <dc:date>2019-05-29T09:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: Syncing on Background - Best Practice</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Syncing-on-Background-Best-Practice/m-p/3227#M118</link>
      <description>&lt;P&gt;If you're using the Sync API, you should work through the tutorial to see how it's recommended apps use the API to upload and download files, use listeners, etc.:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://www.dropbox.com/developers/sync/start/android" rel="nofollow noreferrer"&gt;https://www.dropbox.com/developers/sync/start/android&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Alternatively, you can use the Core API, which may be more straightforward if you just need to upload/download a single file:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://www.dropbox.com/developers/core/start/android" rel="nofollow noreferrer"&gt;https://www.dropbox.com/developers/core/start/android&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2014 06:29:35 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Syncing-on-Background-Best-Practice/m-p/3227#M118</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2014-12-16T06:29:35Z</dc:date>
    </item>
  </channel>
</rss>

