You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Dropbox API to create a file, write in it via stream and then close the file.
Hi,
I am from Softaculous Ltd. I already have an open issue but here I'm opening a new one which is regarding a different issue.
I have a query regarding Dropbox. We want our users to upl...
Greg-DB
Dropbox Staff
Dropbox StaffFor large files, or any files you want to upload in pieces, you should use upload sessions:
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-start
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-append_v2
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-finish
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-start
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-append_v2
https://www.dropbox.com/developers/documentation/http/documentation#files-upload_session-finish
Hi,
I have some doubt about 'files_upload_session_start' API. Do I require to first call the 'upload' API and then start the 'upload_session_start' API as I can't see where to mention the dropbox path where I want to upload the file to in 'upload_session_start' API. Can you please tell me how to implement this?
Also if I want to upload 1MB at a time instead of 150 MB, how can I mention that?
- Greg-DB
No, you don't need to also call /upload if you're using upload sessions. You specify the path where you want to upload the file when you call /2/files/upload_session/finish.
If you want to upload 1 MB at a time, you would just supply 1 MB of data to each request to /2/files/upload_session/start, /2/files/upload_session/append_v2, and /2/files/upload_session/finish. That is, you would have your app only submit 1 MB of data (in the request body) per call.
When calling /2/files/upload_session/append_v2 or /2/files/upload_session/finish, the 'offset' is the total amount of data that has been uploaded so far for that upload session, in bytes. This is something the app should keep track of client-side, as the app decides how much to upload each time.
There's a basic example of using upload sessions that may be helpful here. It's for the Python SDK, but the logic is the same.
- Hi,
I have been trying the same thing but while upload_finish, I was getting the following error:
{"error_summary": "lookup_failed/not_found/..", "error": {".tag": "lookup_failed", "lookup_failed": {".tag": "not_found"}}}
On further research I found out that the error occur due to incorrect session id. I corrected the same and the error was eliminated.
I now have another doubt. I have created three different functions for session start, session append and session finish. From inside session start, if the session id is not empty, session append function is called. Now when initially I'm calling the session start function with 1MB of data to upload, the upload session start executes. Now the session id is filled. So now again the session start function is called (automatically) and session append is done from inside it (as coded by me as session id is now filled.). Now once the session append is done, the same process repeats again and again till 7MB (since the file size I'm trying to upload is 7.48MB). But after 7MB, automatically the session finish funstion is called and the session ends with incomplete file upload.
I have two doubts here:
1. How the looping is going automatically when I'm not putting the code in any loop? Is this the intended behavior?
2. How shall it be handled when there is an extra .48MB of data remaining to upload?
- Hi,
Also I'm trying to upload a .tar.gz file but the file is uploaded incompletely and corrupted using upload session functionality. Can you tell me the reason?- Greg-DB
1. I'm not sure I follow. Exactly what functions are called and when is controlled by your app. You may want to step through with a debugger to see what it is doing and how to correct it.
2. You don't have to upload the same amount of data with each call. For example, when you only have less than 1 MB left to upload, you can call finish and upload that less than 1 MB amount of data.
When using upload sessions, you should only call start once per file. Then you can call append as many times as necessary. You should then call finish once. You don't have to send the same amount of data in each call (e.g., the last call will usually contain less than the others) but you do need to upload the file data in order.
If you're not getting valid files, you should debug your implementation to make sure you're sending up all of the correct data, and in order. (From your earlier post, it sounds like you're missing the last piece.)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
