My project build.gradle file shows a warning: `Kotlin version that is used for building with Gradle ...

# compose

[robnik]

My project build.gradle file shows a warning: Kotlin version that is used for building with Gradle (1.4.30) differs from the one bundled into the IDE plugin (1.4.21). It's on the line inside buildscript.dependencies: `classpath "org.jetbrains.kotlinkotlin gradle plugin$kotlin_version"`` . I thought we were supposed to use Kotlin 1.4.30 now? The Kotlin plugin doesn't seem to have an update available. I'm getting a much worse internal compiler error later, so I'm trying to sort out this warning first.

[Vsevolod Ganin]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1612984407135300?thread_ts=1612982100.129800&cid=CJLTWPH7S

[Vsevolod Ganin]

But this will not help resolve internal compiler error. Could you post compiler stacktrace here if you have one?

[robnik]

Okay, let me see if I can attach a text file...

[robnik]

stacktrace.txt

[Vsevolod Ganin]

Looks bad

[Vsevolod Ganin]

Caused by: org.jetbrains.kotlin.codegen.CompilationException: Back-end (JVM) Internal error: Couldn't inline method call 'Column' into
public final fun invoke(paddingValues: androidx.compose.foundation.layout.PaddingValues, `$composer`: androidx.compose.runtime.Composer?, `$changed`: <http://kotlin.Int|kotlin.Int>): kotlin.Unit defined in com.mycompany.androidapp.`ComposableSingletons$AutoLoanAndInsuranceScreenKt`.<clinit>.<no name provided>

[Vsevolod Ganin]

Probably should find minimal reproducer and file a bug

[robnik]

@Vsevolod Ganin Bug with Kotlin/Jetbrains or Compose/Google? I do have a very simple demo. It doesn't like the ::method refs...

package co.demo

import androidx.compose.foundation.layout.*
import androidx.compose.material.*
import androidx.compose.runtime.*

@Composable
fun Problem() {
    fun foo() { }
    Scaffold() { _ ->
        Column() {
            Button(onClick = ::foo) { }
        }
    }
}

[robnik]

Good news is that { foo() } is a simple replacement.

[Vsevolod Ganin]

Ah, great to hear. Actually I stumbled upon exactly this bug half a year back but never bothered that much to file a bug 🙂

[Vsevolod Ganin]

Actually I tried now with alpha12 to replace my lambda with function reference (I marked the problem place with FIXME) and it compiles fine. I guess my problem is fixed now. Are you sure you are using latest compose compiler? Or maybe these are not same issues after all

[robnik]

Did you try my code snippet? Without the Scafford part it compiles okay, so not not all function refs are a problem. Pretty sure I'm using alpha12.

[Alex Bieliaiev]

@robnik did you try to move nested foo function to the top-level scope?

[Vsevolod Ganin]

Did you try my code snippet?

Ok, tried now and can confirm that compiler crashes. Compiler definitely shouldn’t crash. From the stacktrace I got the idea that it has to do with Compose compiler so imo you should file a bug to compiler component https://issuetracker.google.com/issues?q=componentid:610764

[robnik]

Looks like moving the nested function to top-level also fixes it. I reported a bug.