-
Notifications
You must be signed in to change notification settings - Fork 550
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
What is a proper way to refresh FAILED transfer #87
Comments
Currently the SDK doesn't allow you to retry a failed transfer. Instead, you need to start a new transfer. I've seen similar requests several times. I'll research the best approach to address it. Stay tuned. |
Cool, looking forward for it. Thanks |
AWS SDK for Android v2.2.11 was released just now. You can use TransferUtility.resume(int) to resume a transfer which is not in |
Awesome! I will check. Thx |
Closing this. Feel free to reopen it if the issue persists. |
Does it still working for version 2.3.3? I've tried to call TransferUtility.resume(int) several times for a failed file and nothing happens. And also transferUtility.getTransfersWithTypeAndState(TransferType.ANY, TransferState.FAILED) returns an empty list even with FAILED files. |
Hi,
I have a view where I show progress of the update. The problem is that sometimes because of low internet connection I get such error Unable to execute HTTP request: Read timed out... and transfer gets FAILED status what is fine but the problem is how I should force the SDK to start upload again. I don't want to close the app and run once again. Is there a possibility that this could be done automatically, scheduled or something ?
Thanks in advance,
The text was updated successfully, but these errors were encountered: