I’m trying to migrate a configuration like:

plugins {
    kotlin("multiplatform")
    id("org.jetbrains.compose") version Versions.JetBrains.Compose.desktop
}

to a convention plugin where:

with(pluginManager) {
  apply("org.jetbrains.kotlin.multiplatform:${catalog.findVersion("kotlin").get()}")
  apply("org.jetbrains.compose:${catalog.findVersion("desktopCompose").get()}")
}

but when I run it throws saying (same for the second line if I comment the first):

Caused by: org.gradle.api.plugins.UnknownPluginException: Plugin with id 'org.jetbrains.kotlin.multiplatform:1.7.10' not found.
	at org.gradle.api.internal.plugins.DefaultPluginManager.apply(DefaultPluginManager.java:144)

I’ve checked here and the syntax of the plugin is correct. What am I missing here? 🤔 Thanks!

What is

kotlin-js-store

? Recently it is being autogenerated in my projects that target JS

I want to register an observer to a lifecycleOwner and remove it when this lifecycle is no longer resumed. I am currently doing:

lifecycleOwner.repeatOnLifecycle(Lifecycle.State.RESUMED) {
    launch {
        val callback = LifecycleEventObserver { _: LifecycleOwner, event: Lifecycle.Event ->
            if (event == Lifecycle.Event.ON_PAUSE) {
                // do something on pause
            }
        }
        lifecycleOwner.lifecycle.addObserver(callback)
        try {
            awaitCancellation()
        } finally {
            lifecycleOwner.lifecycle.removeObserver(callback)
        }
    }
}

But this

try/finally

with the

awaitCancellation()

combination feels a bit weird. Is there a nicer way to do this in general?

Whats the recommended way to do Navigation on compose desktop? It seems the official one mentioned in compose doc (https://developer.android.com/jetpack/compose/navigation) is not implemented.

Hello! I have a question regarding back swipe gestures. The sample app lets me swipe back. But my implementation does not (neither android nor ios). The Back button works as intended. I am wondering if I am missing something?

Using context receivers for dependency injection, is that a valid use-case?

interface Blah {
    suspend fun doSomething()
}

class BlahImpl : Blah {

    context(Connection)
    suspend fun doSomething() { ... }

}

currently the above doesn't compile (and the compiler actually just outputs garbage without hinting that this is not allowed - KT-58442) unless you add the context receiver on the

doSomething()

in the interface as well

interface Blah {
    context(connection)
    suspend fun doSomething()
}

which leads to my question, should the interface really know in what context(s) it will be used, doesn't that defeat the purpose of an interface? the actual context in which the implementation runs sounds like implementation detail that now pollutes the interface. maybe the same can be said for suspend, should that really be in the interface too? that being said, if it's not in the interface, then you would be forced to specify at the call-site which implementation you are referring to which would then either require a context or no context or to call it from a coroutineScope or just normally.

I can’t seem to get autocorrect to work. This is what my detekt.gradle file looks like. Any ideas?

apply plugin: 'io.gitlab.arturbosch.detekt'

detekt {
    parallel = true
    config = files("$rootDir/codeQuality/detekt.yml")
    autoCorrect = true
    reports {
        xml {
            enabled = false
        }
        txt {
            enabled = false
        }
    }
}

Is there any library in kmp can do convert from byteArray into file? Then this file I will upload using ktor client.

Is it possible to implement Google authentication in kmm and let the ktor-server handle it so that I can use that token to query data from my PostgreSQL database?

hello again, has anyone figured out how to load fonts in compose/canvas?