<?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: Could not decode input as JSON happening in production starting today in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206654#M10051</link>
    <description>Can you share a sample request and response? That will help us determine the issue. Just make sure you redact the access token. Thanks!</description>
    <pubDate>Mon, 13 Feb 2017 21:58:08 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2017-02-13T21:58:08Z</dc:date>
    <item>
      <title>Could not decode input as JSON happening in production starting today</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206648#M10049</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi, today we started getting the error&amp;nbsp;below for a small % of our userbase in production (our app has been in production for &amp;gt; 1&amp;nbsp;year - and this is the first time we've seen this).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It seems to be specific to individual authorized accounts - neither files/list_folder or&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/files/list_folder/continue works for those users (they all give the error below) - but when run against other user accounts it's working fine. When a user got the error on /files/list_folder/continue we reset their sync token (so called files/list_folder for the user instead) and it still occured.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a backend issue on the Dropbox end?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Error in call to API function "files/list_folder": request body: could not decode input as JSON&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:25:54 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206648#M10049</guid>
      <dc:creator>dmf</dc:creator>
      <dc:date>2019-05-29T09:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: Could not decode input as JSON happening in production starting today</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206654#M10051</link>
      <description>Can you share a sample request and response? That will help us determine the issue. Just make sure you redact the access token. Thanks!</description>
      <pubDate>Mon, 13 Feb 2017 21:58:08 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206654#M10051</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-02-13T21:58:08Z</dc:date>
    </item>
    <item>
      <title>Re: Could not decode input as JSON happening in production starting today</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206666#M10054</link>
      <description>&lt;P&gt;Sorry for the false alarm. Looks like the issue was in some code on our end.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2017 22:20:47 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Could-not-decode-input-as-JSON-happening-in-production-starting/m-p/206666#M10054</guid>
      <dc:creator>dmf</dc:creator>
      <dc:date>2017-02-13T22:20:47Z</dc:date>
    </item>
  </channel>
</rss>

