This was the exact issue i faced back then
Seeing this as well. For me it's like this:
Download is started and seems to complete ok, I get the
DOWNLOAD_COMPLETED broadcast. However, right after this I see
DownloadManager logging:
I/DownloadManager( 5893): Initiating request for download 1419
W/DownloadManager( 5893): Aborting request for download 1419: Trying
to resume a download that can't be resumed
Then I get another DOWNLOAD_COMPLETED with the same download ID. Also,
it seems the downloaded file gets deleted during this second, failed
attempt.
Any ideas what triggers this? Or any workarounds? Or is everyone just
writing their own download managers...
Reported to google; here
I tried to figure out a way to work around this issue. But it was hard and costed alot. So i threw away all my work with DownloadManager
and started coding my custom downloader. DownloadManager
back then proved to be a pain.
A solution suggested for the issue is to use this free, open source third party downloader in github
I'm not sure that it will work as you expect, it might have the same problem. I didn't try, but i hope it helps