<?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 Short-lived tokens: iOS vs Android in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Short-lived-tokens-iOS-vs-Android/m-p/480871#M24263</link>
    <description>&lt;P&gt;After having successfully migrated my app in both the Android and the iOS platform, I am curious about something.&amp;nbsp; Why were the changes for Android so much more complicated than the changes for iOS?&amp;nbsp; For Android, I had to handle persisting the string version of a new DbxCredential object and still create a new DbxCredential object with a refresed token on every session.&amp;nbsp; And of course the linking to Dropbox required a new API call, Auth.startOAuth2PKCE, giving it scope parameters.&amp;nbsp; With iOS, the only change necessary was the new initial linking API to provide the option of scope parameters.&amp;nbsp; There was no messing around with creating a new credential object.&amp;nbsp; The token refreshing seems to be taken care of completely in background.&amp;nbsp; So my question is, what is so different between these two operating systems that the migrated Dropbox API for Android could not be as simple as it was for iOS?&lt;/P&gt;</description>
    <pubDate>Mon, 21 Dec 2020 11:28:43 GMT</pubDate>
    <dc:creator>Robert S.138</dc:creator>
    <dc:date>2020-12-21T11:28:43Z</dc:date>
    <item>
      <title>Short-lived tokens: iOS vs Android</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Short-lived-tokens-iOS-vs-Android/m-p/480871#M24263</link>
      <description>&lt;P&gt;After having successfully migrated my app in both the Android and the iOS platform, I am curious about something.&amp;nbsp; Why were the changes for Android so much more complicated than the changes for iOS?&amp;nbsp; For Android, I had to handle persisting the string version of a new DbxCredential object and still create a new DbxCredential object with a refresed token on every session.&amp;nbsp; And of course the linking to Dropbox required a new API call, Auth.startOAuth2PKCE, giving it scope parameters.&amp;nbsp; With iOS, the only change necessary was the new initial linking API to provide the option of scope parameters.&amp;nbsp; There was no messing around with creating a new credential object.&amp;nbsp; The token refreshing seems to be taken care of completely in background.&amp;nbsp; So my question is, what is so different between these two operating systems that the migrated Dropbox API for Android could not be as simple as it was for iOS?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 11:28:43 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Short-lived-tokens-iOS-vs-Android/m-p/480871#M24263</guid>
      <dc:creator>Robert S.138</dc:creator>
      <dc:date>2020-12-21T11:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: Short-lived tokens: iOS vs Android</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Short-lived-tokens-iOS-vs-Android/m-p/481095#M24269</link>
      <description>&lt;P&gt;Thanks for writing this up! We appreciate the feedback. These SDKs don't share code with each other, and are implemented differently. I can't speak to why specifically that's the case, but it may just be due to them having different constraints&amp;nbsp;and supporting different platforms. For instance, the Java SDK supports both Android and non-Android environments, whereas the Objective-C and Swift SDKs only support iOS/macOS.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 16:07:20 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Short-lived-tokens-iOS-vs-Android/m-p/481095#M24269</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2020-12-21T16:07:20Z</dc:date>
    </item>
  </channel>
</rss>

