<?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: Folders with lots of files failing in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229826#M12493</link>
    <description>&lt;P&gt;So the problem is that I created 2 different calls. One for folders only and another for files. Apparently if there are enough files and it takes long enough, having the 2 calls at the same time will cause problems. I guess they cannot run concurrently without something happening. If I use just one routine, it works but is considerably slower than V1 I think.&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jun 2017 06:44:37 GMT</pubDate>
    <dc:creator>808phone</dc:creator>
    <dc:date>2017-06-29T06:44:37Z</dc:date>
    <item>
      <title>Folders with lots of files failing</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229811#M12490</link>
      <description>&lt;P&gt;When I call listFolder like in the example code, *response is often nil.&lt;/P&gt;
&lt;P&gt;This only happens with large numbers of files (over 1800, with some people 3000+ files).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;DBFILESListFolderResult *response is nil.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a problem for my app.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE class="highlight plaintext"&gt;&lt;CODE&gt;[[client.filesRoutes listFolder:@"/test/path/in/Dropbox/account"]
    setResponseBlock:^(DBFILESListFolderResult *response, DBFILESListFolderError *routeError, DBRequestError *networkError) {
      if (response) {
        NSArray&amp;lt;DBFILESMetadata *&amp;gt; *entries = response.entries;
        NSString *cursor = response.cursor;
        BOOL hasMore = [response.hasMore boolValue];

        [self printEntries:entries];

        if (hasMore) {
          NSLog(@"Folder is large enough where we need to call `listFolderContinue:`");

          [self listFolderContinueWithClient:client cursor:cursor];
        } else {
          NSLog(@"List folder complete.");
        }
      } else {
        NSLog(@"%@\n%@\n", routeError, networkError);
      }
    }];&lt;/CODE&gt;&lt;/PRE&gt;
&lt;PRE class="highlight plaintext"&gt;&lt;CODE&gt;listFolder&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:21:09 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229811#M12490</guid>
      <dc:creator>808phone</dc:creator>
      <dc:date>2019-05-29T09:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: Folders with lots of files failing</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229826#M12493</link>
      <description>&lt;P&gt;So the problem is that I created 2 different calls. One for folders only and another for files. Apparently if there are enough files and it takes long enough, having the 2 calls at the same time will cause problems. I guess they cannot run concurrently without something happening. If I use just one routine, it works but is considerably slower than V1 I think.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 06:44:37 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229826#M12493</guid>
      <dc:creator>808phone</dc:creator>
      <dc:date>2017-06-29T06:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: Folders with lots of files failing</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229896#M12499</link>
      <description>If response is nil, make sure you check the routeError and networkError. One of them should contain an error message.&lt;BR /&gt;&lt;BR /&gt;In any case, yes, you shouldn't make multiple concurrent listFolder[Continue] calls. A single listFolder[Continue] loop will return both files and folders under the requested path.</description>
      <pubDate>Thu, 29 Jun 2017 15:00:26 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/229896#M12499</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-06-29T15:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: Folders with lots of files failing</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/230100#M12521</link>
      <description>&lt;P&gt;Greg,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The routine is much slower than V1 as well. The callback takes much longer. Is there going to be any improvement on this?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 17:43:13 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/230100#M12521</guid>
      <dc:creator>808phone</dc:creator>
      <dc:date>2017-06-30T17:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: Folders with lots of files failing</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/230109#M12523</link>
      <description>I can't make any promises, but I'm sending this along to the team as a request to improve performance here.</description>
      <pubDate>Fri, 30 Jun 2017 18:28:13 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Folders-with-lots-of-files-failing/m-p/230109#M12523</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-06-30T18:28:13Z</dc:date>
    </item>
  </channel>
</rss>

