Comments
-
Do we need to explicitly cancel the upload requests, or is it enough to release the objects by setting it to nil? Example, I have dbUploadTask = client?.files.uploadSessionStart(input: data) dbUploadTask?.response(completionHandler: { [weak self] (result, error) in } Then is it safe to set the object to nil while upload is…
-
pod repo update didn't help. The only way to fix it was to downgrade Alamofire version to 4.5.1. But this version gives 1 warning and SwiftyDropbox has 3 warnings: " Using '!' in this location is deprecated and will be removed in a future release; consider changing this to '?' instead" "'characters' is deprecated: Please…
-
I will try to conduct test with 8 MB chunks, but I see the issue with chunked approach is it doesn't work in background on iOS. Is there any approach to get the upload working in background?
-
Also, many a times upload simply hangs without throwing any error. Setting large block size to 100 MB causes such problems more often.
-
I am having the same trouble of extemely slow upload speeds, no matter I set chunk size to 5 MB or 100 MB. It's only 191 MB file I am uploading. Please help, there is no official iOS sample code in Objective C or Swift though. Progress callbacks always arrive every 32 KB.