Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
When trying to dealing with shared folder event generated by /ist_folder/continue API, we noticed the folder changes reported by /ist_folder/continue API is same in the following two case and it confues us.
case1: sync some files under a folder and delete the folder then create a shared folder with the same name (ex: create /A/B.txt, delete /A, create a shared folder /A)
case2: creating a shared folder (ex: creat a shared folder /A)
The /ist_folder/continue API will report the same event:
-----------------------------------------------------------------------------------------
{
"entries": [
{
".tag": "deleted",
"name": "A",
"path_lower": "/A",
"path_display": "/A"
},
{
".tag": "folder",
"name": "A",
"path_lower": "/A",
"path_display": "/A",
"id": "id:a7PnAnCp1kAAAAAAAABjyQ",
"shared_folder_id": "2841070816",
"sharing_info": {
"read_only": false,
"shared_folder_id": "2841070816",
"traverse_only": false,
"no_access": false
}
}
],
"cursor": "XXXXXX",
"has_more": true
}
-----------------------------------------------------------------------------------------
We can not identify there two cases easily.
It may lead to remove local folder even we only sharing a folder because /ist_folder/continue API reports a folder delete event.
Is this a kind of bug for /ist_folder/continue API for shared folder or by design ?
Is there a guideline to handle these case and is there any chance to imporve the /ist_folder/continue API behavior for shared folder.
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!