It is unlikely that DownloadManager
will be able to do this. My assumption is that DownloadManager
does not run in your process, but in another process controlled by the system. Internal storage locations are permissions protected and any location that you would provide would be accessible only to your application.
It seems like you have two options.
(1) Supply a file path on "external" storage, when it completes, copy to internal storage, and then delete the file on external storage.
(2) Create a ContentProvider
which DownloadManager
can write to and give it a URI
that corresponds to this ContentProvider
. The ContentProvider
that you implement can write the file to internal storage since it will run in the context of your application.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…