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
I'm looking into pausing and resuming DownloadManager, and I saw the following code and comments in Downloader.java:
// WAITING FOR THE FIX TO BE MERGED
// https://android-review.googlesource.com/c/platform/packages/providers/DownloadProvider/+/2089866
public void pause(long downloadId) {
// ContentValues values = new ContentValues();
// values.put(Downloads.Impl.COLUMN_CONTROL, Downloads.Impl.CONTROL_PAUSED);
// values.put(Downloads.Impl.COLUMN_STATUS,
// Downloads.Impl.STATUS_PAUSED_BY_APP);
// downloadManager.mResolver.update(ContentUris.withAppendedId(mBaseUri,
// ids[0]), values, null, null)
}
It seems mResolver and mBaseUri are private fields in DownloadManager. If it's the case, even if the bug fix is merged, would we be able to pause/resume DownloadManager? I'm also not sure where the Downloads.Impl... constants come from and if they're accessible to us.
Thanks for the great work!
The text was updated successfully, but these errors were encountered:
Is this a bug report, a feature request, or a question?
Question.
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
The question is specific to Android.
Environment
Environment:
react-native-background-downloader: 3.2.0
Target Platform:
Android API 34
Expected Behavior
I'm looking into pausing and resuming
DownloadManager
, and I saw the following code and comments inDownloader.java
:It seems
mResolver
andmBaseUri
are private fields inDownloadManager
. If it's the case, even if the bug fix is merged, would we be able to pause/resumeDownloadManager
? I'm also not sure where theDownloads.Impl...
constants come from and if they're accessible to us.Thanks for the great work!
The text was updated successfully, but these errors were encountered: