Hi,
our users can choose specific folders that they want to synchronize from Dropbox to our app*. We store the current list_folder/list_folder_continue cursor in our database, so we only get changed files. This is working fine, as long as the "subscribed" folders are never moved/renamed. If a user does that, the list_folder_continue call fails with (even though we didn't use a path, we used a cursor):
Exception in 2/files/list_folder/continue: {".tag":"path", "path":"not_found"}
We already had this problem using the V1 API and I had great hopes when I read that there's ID support in the V2 API (so we could use the same ID, regardless if the folder was renamed), but so far this isn't really working out because of two problems:
- First, the initial list_folder call (when we don't have a cursor, yet) can't use the ID, since IDs are not supported for list_folder, so if the user has renamed the folder in the meantime, we can basically only skip it.
- Second, as described above, the cursors for list_folder_continue also seem to be path-based and stop working when a folder is moved or renamed.
So, what's the recommended way to deal with this situation? So far, all I can see that we can do is stop synchronizing that folder and ask our users to choose folders again if they want the renamed folder to be included.
Cheers,
David
* fileee.com