Update If you need to check already running work manager just because you don’t want duplicate works. You can simply use enqueueUniquePeriodicWork() This method allows you to enqueue a uniquely-named PeriodicWorkRequest, where only one PeriodicWorkRequest of a particular name can be active at a time. For example, you may only want one sync operation to … Read more
You can use setInputData method to send data just like Bundle. /*** Logic to set Data while creating worker **/ val compressionWork = OneTimeWorkRequest.Builder(CompressWorker::class.java) val data = Data.Builder() //Add parameter in Data class. just like bundle. You can also add Boolean and Number in parameter. data.putString(“file_path”, “put_file_path_here”) //Set Input Data compressionWork.setInputData(data.build()) //enque worker WorkManager.getInstance().enqueue(compressionWork.build()) /*** … Read more
WorkManager comes with following features: Provides tasks which can survive process death It can waken up the app and app’s process to do the work thereby guarantees that works will be executed. Allows observation of work status and the ability to create complex chains of work Allows work chaining which allows to segregate big chunk … Read more
In my case, I had to add the following configurations to app’s module build.gradle: configurations { all*.exclude group: ‘com.google.guava’, module: ‘listenablefuture’ } It happens because some dependencies use com.google.guava:guava and com.google.guava:listenablefuture together. It causes a dependency conflict.
Unfortunately, you cannot schedule a work at specific time as of now. If you have time critical implementation then you should use AlarmManager to set alarm that can fire while in Doze to by using setAndAllowWhileIdle() or setExactAndAllowWhileIdle(). You can schedule a work, with onetime initial delay or execute it periodically, using the WorkManager as … Read more
Based on various issues reported on the WorkManager bugtracker, their documentation is not completely precise about the exact behavior of the WorkManager in such edge cases. On certain devices, apps are force stopped when the app is cleared from task manager, so that part is expected. … source Unfortunately, some devices implement killing the app … Read more
“WorkManager has a lot of nice features but its main goal is to use the JobScheduler’s API on older devices”… Wait, but we already have some backports. What’s wrong with them? To cut it short: FireaseJobDispatcher is fine but it requires Google Play to schedule jobs which isn’t good if we’re targeting China, for example. … Read more
This is a known problem at the moment, Architecture Components Release Notes outline the issue and provides a solution to fix it until alpha10 version of work manager library: Known Issue If you run into the following issue: “More than one file was found with OS independent path ‘META-INF/proguard/androidx-annotations.pro’”, please put the following in your … Read more