We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
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 StaffNo, 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?
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?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
