It seems like

runBlocking {}

isn't possible anymore, since you can't use the

lifecycleScope

with it...

Using

runBlocking

on Android for something other than tests is almost always a bad idea.

I have a SyncAdapter with this:

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 }

You're not right, the service will not be "blocked". It'll stay there until you ask it to stop or the user or Android stops it.

That's for a regular service, but a SyncAdapter binds to a service, so doesn't the service get stopped when Android unbinds it at the end of the Sync?

You can check the sources of

LifecycleService

from your IDE to find out, and be sure.