You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is some code in the Android version, that should be used for re-initializing download-tasks that haven't finished while the app was running.
As we can't surely say which tasks belong to our app when restarting the app (the browser may also has some items in there) and the filter for running, paused and queued tasks doesn't work on Android 4.x (see #33), I think the best option we currently have is to stop all downloads that are done against the temporary location.
The downloads that are going to a custom location cannot be queried but you can see that they finished by the time the file is already downloaded.
I'm also working on a check for re-initializing an ongoing download if you try to download the file again. The system then throws an error that this file already is queued and we'll just catch it up, because it was in the native queue, but not in the queue of this lib.
This is just required as long as we use Androids implementation of the DownloadManager. #34 would make this request invalid.
The text was updated successfully, but these errors were encountered:
SimonSimCity
changed the title
[Android] Stop downloading task without custom location
[Android] Stop downloading task when app is killed or crashes without custom location
Nov 22, 2016
SimonSimCity
changed the title
[Android] Stop downloading task when app is killed or crashes without custom location
[Android] Stop download tasks without custom location when app is killed or crashes
Nov 26, 2016
There is some code in the Android version, that should be used for re-initializing download-tasks that haven't finished while the app was running.
As we can't surely say which tasks belong to our app when restarting the app (the browser may also has some items in there) and the filter for running, paused and queued tasks doesn't work on Android 4.x (see #33), I think the best option we currently have is to stop all downloads that are done against the temporary location.
The downloads that are going to a custom location cannot be queried but you can see that they finished by the time the file is already downloaded.
I'm also working on a check for re-initializing an ongoing download if you try to download the file again. The system then throws an error that this file already is queued and we'll just catch it up, because it was in the native queue, but not in the queue of this lib.
This is just required as long as we use Androids implementation of the DownloadManager. #34 would make this request invalid.
The text was updated successfully, but these errors were encountered: