<?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: Dropbox Core API on Android and startActivityForResult in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34476#M1053</link>
    <description>&lt;P&gt;The Sync and Core SDKs do handle the app authorization flow somewhat differently as you pointed out. I'll be sure to send this along as feedback, but for now we recommend implementing the authorization flow as shown in the &lt;A href="https://www.dropbox.com/developers/core/start/android#authenticating" rel="nofollow noreferrer"&gt;tutorial&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jun 2015 03:47:06 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2015-06-12T03:47:06Z</dc:date>
    <item>
      <title>Dropbox Core API on Android and startActivityForResult</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34475#M1052</link>
      <description>&lt;P&gt;I am trying to switch from SyncSDK to Core API. Everything going smoothly apart from your sample about picking up authentication result on &lt;CODE&gt;onResume&lt;/CODE&gt; method of the activity. Shouldn't Core API Android helper follow Android design pattern and deliver result to activity after calling &lt;CODE&gt;startActivityForResult&lt;/CODE&gt;? SyncSDK does this.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;onResume&lt;/CODE&gt; works too but it is unnecessary to keep checking authentication result whenever user opens my settings activity. &lt;BR /&gt;
Am I missing something?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:42:09 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34475#M1052</guid>
      <dc:creator>asi d.</dc:creator>
      <dc:date>2019-05-29T09:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: Dropbox Core API on Android and startActivityForResult</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34476#M1053</link>
      <description>&lt;P&gt;The Sync and Core SDKs do handle the app authorization flow somewhat differently as you pointed out. I'll be sure to send this along as feedback, but for now we recommend implementing the authorization flow as shown in the &lt;A href="https://www.dropbox.com/developers/core/start/android#authenticating" rel="nofollow noreferrer"&gt;tutorial&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2015 03:47:06 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34476#M1053</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2015-06-12T03:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Dropbox Core API on Android and startActivityForResult</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34477#M1054</link>
      <description>&lt;P&gt;Thanks very much for responding. I have implemented as in your tutorial but as I've stated above, handling response from authorization is not optimal and does not follow Android design pattern.&lt;/P&gt;

&lt;P&gt;I will wait for future updates&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2015 03:53:54 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-Core-API-on-Android-and-startActivityForResult/m-p/34477#M1054</guid>
      <dc:creator>asi d.</dc:creator>
      <dc:date>2015-06-12T03:53:54Z</dc:date>
    </item>
  </channel>
</rss>

