Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Renamed shared folder reported both as new and deleted by /list_folder/continue
Hello Greg,
Found a strange behavior with /list_folder/continue that you might be able to clarify. Here's how to reproduce:
- Using /list_folder/continue until you get the last cursor.
- Re...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThanks for the report! I'm seeing the duplicate "/oldname" in my testing, but not the extra deleted "/newname", though I expect it will depend on the particular state of the account. In this sample, did you previously have anything at "/newname" by any chance?
We'll look into whether or not we can clean this up, but the entries as shown here should still give you the correct state as long as you process them in order according to the rules indicated in the /files/list_folder documentation:
https://www.dropbox.com/developers/documentation/http/documentation#files-list_folder
I.e., Per "If there's nothing at the given path, ignore this entry.", you should make sure your app is able to ignore any such entries, such as these redundant deleted ones.
We'll look into whether or not we can clean this up, but the entries as shown here should still give you the correct state as long as you process them in order according to the rules indicated in the /files/list_folder documentation:
https://www.dropbox.com/developers/documentation/http/documentation#files-list_folder
I.e., Per "If there's nothing at the given path, ignore this entry.", you should make sure your app is able to ignore any such entries, such as these redundant deleted ones.
Good point, I did not think about this name having ever been used. So, to be sure I did the same test again with both old and new names being random strings that surely has never been used in the whole account. I get the same behavior.
The processing order is hard to enforce when working in a threaded context so having both a new and a deleted folder might result in an unpredictable behavior.
Anyway, thank you for the quick feedback and I'll be happy to help if you need more context to be able to replicate this behavior.
- Greg-DBThanks! We'll look into it.
Note that is is important that your app process these entries in order. Otherwise, you may not get a state consistent with the state on the Dropbox servers.Hi Greg K.
We got tha same issue when trying to sharing folder.
Reproduce steps:
1. create a test_folder and add sub-folder a, b, c, d, e
2. sharing test_folder/a, test_folder/b, test_folder/c, test_folder/d, test_folder/e
3. /list_folder/continue will report folder delete event and folder sharing event
---------------------------------------------------------------------------------------------------------------------------------
{
"entries":[
{
".tag":"deleted",
"name":"d",
"path_lower":"/test_folder/xx/d",
"path_display":"/test_folder/xx/d"
},
{
".tag":"deleted",
"name":"b",
"path_lower":"/test_folder/xx/b",
"path_display":"/test_folder/xx/b"
},
{
".tag":"folder",
"name":"b",
"path_lower":"/test_folder/xx/b",
"path_display":"/test_folder/xx/b",
"id":"id:8hk3XBzqwAoAAAAAAAMtfQ",
"shared_folder_id":"2218134592",
"sharing_info":{
"read_only":false,
"shared_folder_id":"2218134592",
"traverse_only":false,
"no_access":false
}
},
{
".tag":"folder",
"name":"d",
"path_lower":"/test_folder/xx/d",
"path_display":"/test_folder/xx/d",
"id":"id:8hk3XBzqwAoAAAAAAAMtfw",
"shared_folder_id":"2218136512",
"sharing_info":{
"read_only":false,
"shared_folder_id":"2218136512",
"traverse_only":false,
"no_access":false
}
}
],
"cursor":"xxx",
"has_more":true
}
---------------------------------------------------------------------------------------------------------------------------------------
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
