We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Issues about Chunkupload
I'm writing a very simple console uploading program using most of the sample code from Dropbox.net Api. But I have two issues now.
When the network drops and reconnects, I get an error saying "...
The documentation for UploadSessionLookupError.IncorrectOffset covers an example of how this can occur:
"The specified offset was incorrect. See the value for the correct offset. This error may occur when a previous request was received and processed successfully but the client did not receive the response, e.g. due to a network error."
To get the correct offset, you can catch and inspect the exception like this:
try { await client.Files.UploadSessionAppendV2Async(cursor, body: memStream); } catch (ApiException<UploadSessionLookupError> e) { if (e.ErrorResponse.IsIncorrectOffset) { Console.WriteLine("Expected offset: " + e.ErrorResponse.AsIncorrectOffset.Value.CorrectOffset); } // todo: other error handling throw; }In your 5120kb file scenario, I believe the offset would still be 3072 at that point, since the connection failed. However that may depend on the exact nature of the failure, so you should always check the returned value anyway.
Greg-DB
Dropbox Staff
Dropbox StaffThe documentation for UploadSessionLookupError.IncorrectOffset covers an example of how this can occur:
"The specified offset was incorrect. See the value for the correct offset. This error may occur when a previous request was received and processed successfully but the client did not receive the response, e.g. due to a network error."
To get the correct offset, you can catch and inspect the exception like this:
try {
await client.Files.UploadSessionAppendV2Async(cursor, body: memStream);
} catch (ApiException<UploadSessionLookupError> e) {
if (e.ErrorResponse.IsIncorrectOffset) {
Console.WriteLine("Expected offset: " + e.ErrorResponse.AsIncorrectOffset.Value.CorrectOffset);
}
// todo: other error handling
throw;
}
In your 5120kb file scenario, I believe the offset would still be 3072 at that point, since the connection failed. However that may depend on the exact nature of the failure, so you should always check the returned value anyway.
I'm getting another related problem here. If the program accendentally exits, then how can I resume upload when it restarts?
I tried a solution which is,
1. record the sessionID and cursor.offset to a txt after each chunk upload;
2. every time the program starts, it will check if "record.txt" exists. If txt exists, then it means this is a resume-upload. The program should upload from last offset.
But here is the problem, how can I get the right MemoryStream from last offset position?
The following code
if (File.Exists("record.txt")) { foreach (string line in File.ReadLines("record.txt")) { if (line.Contains("AAAA")) { sessionId = line; } else { currentPosition = long.Parse(line); } } File.Delete("record.txt"); } if (isResume) { byteRead = stream.Read(buffer, 0, chunkSize); //this line doesn't work. }- Greg-DBIt sounds like you already have the right idea, in that you should store upload session ID and resume the upload from where you left off. I don't recommend relying on the session ID having "AAAA" though, as that's not guaranteed. You should store it in some format you can rely on, and use whatever session ID string the API gave you.
As far as how you interact with the local file, I'm afraid that's a bit outside the scope of Dropbox API support, as that has to do with the local file system and not Dropbox. You'll probably want to refer to the documentation for FileStream and MemoryStream to determine how to start reading from the file at a particular offset in the file.Alright. Thank you!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
