Skip to content
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

Upload stuck : how I can force to start uploading #81

Closed
polok opened this issue Dec 11, 2015 · 6 comments
Closed

Upload stuck : how I can force to start uploading #81

polok opened this issue Dec 11, 2015 · 6 comments
Labels
bug Something isn't working

Comments

@polok
Copy link

polok commented Dec 11, 2015

Hi,

First my problem/case.

I have my own custom service which uses your SDK (basically TransferUtility). All works fine when I have internet connection. The whole fun begins when:

  • my service was killed
    • when I loose network connection the transfer doesn't want to start (sometimes it works but more often it seems to stuck : the records have RESUMED_WAITING and then when I run the app/my service (btw.I start my service during app launch) the records have status WAITING and nothing is uploaded

Also, for first case when my service was killed. I wanted to force it the upload agin. However, I don't see how I can do this. I tried to use resume but the state has to be PASUED, so first I run pause method which doesn't do the trick for me as it is setting PENDING_PAUSE and won't change to PAUSE so I can't resume it. How I can force, notify the TransferUtility or it's service to start uploading once again.

I am writing in a small rush so if I don't put enough information, just let me know. I will try to put more light on it then.

Thanks in advance for help.

@fosterzhang fosterzhang added the bug Something isn't working label Dec 11, 2015
@fosterzhang
Copy link
Contributor

Thanks for reporting it. We are working on the fix. Stay tuned.

@polok
Copy link
Author

polok commented Dec 14, 2015

Thanks for quick answer. Is there any chance that you will release new version with fix for above in very near future ? Our core functionality is based on uploading and this is really crucial for us ;/

@fosterzhang
Copy link
Contributor

@polok I'll definitely fix it ASAP, but sorry that I can't promise you an exact date. The service idles due to lost of network connection and eventually stops itself. An alternate solution is to delete the transfer and add it back to reactivate the service.

@fosterzhang
Copy link
Contributor

AWS SDK for Android v2.2.11 was released just now. The service should stay alive as long as there are active transfers. It'll resume transfers automatically when network is back. Also, you can use TransferUtility.resume(int) to resume a transfer which is not in TransferState.COMPLETED state. Check out the release notes for more details.

@polok
Copy link
Author

polok commented Jan 29, 2016

Awesome! I will check. Thx

@fosterzhang
Copy link
Contributor

Closing this. Feel free to reopen it if the issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants