I have hit an issue when using the Dropbox API in c# - which in general is excellent. Binary files that have not changed are always updated online if they are recreated but the content has not changed.
I found over in the general user area of the forum this thread (Problems-with-100s-of-files-syncing-even-though-they-haven-t/m-p) which is the same issue I think that is occurring more generally for all Dropbox users.
To narrow the issue down a bit, when uploading a text file, Dropbox correctly identifies that the file has not changed and does not revise the version online.
When uploading binary files (e.g. zip files), the API doesn't see that the files are the same and updates the file online to the "new" version. I had a quick look at a tiny 340 byte zip file and they look to be identical at the byte level. I'm going to work around this for now and stop binary uploads when the file size with the current live version has not changed, but this is obviously less than ideal and is going to create some (unlikely) edge case issues with the application I'm developing. I'm using the API for c# version 4.2.0.
I'm not sure if this is a bug, or just that I'm perhaps not using the API correctly?
