What could be the cause of this?

e: java.lang.Error: Something went wrong while checking for version compatibility between the Compose Compiler and the Kotlin Compiler.  It is possible that the versions are incompatible.  Please verify your kotlin version  and consult the Compose-Kotlin compatibility map located at <https://developer.android.com/jetpack/androidx/releases/compose-kotlin>
	at androidx.compose.compiler.plugins.kotlin.ComposeComponentRegistrar$Companion.checkCompilerVersion(ComposePlugin.kt:274)
	at androidx.compose.compiler.plugins.kotlin.ComposeComponentRegistrar.registerProjectComponents(ComposePlugin.kt:199)
Caused by: java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.cli.common.messages.MessageCollector.report$default(org.jetbrains.kotlin.cli.common.messages.MessageCollector, org.jetbrains.kotlin.cli.common.messages.CompilerMessageSeverity, java.lang.String, org.jetbrains.kotlin.cli.common.messages.CompilerMessageSourceLocation, int, java.lang.Object)'
	at androidx.compose.compiler.plugins.kotlin.ComposeComponentRegistrar$Companion.checkCompilerVersion(ComposePlugin.kt:252)

Versions: • Kotlin 1.7.20 • Compose-jb 1.2.2 • Compose BOM 2023.01.00

I'd recommend not having compose-jb and jetpack compose in the same project. Jetbrains compose pulls down the android compose binaries anyways, so it just makes versioning inconsistent across platforms.

What's the compose-jb way to get material3 for Android? I seem to remember it wasn't available as part of compose-jb, but maybe that's not the case anymore?

compose.material3

What about window-size-class?

You can add other jetpack compose dependencies for Android separately. Adding the BoM sometimes causes issues with multiplatform compose, since it changes the android artifact versions, but not other platforms.

Thanks 👍

Are you overriding the compose compiler version?

I have KMM with Jetpack Compose and JB Compose are in same projects

Like Jonathan, I have both jetpack and jetbrains compose in the same project.

I removed the BOM but still have the same issue… Any other ideas of what it could be?

Did you specify:

composeOptions {
        kotlinCompilerExtensionVersion = "1.4.3"
    }

Yes, in the app module, but this is happening in a library module

Did you add any Jetpack compose lib to

androidMain

?

JB's

compose.material3

and

compose.runtime

.

It's odd that it says there was an error checking versions. It normally prints the minimum and actual Kotlin version if they don't match.

If you look at the

Caused by:

, it fails with

NoSuchMethodError

🤔

@Landry Norris Jetpack throws that error unless you suppress. I dunno about JB's

If you want to take a look, it's the branch 110-gradle of Decouple… Running any task related to Android fails with that error (from the linter to Dokka)

Aiit. I'll take a look.

Not at my computer right now, but the error for compose-jb should read something like 'compose compiler 1.4.0 requires Kotlin 1.8.10, but you appear to be using 1.7.20. You can suppress this error with ... (but don't say I didn't warn you)'

I've seen it multiple times before, but this is a NoSuchMethodError so I think it's more complicated than that. Maybe a version difference with Gradle?

Or JVM difference?

🤔 Reminds me that I should specify a Java toolchain

compose-androidCompilerExtension = "1.4.3"

That line in your libs file is the culprit

What should it be?

It should be 1.3.2 as per your Kotlin version 1.7.20

Give me a second to run it

Is 1.4.3 even out? I makes sense it failed in that case.

It is. But it supports Kotlin 1.8.10 higher

Yep, you're right, that was the culprit. Thanks a lot

That was quick. 1.4.0-rc feels like yesterday