-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No progress updates when executing a batch upload with small files #219
Comments
Thanks for the report! We'll look into it. |
Hi @gertjanvg , may I ask which batch upload method you are using? I can't find it |
@dor4emon They are referring to the |
This issue still exists. As @gertjanvg says, the fix is quick and easy, just adding executeProgressHandler etc. to the end of startUploadSmallFile to match the end of startUploadLargeFile. |
@angelFrog Thanks for the note! I'll bring this up with the team. |
I have tested as @angelFrog said and @gertjanvg guessed, but nothing happens. I still do not have progress. Can somebody help how to get progress? |
@pumPkin555 This issue is still open with the team, but it hasn't been addressed yet. I'll follow up here if/when I have an update on it. |
Thank you @greg-db! I look forward to your update. |
Does it support batchUploadData instead of files? |
@strong84 No, the SDK doesn't offer a version of this method that takes |
I have been working on an application that uploads a bunch of photos to Dropbox. All of the photos are pretty small and I used the batch upload method available in Dropbox to upload all of them. Everything worked, up until the point I wanted to track the progress of the upload process. I passed a
BatchUploadResponseBlock
as parameter forFilesRoutes.batchUploadFiles
, but no progress is being reported.Diving into the source code revealed the following issue: there are two different types of file uploading: small files and large files. Since all of my files were small all of them were passed to the
startUploadSmallFile
method. It turned out thatstartUploadSmallFile
does not actually ever callself.executeProgressHandler
, which results in no progress being reported at all.I have not yet tested whether this lack of reporting results in incorrect progress reporting when mixing small and large files, but my guess is it does. This obviously is an issue because one would expect progress from an upload task, especially a batched task.
For now I have put in place a quick bugfix, but a more elegant solution should be found. I will most likely submit a pull request later on with a better solution.
The text was updated successfully, but these errors were encountered: