Hi,
I recently tried a case and can you please why this happened?
CASE 1: I deleted a folder in Dropbox UI, invoked upload api with the deleted folder's id(not folder path)
---> A new folder was created with the same name and the file was uploaded. New folder ID is assigned and upload works with old folder id but file listing does not work. So it is better if the new parent folder id is returned with the response.
CASE 2: I deleted a folder in Dropbox UI, Permanently deleted from deleted files list, and invoked upload api with the deleted folder's id(not folder path)
---> I get an error response with 409 code
{
"error_summary":"path/no_write_permission/..",
"error":{
"reason":{
".tag":"no_write_permission"
},
"upload_session_id":"AAAACCyd-qiaauwth7qQ",
".tag":"path"
}
}
Why does this happen? Can't this error be more clear like "Folder does not exist"?
However, while listing the files with the folder id (that of the deleted folder's), I get the following response
{
"error_summary":"path/not_found/..",
"error":{
"path":{
".tag":"not_found"
},
".tag":"path"
}
}
Can't the same error response be given for previous case also?
This whole scenario is so confusing. Can you clarify and tune the repsonse ?
Thanks!
