-
Notifications
You must be signed in to change notification settings - Fork 549
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
S3 transferUtility progress tracking issue #333
Comments
Hi @FilenkovMaxim, Thanks for reporting to us.
|
@kvasukib hi
|
@kvasukib onProgressChanged(8, 37357164 / 111450625) |
@kvasukib hello! |
Hello, what is the file type you are trying to upload? Are you using any custom headers in the request? |
@rohandubal Hello! I use only setRegion() and not always setAccelerateModeEnabled() options. |
Hello. Any news? Yesterday I've got again 0 in bytesTotal it looked like this:
My code is:
|
We have been able to reproduce the first case and are working on the fix. We have not been able to reproduce the issue where the bytesTotal is 0. Are you doing more than one download at a time or just one? |
We released 2.6.6 that fixes the progress update. Can you try upgrading to 2.6.6 and check if it works for you? |
@kvasukib thanks a lot. Today I'll try this. |
@FilenkovMaxim Are you still having issues or did this update fix them for you? |
@kredden it seems to me that issue with progress was fixed. Thank you very much. |
Great! I'm going to close this issue now, if the zero issue happens again please reopen it. |
Hi @FilenkovMaxim, I was able to reproduce the issue finally. Sorry for the delayed reply. Test case: Start a download of 294.18 MB file. Logs here: 01-31 14:29:20.322 8560-8625/com.amazonaws.demo.s3transferutility V/StudioProfiler: Tracking initialization took: 514710595ns 01-31 14:31:11.938 8560-8571/com.amazonaws.demo.s3transferutility I/zygote: Background concurrent copying GC freed 4407(3MB) AllocSpace objects, 0(0B) LOS objects, 57% free, 1158KB/2MB, paused 8.743ms total 292.532ms Sorry for the inconvenience caused. We are looking into the code to spot the bug. If you have additional logs by enabling strict mode or any other test which reproduce the issue, please do attach it here. Thanks |
We also identified that the transfer observer after an app restart doesn't have the correct state of the transfer. We are working on to fix the internal state managed by the observer and the listener as they don't have a consistent view of the transfer record. |
Great! Please, notify me when you'll release. Then I'll be able to clean my code. |
Thanks @FilenkovMaxim for the reply. Do you have a code snippet that you would like to share? Do you use the observer only or observer with a listener? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems. |
To help us solve your problem better, please answer the following list of questions.
What service are you using?
TransferUtility (download)
In what version of SDK are you facing the problem?
com.amazonaws:aws-android-sdk-s3:2.4.7
Is the issue limited to Simulators / Actual Devices?
Actual Device (Xiaomi)
Can your problem be resolved if you bump to a higher version of SDK?
no
Is this problem related to specific Android/OS version?
no
Can you give us steps to reproduce with a minimal, complete, and verifiable example? Please include any specific network conditions that might be required to reproduce the problem.
I received not smoothy and not realistic data at onProgressChanged from TransferUtility. It finished downloading in one time after reached half size. Just jumped to 100% from 60%
It looks like this (look at the last line):
`21:58:41.0830 [main] D onProgressChanged(5, 56288708 / 111444303)
21:58:42.0750 [main] D onProgressChanged(5, 57845212 / 111444303)
21:58:43.0900 [main] D onProgressChanged(5, 59303172 / 111444303)
21:58:44.0880 [main] D onProgressChanged(5, 60466652 / 111444303)
21:58:45.0020 [main] D onProgressChanged(5, 111444303 / 111444303)`
And some times I got zero in bytesTotal argument. Not zero in first time, and then all of the calls with zero, and the last one with not zero again.
The text was updated successfully, but these errors were encountered: