Ok i've got a mix of gradle version/multiplatform version/intelliJ version that is actually working,...

# decompose

[Adam Brown]

Ok i've got a mix of gradle version/multiplatform version/intelliJ version that is actually working, no one touch anything 😂 except after updating various things, my Android Module now thinks it doesn't have a compose runtime: IncompatibleComposeRuntimeVersionException: The Compose Compiler requires the Compose Runtime to be on the class path, but none could be found. The compose compiler plugin you are using (version 1.3.2) expects a minimum runtime version of 1.0.0.

Anyone run into this before?

[Landry Norris]

Are you using Jetpack Compose or compose-jb? If using compose-jb, make sure to have compose.runtime in commonMain.

[Adam Brown]

ya I've got

implementation(compose.runtime)

In my common module, also added it to my Android module, it doesnt care

[Adam Brown]

and my desktop target works just fine

[Adam Brown]

the only difference I can think of is in my desktop i've got the platform dependency:

implementation(compose.desktop.currentOs)

But theres nothing like that for Android

[Landry Norris]

The same setup (compose-jb + decompose) works for me with

implementation(compose.runtime)
                implementation(compose.foundation)
                implementation(compose.material)
                implementation(compose.ui)
                implementation(compose.materialIconsExtended)

in commonMain

[Adam Brown]

what does your Android module look like then?

[Adam Brown]

or don't you have a separate one?

[Landry Norris]

It looks like I kept the same thing in androidMain, but that shouldn’t affect anything. Should be good to remove it from androidMain.

[Adam Brown]

my setup is slight different, I have 3 modules: Android -> ComposeUI -> Common

[Adam Brown]

but shouldnt really matter

[Landry Norris]

I do the same often, setting up a composeMain, commonMain, and {android,ios}Main.

[Landry Norris]

Makes it easier to add/remove iOS support.

[Adam Brown]

ya

[Landry Norris]

I can;t share my work project, but I can tell you the setup in this project works well for android/ios.
https://github.com/LandryNorris/MultiFactor/blob/main/mobileapp/build.gradle.kts

[Adam Brown]

hhmmm ya interesting, so mine isn't just different source sets, its actually different modules: https://github.com/Wavesonics/hammer-editor/

[Landry Norris]

Which module do you see the error in?

[Adam Brown]

android

[Adam Brown]

which includes composeUi

[Landry Norris]

I noticed you have api(project(":composeUi"))

[Adam Brown]

ya

[Landry Norris]

I don’t think api brings in transitive dependencies. Try explicitly adding compose.runtime to the dependencies block of the android module.

[Landry Norris]

I also noticed you seem to be mixing compose-jb and jetpack compose in the android module. Try replacing

implementation("androidx.compose.ui:ui:$androidx_compose_version")
    implementation("androidx.compose.ui:ui-tooling:$androidx_compose_version")
    implementation("androidx.compose.foundation:foundation:$androidx_compose_version")
    implementation("androidx.compose.material:material:$androidx_compose_version")
    implementation("androidx.compose.material:material-icons-core:$androidx_compose_version")
    implementation("androidx.compose.material:material-icons-extended:$androidx_compose_version")

with the compose-jb equivalents.

[Adam Brown]

ya actually the only one I need there is activity-compose

[Adam Brown]

removed them but it didn't change anything

[Landry Norris]

What happens if you use implementation instead of API to pull in the compose module?

[Adam Brown]

pushed the latest

[Adam Brown]

dependencies {
    implementation(project(":common"))
    implementation(project(":composeUi"))
    api(compose.runtime)
    api(compose.uiTooling)
    api(compose.preview)
    api(compose.foundation)
    api(compose.material)
    //api(compose.material3)
    api(compose.animation)
    api(compose.animationGraphics)
    api(compose.materialIconsExtended)
    implementation("androidx.activity:activity-compose:1.6.1")
}

[Adam Brown]

same error

[Adam Brown]

oh man, very strange, so down in my common module, which shouldn't even have any compose in it at all, I added

val androidMain by getting {
    dependencies {
        api(compose.runtime) // <- added this
        api("org.jetbrains.kotlinx:kotlinx-coroutines-android:$coroutines_version")
        api("io.insert-koin:koin-android:$koin_version")
    }
}

And now it works....

[Adam Brown]

ah i think i see the problem

[Landry Norris]

You have id("org.jetbrains.compose") at the top

[Adam Brown]

im applying the compose plugin there

[Adam Brown]

yyuuuppp

[Adam Brown]

artifact of some early hackery

[Landry Norris]

Wherever you have the compose plugin, you have to have the runtime in every compatible target. That includes iOS if you’re on a high enough version of compose-jb. Just add the artifact and ignore it, or remove the plugin.

[Adam Brown]

ya and i had even added it there explicitly for the desktop target

[Adam Brown]

removing the plugin

[Adam Brown]

hey it's all working again!

[Adam Brown]

thanks for your time