Closed libreliodev closed 10 years ago
Do you mean that the download stopped half way through downloading the pdf? I.e. it was not at 0% or 100%
When I found an asset url that wasn't working, it was a problem with Amazon S3. You could try a test build with a different web host.
Maybe also a build with better logging of urls that fail to download so we can see what the actual error is.
On 18 November 2013 15:23, Librelio Dev Team notifications@github.comwrote:
@libreliopre https://github.com/libreliopre reported that 1/4 times the download stopped while loading the pdf, and 1/4 times the download stopped at the avant last resource (26/27) . He already had the problem before, with download often stopping at 26/27
@intrications https://github.com/intrications: what do you think? Assuming connectivity issues, is there any reason why download often seems to stop at 26/27?
— Reply to this email directly or view it on GitHubhttps://github.com/libreliodev/android/issues/197 .
Do you mean that the download stopped half way through downloading the pdf? I.e. it was not at 0% or 100%
I think it was 100%. @libreliopre : Can you confirm?
When I found an asset url that wasn't working, it was a problem with Amazon S3. You could try a test build with a different web host.
There was actually an issue with a naming mistake on one asset that you pointed out. But we still observe some download errors on other assets. Amazon S3 is an extremely reliable host, so I don't think the issue is there. On the other side, the Android DownloadManager is known for not being totally reliable.
Maybe also a build with better logging of urls that fail to download so we can see what the actual error is.
That's certainly a good idea. Can you push a test version to Github so that we build it?
This should be fixed with #231
@libreliopre reported that 1/4 times the download stopped while loading the pdf, and 1/4 times the download stopped at the avant last resource (26/27) . He already had the problem before, with download often stopping at 26/27
@intrications: what do you think? Assuming connectivity issues, is there any reason why download often seems to stop at 26/27?