<?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 How to dealing with shared folder event by /ist_folder/continue API in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-dealing-with-shared-folder-event-by-ist-folder-continue/m-p/271695#M16094</link>
    <description>&lt;P&gt;When trying to dealing with shared folder event generated by&amp;nbsp;/ist_folder/continue API, we noticed the folder changes reported by&amp;nbsp;&lt;SPAN&gt;/ist_folder/continue API is same in the following two case and it confues us.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;case1:&amp;nbsp; &amp;nbsp; sync some files under a folder&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;delete the folder then create a shared folder with the same name (ex: create /A/B.txt, delete /A, create a shared folder /A)&lt;/P&gt;&lt;P&gt;case2:&amp;nbsp; &amp;nbsp; creating a shared folder (ex: creat a shared folder /A)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The&amp;nbsp;&lt;SPAN&gt;/ist_folder/continue API will report the same event:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----------------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;{&lt;BR /&gt;"entries": [&lt;BR /&gt;{&lt;BR /&gt;".tag": "deleted",&lt;BR /&gt;"name": "A",&lt;BR /&gt;"path_lower": "/A",&lt;BR /&gt;"path_display": "/A"&lt;BR /&gt;},&lt;BR /&gt;{&lt;BR /&gt;".tag": "folder",&lt;BR /&gt;"name": "A",&lt;BR /&gt;"path_lower": "/A",&lt;BR /&gt;"path_display": "/A",&lt;BR /&gt;"id": "id:a7PnAnCp1kAAAAAAAABjyQ",&lt;BR /&gt;"shared_folder_id": "2841070816",&lt;BR /&gt;"sharing_info": {&lt;BR /&gt;"read_only": false,&lt;BR /&gt;"shared_folder_id": "2841070816",&lt;BR /&gt;"traverse_only": false,&lt;BR /&gt;"no_access": false&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;],&lt;BR /&gt;"cursor": "XXXXXX",&lt;BR /&gt;"has_more": true&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----------------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We can not identify there two cases easily.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It may lead to remove local folder even we only sharing a folder because&amp;nbsp;/ist_folder/continue API reports a folder delete event.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this a kind of bug for&amp;nbsp;/ist_folder/continue API&amp;nbsp;&amp;nbsp;for shared folder&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;or by design ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a guideline to handle these case&amp;nbsp;and is there any chance to imporve the&amp;nbsp;/ist_folder/continue API&amp;nbsp; behavior for shared folder.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:14:05 GMT</pubDate>
    <dc:creator>Cloud</dc:creator>
    <dc:date>2019-05-29T09:14:05Z</dc:date>
    <item>
      <title>How to dealing with shared folder event by /ist_folder/continue API</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-dealing-with-shared-folder-event-by-ist-folder-continue/m-p/271695#M16094</link>
      <description>&lt;P&gt;When trying to dealing with shared folder event generated by&amp;nbsp;/ist_folder/continue API, we noticed the folder changes reported by&amp;nbsp;&lt;SPAN&gt;/ist_folder/continue API is same in the following two case and it confues us.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;case1:&amp;nbsp; &amp;nbsp; sync some files under a folder&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;delete the folder then create a shared folder with the same name (ex: create /A/B.txt, delete /A, create a shared folder /A)&lt;/P&gt;&lt;P&gt;case2:&amp;nbsp; &amp;nbsp; creating a shared folder (ex: creat a shared folder /A)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The&amp;nbsp;&lt;SPAN&gt;/ist_folder/continue API will report the same event:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----------------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;{&lt;BR /&gt;"entries": [&lt;BR /&gt;{&lt;BR /&gt;".tag": "deleted",&lt;BR /&gt;"name": "A",&lt;BR /&gt;"path_lower": "/A",&lt;BR /&gt;"path_display": "/A"&lt;BR /&gt;},&lt;BR /&gt;{&lt;BR /&gt;".tag": "folder",&lt;BR /&gt;"name": "A",&lt;BR /&gt;"path_lower": "/A",&lt;BR /&gt;"path_display": "/A",&lt;BR /&gt;"id": "id:a7PnAnCp1kAAAAAAAABjyQ",&lt;BR /&gt;"shared_folder_id": "2841070816",&lt;BR /&gt;"sharing_info": {&lt;BR /&gt;"read_only": false,&lt;BR /&gt;"shared_folder_id": "2841070816",&lt;BR /&gt;"traverse_only": false,&lt;BR /&gt;"no_access": false&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;],&lt;BR /&gt;"cursor": "XXXXXX",&lt;BR /&gt;"has_more": true&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-----------------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We can not identify there two cases easily.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It may lead to remove local folder even we only sharing a folder because&amp;nbsp;/ist_folder/continue API reports a folder delete event.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this a kind of bug for&amp;nbsp;/ist_folder/continue API&amp;nbsp;&amp;nbsp;for shared folder&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;or by design ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a guideline to handle these case&amp;nbsp;and is there any chance to imporve the&amp;nbsp;/ist_folder/continue API&amp;nbsp; behavior for shared folder.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:14:05 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-dealing-with-shared-folder-event-by-ist-folder-continue/m-p/271695#M16094</guid>
      <dc:creator>Cloud</dc:creator>
      <dc:date>2019-05-29T09:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to dealing with shared folder event by /ist_folder/continue API</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-dealing-with-shared-folder-event-by-ist-folder-continue/m-p/271811#M16107</link>
      <description>This is the expected behavior, and it is unlikely to change.&lt;BR /&gt;&lt;BR /&gt;I'll be happy to pass this along as feedback to the team though. Can you elaborate on how this causes issues for your app?&lt;BR /&gt;&lt;BR /&gt;You can check that the folder has been shared via the `sharing_info` included in the new folder metadata, in order to reconcile the deletion and addition, if you wish. Additionally, in the case of a shared folder, the `id` of the folder itself won't change (unlike in the deletion/new folder case).</description>
      <pubDate>Mon, 09 Apr 2018 14:46:46 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-dealing-with-shared-folder-event-by-ist-folder-continue/m-p/271811#M16107</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2018-04-09T14:46:46Z</dc:date>
    </item>
  </channel>
</rss>

