I m not sure how immediate works doesn t it run on the calle

Question

I m not sure how immediate works doesn t it run on the caller s thread and Hi would be printed before Finished maybe I have to add a `yield `

gildor · Answer

Immediate just avoid dispatching if it s main thread Imagine that without immediate coroutine always does `<http mainHandler post|mainHandler post> work ` and with immediate it will do `if isMainThread work else post work `

gildor · Answer

But because you do delay it will always also do mainHandler postDelay work 30 just because it s only way for non blocking delay

gildor · Answer

If you want to do something on caller s thread you can use Unconfined

gildor · Answer

But what is exactly your use case for it

dave08 · Answer

In the end with immediate does all the code in `launch` get run before the method exits or can such code leak I have a SyncAdapter that I need to use its service s lifecycleScope on

dave08 · Answer

But I don t want work to leak

dave08 · Answer

And runBlocking won t give me the Service s scope so if Android kills the service the task might leak

gildor · Answer

It will leak if it will not be cancelled

gildor · Answer

Same as with other dispatcher

dave08 · Answer

That s why I want to use `lifecycleScope` with `launch`

gildor · Answer

Yes make sense I m still didn t get your case

gildor · Answer

Do you launch something in a service

dave08 · Answer

``` override fun onPerformSync account Account bundle Bundle s String contentProviderClient ContentProviderClient syncResult SyncResult = coroutineScope launch syncEventTrigger onSyncStart context syncResult onStart i Sync Started onCompletion i Sync Stopped collect let Unit ```

dave08 · Answer

Which Android runs in the context of a bound service

dave08 · Answer

So I made that service into a `LifecycleService` that provides me with a `lifecycleScope` extension from ktx

dave08 · Answer

But I m afraid onPerformSync will exit before the tasks are finished in `launch`

dave08 · Answer

Then Android might unbind the Service and cancel all my tasks because it thinks I m finished already

dave08 · Answer

That s why I wondered that maybe immediate maybe stops onPerformSync from exiting since it s running on it s thread

dave08 · Answer

I m talking about this <https developer android com training sync adapters creating sync adapter html>

dave08 · Answer

But I replaced the Service there with <https developer android com reference androidx lifecycle LifecycleService html>

gildor · Answer

If so just cancel scope on service onDestroy

dave08 · Answer

I don t understand how that would help That s handled by `lifecycleScope` automatically I think the problem knowing whether onPerformSync exits before the work is all done

dave08 · Answer

Unless you mean to use runBlocking and just handle the cancelling myself

dave08 · Answer

which might be a bit harder from an adapter using a bound service