It seems like `runBlocking {}` isn't possible anymore, since you can't use the `lifecycleScope` with...

# android

[dave08]

It seems like runBlocking {} isn't possible anymore, since you can't use the lifecycleScope with it...

[louiscad]

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

[dave08]

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 }

[dave08]

But I don't want the onPerformSync to exit until the collect finishes...

[dave08]

I'm assuming that since the `Service`'s lifecycleScope is using Dispatchers.Main.immediate, that it will block the service until the sync is finished. Am I right?

[dave08]

But then, maybe that's a bit flaky to count on such things... so runBlocking might be better here...

[louiscad]

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.

[dave08]

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?

[louiscad]

You can check the sources of LifecycleService from your IDE to find out, and be sure.