Does multiplatform library have the access to run background tasks for android and iOS? Sample use case is to monitor their location even app is in the background. Thanks in advance!

Hi All Is there any way to use Android Context in the KMM test?

what's the right way to change the TopAppBar title (or any other prop for that matter) dynamically from each screen? So right now I have 1 Scaffold which use and inside is the NavHost, passed to each

composable

inside is

scaffoldState

where I go

scaffoldstate.value.title = { Text("Screen A" }

and the primary Scaffold just populates its own topAppBar with MyAppBar(title = scaffoldState.title) but this causes a lot of jank when switching between bottom bar destinations and sometimes one screen ends up with the title of the other and it's just bad having 2 Scaffolds causes a visual effect where you can see them being swapped out, Now In Android does it really well but the code is so convoluted I couldn't really pin down even where the switch was happening

How to convert a compose

ImageVector

to an Android

Bitmap

? Note - need to use it for

CustomTabsIntent.Builder#setCloseButtonIcon

so not within a composable. https://developer.android.com/reference/androidx/browser/customtabs/CustomTabsIntent.Builder#setCloseButtonIcon(android.graphics.Bitmap)

How does OkHttp compare to Ktor Client? Seems they land on similar use cases? Why might I prefer one over the other?

I’m in the process of migrating from buildSrc to build-logic, and I was studying idiomatic-gradle and also Google’s now-in-android repository. But I’m having a problem, in buildSrc I’ve classes and enums that can be accessed by any module’s

build.gradle.kts

, but when using build-logic, I can’t share them, it throws

org.gradle.internal.exceptions.LocationAwareException

. Surely I’m doing something wrong because Google’s sample uses it with no problem here, but I don’t know what’s missing 😞 Any hint? Thanks 🙏

I set

allWarningsAsErrors = true

in all of my projects because I find that addressing warnings before they become bugs makes life easier. However a lot of build functionality uses the same concept of warning to flag things that can't be addressed by the user. There's been discussion about this before (e.g. here and here) and now I've run into it again when trying to update to Kotlin 2.0.0 in a project that uses kapt. If I set

kapt.use.k2 = false

I get this warning:

> Task :app:kaptGenerateStubsDebugKotlin FAILED
w: Kapt currently doesn't support language version 2.0+. Falling back to 1.9.
e: warnings found and -Werror specified

and if I set

kapt.use.k2 = true

I get this warning:

> Task :app:kaptGenerateStubsDebugKotlin FAILED
w: K2 kapt is an experimental feature. Use with caution.
e: warnings found and -Werror specified

in both cases my only recourse to using Kotlin 2.0.0 is to set

allWarningsAsErrors = false

which can lead to the quality of my project degrading. It would be nice if

allWarningsAsErrors

differentiated between warnings that are resolvable by the user, and warnings that are not.

What is

iosX64()

for? Are there some x64 ios devices? I though it was all arm always?

Just bumped to Kotlin

1.7.0

and am seeing this in Kotest:

Found interface kotlin.time.TimeMark, but class was expected
java.lang.IncompatibleClassChangeError: Found interface kotlin.time.TimeMark, but class was expected
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor.intercept-0E7RQCE(SpecFinishedInterceptor.kt:37)
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor$intercept$1.invokeSuspend(SpecFinishedInterceptor.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

do I need to wait for a new Kotest version? ** Not a contribution

anyone find anyway to show toasts in kmm?