coroutineworker | Kotlin Coroutine-based workers | Android library

Using this library "androidx.work:work-runtime-ktx:2.5.0" to run a background thread. But OneTimeWorkRequest is being cancelled everything i exit the screen. What i am trying to acheive is set it run on the application level can someone help please or some hints? here is my code below :

I didn't realize there was more than one constructor for periodic work requests. The clue to my confusion was in the comments of the accepted answer.

I have a few special cases I am trying to solve for while scheduling work. One of them involves doing work immediately and then creating a periodic work request. I found this in the Android's PeriodicWorkRequest documentation:

This work executes multiple times until it is cancelled, with the first execution happening immediately or as soon as the given Constraints are met.

I figured that this meant work would execute upon creating a request. However, this was not what happened in my test implementation. (For this work there is no need for a CoroutineWorker or network connection constraints but its applicable to my business need so I am testing it)

Starting Worker

My app is checking for unread emails in the background, the problem is that i need to save and retrieve lastCheckedDate when i last checked for emails so i can show only newly received emails.

For retrieving data from datastore i use observeLastCheckedDate() and i must call it with handler because if i dont i get:

java.lang.IllegalStateException: Cannot invoke observe on a background thread

Function observeLastCheckedDate() get called but while it finish(updates lastCheckedDate), workManager task is already finished with not-updated var lastchecked date.

In main class i avoid this problem by creating and invoking callback but here that does not work(it makes whole app freeze), so we somehow need to wait for that function to finish or get some new way of retreiving data from datastore.

So I replaced all of my Jobs to these Work representation.

I have two problem in the current state of refactoring.

I have many worker classes, let's say these are W1,W2,W3...

My problem is, when I schedule a work as onTime and periodic as well. I use uniq works with uniq tags. My problem is, when I queue W1 as a periodic with "W1_TAG" tag and after that I would like to create a onTime from W1 with the same tag, it doesn't starts, because there is an another Work with the same tag.

I would like to achive that, If I start W1 worker, and after that start W2 worker as periodic, and after that I start W2 as onTime, the operation will be the following:

-W1 starts -W2 periodic sees that, W1 runs, so he will wait untill w1 succeeded -w2 onTime sees that, there is an another W2 (doesn't matter that it is periodic), and he will be removed? by WorkManager, so w2 periodic remains and w2 on time wont run

I know there is an enqueUniqWork possibility, but It only append, or keep the pervious worker, and this is not working different tags.

So currently I solved this, by add different tags, but I wondering, can I samehow resolve this?

Work scheduling

I'm trying to inject WorkManager with Hilt. first I implement the documentation:

Inject a Worker using the @HiltWorker annotation in the class and @AssistedInject in the Worker object's constructor. You can use only @Singleton or unscoped bindings in Worker objects. You must also annotate the Context and WorkerParameters dependencies with @Assisted:

I'm learning android development from Android_developer. while using CoroutinesWorker, I encountered a problem whilst working with Kotlin

Logcat

I'm trying to run synchronous jobs using the WorkManager however it seems as if the configuration passed is partially ignored.

Below is my implementation:

App:

I have an Worker that executed periodically. It connects to BLE device and syncs data from it. The connection is done by observers. doWork calling syncRides(). syncRides created an observeForever, and starts connections, when connection is established BleClient.runBleSync() called.

My concerns are the "observeForever" called every 15 min (minimal WorkManager time) and crerates observeForever that not removed. The thing is BleWorker does not have LifecycleOwner for creating "BleClient.connectionStatus.observe" instead of "BleClient.connectionStatus.observeForever". My question is should I be concerned of using observeForever and triggering it every 15 min. Or maybe you can suggest better option like adding and removing observer.

Also, when running without GlobalScope.launch(Dispatchers.Main) there is an error that this function cant run on background thread. So what does Dispatchers.Main mean when running in Worker?

I'm trying to use WorkManager for a periodic to retrieve notifications count from the API, the problem is that I'm using hilt for the dependency injection therefore I can't inject my repository with "@Inject" even if i used @AndroidEnteryPoint. And how I can observe my retrieved data inside the "doWork" function.