Child Item

Single API call creating duplicate file versions using Dropbox .Net Api

Hi Dropbox Support,

I'm experiencing an issue with the Dropbox .NET API where a single file upload API call is creating two identical versions of the same file with the following problems:

Problem details:

Using Dropbox .NET API for file uploads
One API request results in two file versions created 1ms apart
Different attribution: One version shows "edited by user on web", the other shows "edited by user on API app"
All uploads are done through API only - no web interface involvement
This happens inconsistently - some files upload normally, others create duplicates
API methods used: For small files:
uploadArg = gcnew Dropbox::Api::Files::UploadArg(dropboxPath, Dropbox::Api::Files::WriteMode::Overwrite::Instance, false, clientModified, true, nullptr, false, nullptr); uploadTask = m_dropboxclient->Files->UploadAsync(uploadArg, fileStream);
For large files:
task = m_dropboxclient->Files->UploadSessionFinishAsync(cursor, commitInfo, nullptr, fileChunk);

Find more posts tagged with

API

Upload

Abuse

Comments

DB-Des

Hi @User9871

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with:

the steps to reproduce the issue, including relevant full code snippet(s), but don't include any access or refresh token(s)
5-10 different 'X-Dropbox-Request-Id' response header values encountering the issue

Also, you mentioned this is an intermittent issue you have observed, can you confirm that when it has happened that it happened with both 'UploadAsync()' and 'UploadSessionFinishAsync()'?

James_David

This looks like the API is creating two commits instead of one. Even though you only call the upload once, Dropbox may register a retry or double commit because of timing or how the SDK handles network responses. That explains why you see two versions a millisecond apart, with one marked “API” and one marked “web.” They are not actually duplicates on disk, just two versions of the same file. To fix it, confirm that your code only calls the upload method once per file, especially at the point where sessions are finished for large uploads. Add logging to ensure there are no retries or parallel calls. If the problem persists, note the request IDs from the API responses and pass them to Dropbox Support so they can trace why two commits are recorded.