Dropbox API v1 deprecated

[dennissiemensma]

On June 28, 2017, API v1 will be turned off.

Please sign in to the Dropbox Platform website by September 28, 2016, and acknowledge that you’re aware of the deprecation.

To keep providing Dropbox features in your app, upgrade to API v2.

https://blogs.dropbox.com/developers/2016/04/announcing-the-v1-to-v2-migration-guide/

[dennissiemensma]

Merged to development. Will run it on own production for a while to be sure.

[dennissiemensma]

It seems that uploading does not work well on my own production. Which is weird, since I cannot reproduce it (yet) locally.

I'll have to look into this again.

[dennissiemensma]

I've found another implementation which seem to work locally, it's slightly differs from my own: https://stackoverflow.com/documentation/dropbox-api/409/uploading-a-file/1927/uploading-a-file-using-the-dropbox-python-sdk#t=201610181733061624381

It also checks whether the files should be uploaded at one go (when small) or in chunks (when spanning multile MB's).

My previous implementation however also worked well locally when developing, so I'll have to test this on my own production later this week to be sure it's fixed completely.

[dennissiemensma]

It still does not work on my own production. For some reason this Dropbox v2 API issue keeps haunting me :]

[dennissiemensma]

I finally got Sentry working as well, which gave me some valuable information:

ApiError: ApiError('xxxxxxxxxxxxx', UploadSessionFinishError('path', WriteError('conflict', WriteConflictError('file', None))))

The WriteConflictError triggered me to recheck the existing-file-policy for Dropbox, which you can alter for each command. The old v1 API command had something similar as well.
However, for v2 I seemed to have used autorename=False, which only prevents autorenaming, but not resolving conflicts for existing files. And since daily backups are rotated and overwritten each week, this happens daily.
After having a peek inside the Dropbox v2 client, I saw another parameter called mode, besides autorename. In the end it seems to accept some union or struct of enum of whatever to say Dropbox what policy to use.
So now I simply removed the autorename directive and replaced it by mode=dropbox.files.WriteMode.overwrite. Just a few minutes after deploying this I already saw incoming dropbox notifications about changed files!

I'll monitor it for a few days, but I'm really glad this finally seems fixed.

[dennissiemensma]

Confirmed, finally working on production! Merged once again back to development branch.