Closed jporcenaluk closed 9 months ago
Thanks for the report! We'll look into it and I'll follow up here once I have an update.
Thanks @greg-db ! I updated the ticket with example code that should work once the following dependencies are installed via pip:
dropbox
pytz
Apologies for the delayed response. The team has reported that this was fixed. Please let us know if you're still seeing this.
Describe the bug When searching for files using the
files_search_v2
function, the metadata for the files includes a repeated value forserver_modified
that is randomly retrieved from any one of the files'client_modified
field values.This makes it very difficult to know if a file needs to be downloaded, as
client_modified
is called out in the docs as not a reliable way to find that out, whereserver_modified
is intended to be. Current functionality indicates thatserver_modified
is not reliable for that purpose.To Reproduce
client_modified
andserver_modified
metadata on the filesclient_modified
is different for each file, butserver_modified
is the same for each file (and is set to one or the other of theclient_modified
values)Example Code
Expected Behavior Expected to see
server_modified
has different values per file that indicate when they were last modified.Actual Behavior
server_modified
is the same value for each file, and randomly changes, and is aligned with one randomclient_modified
value from what is returned from the search.Screenshots
Versions
Additional context This is important to us, as we require a reliable way to identify new files being uploaded to Dropbox for our use case.