<?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: Increased latency after upgrade to .Net SDK 6.* in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508252#M25096</link>
    <description>&lt;P&gt;I think I can answer my own question.&amp;nbsp; We create the DropboxClient without specifying&amp;nbsp;&lt;FONT face="courier new,courier"&gt;MaxRetriesOnError&lt;/FONT&gt;.&amp;nbsp; In 6.*, this defaults to 4. If I set this to 0, then my code responds with latency values on par with the behavior in 4.9 SDK.&amp;nbsp; So, I suspect the 6.* SDK is retrying on &lt;FONT face="courier new,courier"&gt;AuthException&lt;/FONT&gt;, whereas the 4.9 SDK did not.&amp;nbsp; If it is retrying on &lt;FONT face="courier new,courier"&gt;AuthExceptions&lt;/FONT&gt;, this seems like a bug to me, especially if its an "invalid access token", as it is in my case.&amp;nbsp; The token isn't suddenly going to change and become valid on a retry.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 26 Mar 2021 23:08:02 GMT</pubDate>
    <dc:creator>jfreer</dc:creator>
    <dc:date>2021-03-26T23:08:02Z</dc:date>
    <item>
      <title>Increased latency after upgrade to .Net SDK 6.*</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508238#M25095</link>
      <description>&lt;P&gt;I have an app that uses long-lived access tokens to upload files in the background.&amp;nbsp; In order to migrate to using refresh tokens, I upgraded from .Net SDK 4.9.* to .Net SDK 6.*.&amp;nbsp; The first call our app makes is to &lt;FONT face="courier new,courier"&gt;Files.GetMetadataAsync&lt;/FONT&gt; to determine if the file exists.&amp;nbsp; I noticed that if the call results in an &lt;FONT face="courier new,courier"&gt;AuthException (&lt;SPAN class="t"&gt;invalid_access&lt;/SPAN&gt;&lt;SPAN&gt;_&lt;/SPAN&gt;&lt;SPAN class="t"&gt;token)&lt;/SPAN&gt;&lt;/FONT&gt;, the latency of the call is now 10-20 seconds, whereas before the upgrade this was under 1 second.&amp;nbsp; I tried upgrading first to 6.0.1, and then to 6.2.&amp;nbsp; Same result.&amp;nbsp; There were 0 code changes with this upgrade; just an update of the Nuget package.&amp;nbsp; I have rolled back this upgrade until the problem is better understood.&amp;nbsp; I am using .Net core 3.1.&amp;nbsp; Any ideas why?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2021 21:10:40 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508238#M25095</guid>
      <dc:creator>jfreer</dc:creator>
      <dc:date>2021-03-26T21:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: Increased latency after upgrade to .Net SDK 6.*</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508252#M25096</link>
      <description>&lt;P&gt;I think I can answer my own question.&amp;nbsp; We create the DropboxClient without specifying&amp;nbsp;&lt;FONT face="courier new,courier"&gt;MaxRetriesOnError&lt;/FONT&gt;.&amp;nbsp; In 6.*, this defaults to 4. If I set this to 0, then my code responds with latency values on par with the behavior in 4.9 SDK.&amp;nbsp; So, I suspect the 6.* SDK is retrying on &lt;FONT face="courier new,courier"&gt;AuthException&lt;/FONT&gt;, whereas the 4.9 SDK did not.&amp;nbsp; If it is retrying on &lt;FONT face="courier new,courier"&gt;AuthExceptions&lt;/FONT&gt;, this seems like a bug to me, especially if its an "invalid access token", as it is in my case.&amp;nbsp; The token isn't suddenly going to change and become valid on a retry.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2021 23:08:02 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508252#M25096</guid>
      <dc:creator>jfreer</dc:creator>
      <dc:date>2021-03-26T23:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: Increased latency after upgrade to .Net SDK 6.*</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508753#M25118</link>
      <description>&lt;P&gt;Thanks! It looks like your understanding is correct. I'm bringing this up with the team to see if we can update the SDK to not retry on an auth failure like that.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Mar 2021 18:01:10 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Increased-latency-after-upgrade-to-Net-SDK-6/m-p/508753#M25118</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2021-03-29T18:01:10Z</dc:date>
    </item>
  </channel>
</rss>

