android-workmanager | 易学教程

WorkManger works on Oreo but not Lollipop

阅读更多关于 WorkManger works on Oreo but not Lollipop

问题 WorkManager states that it works on OSes before JobScheduler and the like, yet it doesn't seem to work on API levels that use AlarmManager . I have a PeriodicWorkRequest which runs in intervals just fine on Oreo, but on Lollipop, it only runs the first time. The code in question ( PeriodicWorker.class is my own class of course): WorkManager .getInstance() .enqueue( new PeriodicWorkRequest.Builder( PeriodicWorker.class, PeriodicWorkRequest.MIN_PERIODIC_INTERVAL_MILLIS, TimeUnit.MILLISECONDS )

How to make sure that WorkManager cancels my Worker?

阅读更多关于 How to make sure that WorkManager cancels my Worker?

问题 It's mentioned in WorkManager documentation that cancelling a Worker is best-effort WorkManager makes its best effort to cancel the task, but this is inherently uncertain--the task may already be running or finished when you attempt to cancel it What if i have a use case that it's mandatory that the Worker gets cancelled upon calling one of the cancelling methods? 回答1: As you wrote WorkManager can only try with a best-effort to cancel a work. In particular, if a task is scheduled to run, and

Compile errors after updating to WorkManager 1.0.0-alpha09

阅读更多关于 Compile errors after updating to WorkManager 1.0.0-alpha09

问题 I'm trying to use WorkManager from architecture components. I've upgraded the compileSdkVersion and targetSdkVersion from 27 to 28. gradle sync is successfully done. But build-time error keeps popping up. android.support libraries are using version 28.0.0-rc02 because of the 'android.support:design'. I've tried to add packagingOptions in order to exclude 'proguard/androidx-annotations.pro'. But it didn't help. But this time I got a different error message: Program type already present: com

Why is Android Worker finishing successfully and calling onStopped()

阅读更多关于 Why is Android Worker finishing successfully and calling onStopped()

问题 My current Android app employs androidx.work:work-runtime:2.2.0-rc01 My Worker code resembles this:- class SyncWorker(context: Context, workerParams: WorkerParameters) : Worker(context, workerParams) { private var syncWorkerResult: Result = Result.success() override fun doWork(): Result { return syncWorkerResult } override fun onStopped() { Log.i(TAG, "onStopped() $isStopped") super.onStopped() } } As far as I understand the docs for Worker I shouldnt be seeing the following logs:- 2019-08-21

How to use WorkManager to run a long running job in Foreground

阅读更多关于 How to use WorkManager to run a long running job in Foreground

问题 Due to the problem mentioned in Proper way to tackle and resolve "Excessive network usage (background)" , I plan to move the long running task (sync to cloud) from background to foreground. Currently, I start my delayed WorkManager in Application 's onPause I was planning to use WorkManager , to launch an IntentService 's startForeground - Android - implementing startForeground for a service? But, WorkManager itself unable to launch a Service . May I know how I can achieve so? Is there a way,

Android Work Manager - Does Work Manager will 100% ensure the background execution to be Completed?

阅读更多关于 Android Work Manager - Does Work Manager will 100% ensure the background execution to be Completed?

问题 From what I read from the documentation https://developer.android.com/topic/libraries/architecture/workmanager, It said that: The task is still guaranteed to run, even if your app is force-quit or the device is rebooted. So which mean, the execution that being at the background will 100% be execute until it complete no matter what? For an example case: An Apps have Button that perform Work Manager Implementation that upload data to an Online Database but it required Internet Connection to

Handle response of WorkManager on Network connection Failure

阅读更多关于 Handle response of WorkManager on Network connection Failure

问题 I'm using WorkManager to sync data from my local Room database to server. The issue is that Room gives error to build database in Loop.MainLooper() and when i use it as following it works fine. But I'm unable to return the 'WorkerResult' on SUCCESS or RETRY based upon task completion. How to stop worker when Netwrok is lost? public class TestSyncManager extends Worker { private final WorkerResult[] workerResult = {WorkerResult.SUCCESS}; // @Inject // Dagger2 has not added the support for

Android Work Manager - Does Work Manager will 100% ensure the background execution to be Completed?

阅读更多关于 Android Work Manager - Does Work Manager will 100% ensure the background execution to be Completed?

From what I read from the documentation https://developer.android.com/topic/libraries/architecture/workmanager , It said that: The task is still guaranteed to run, even if your app is force-quit or the device is rebooted. So which mean, the execution that being at the background will 100% be execute until it complete no matter what? For an example case: An Apps have Button that perform Work Manager Implementation that upload data to an Online Database but it required Internet Connection to upload the data. So, my Apps is currently in Offline Mode and I click the Button. My Uncertainty: Will

WorkManager beginUniqueWork doesn't work as expected

阅读更多关于 WorkManager beginUniqueWork doesn't work as expected

问题 Currently, I'm using WorkManager 1.0.0-alpha02. def work_version = "1.0.0-alpha02" implementation "android.arch.work:work-runtime:$work_version" // use -ktx for Kotlin // optional - Firebase JobDispatcher support implementation "android.arch.work:work-firebase:$work_version" I have no problem to execute background worker, by using the following code, when the app quit. Use enqueue, work as expected OneTimeWorkRequest oneTimeWorkRequest = new OneTimeWorkRequest.Builder(SyncWorker.class)

Handle response of WorkManager on Network connection Failure

阅读更多关于 Handle response of WorkManager on Network connection Failure

I'm using WorkManager to sync data from my local Room database to server. The issue is that Room gives error to build database in Loop.MainLooper() and when i use it as following it works fine. But I'm unable to return the 'WorkerResult' on SUCCESS or RETRY based upon task completion. How to stop worker when Netwrok is lost? public class TestSyncManager extends Worker { private final WorkerResult[] workerResult = {WorkerResult.SUCCESS}; // @Inject // Dagger2 has not added the support for dependency injection in worker yet. private ApiHeader mApiHeader; private HandlerThread mHandlerThread;