I'm trying to update to Kotlin 2.2.20, but I'm getting a problem during the configuration phase:

An exception occurred applying plugin request [id: 'buildsrc.conventions.lang.kotlin-multiplatform']
> Failed to apply plugin 'buildsrc.conventions.lang.kotlin-multiplatform'.
   > Future was not completed yet 'Kotlin Plugin Lifecycle: (root project 'snakeyaml-engine-kmp') stage 'EvaluateBuildscript''

Full logs here. I cannot reproduce locally, although admittedly I have a Mac, and the build works fine on a MacOS worker. Is anyone else seeing this as well? Or having a Linux/Windows machine where it reproduces?

Does gradle build cache work with kmp to cache the xcframework stuff from ios build? If so, how does it play with

umbrella

modules? Say umbrella consists of 10 modules and that is cached. If one module changes, would I still get a cache hit on the 9, even if its exposed to ios via the umbrella?

this may as well be a Gradle problem, so let me cross-post it here: https://kotlinlang.slack.com/archives/C0B8H786P/p1758465878216939

I just realized that many of my projects have the following in the

GRADLE_OPTS

env var:

-Dkotlin.incremental=false

I'm guessing that's not actually doing anything because

-D

is a meant for JVM properties, but is there any chance that's getting forwarded to KGP?

Is there a way to a create Kotlin compilation (

agp-9

) that contributes the main jar but does not leak its

compileOnly

dependencies to the main compilation? • If I use

main.associateWith(agp-9)

, the dependencies are automatically added • I can configure the dependencies manually but then

internal

declarations are not seen from

main

, I'm guessing because of

friendSourceSets

Is there a way?

In a KMP+Android project, an

androidUnitTest

dependency's symbols are not found during

clean testReleaseUnitTest

, unless the dependency is removed,

testReleaseUnitTest

is executed again, the dependency is re-added, after which

testReleaseUnitTest

succeeds. Does this ring a bell to anyone? Details in 🧵.

Hey everybody, I am building currently my first gradle plugins and I am running into some issues because it's currently an old project so I am migrating stuff, and it's kinda messy a little bit, but I will be sharing some of my code snippets over here so if someone has a better understanding would explain to me why this is happening. This is my plugin

/**
 * Minimal Hilt convention:
 * - Applies Hilt Gradle plugin and KSP
 * - Wires hilt-android + hilt-compiler (KSP)
 * Assumes the module already applies com.android.* and kotlin-android outside.
 */
class AndroidHiltConventionPlugin : Plugin<Project> {
    override fun apply(target: Project) = with(target) {
        // Apply external plugins to the target project
        pluginManager.apply("com.google.dagger.hilt.android")
        pluginManager.apply("com.google.devtools.ksp")

        // Access the root version catalog named "libs"
        val libs = extensions.getByType<VersionCatalogsExtension>().named("libs")

        dependencies {
            add("implementation", libs.findLibrary("hilt-android").get())
            add("ksp", libs.findLibrary("hilt-android-compiler").get())
        }
    }
}

My register in build.gradle for build logic.

register("androidHilt") {
            id = "com.yinzcam.android.hilt"
            implementationClass = "yinz.cam.build_logic.conventions.AndroidHiltConventionPlugin"
        }

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext.kotlinVersion = "2.1.0"
    ext.kotlinCoroutinesVersion = '1.6.4'
    ext.kotlinSerializationVersion = '1.0.1'
    ext.dokkaVersion = "0.10.1"
    def gradlePluginVersion = "8.9.1"

    def hiltVersion = '2.57'
    def kspVersion = '2.1.0-1.0.29'

    repositories {
        google()
        mavenCentral()
        mavenLocal()
        jcenter()
    }
    dependencies {
        classpath "com.android.tools.build:gradle:$gradlePluginVersion"
        classpath 'com.google.gms:google-services:4.3.14'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$project.ext.kotlinVersion"
        classpath "org.jetbrains.kotlin:kotlin-serialization:$kotlinVersion"
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.9.5'
        classpath "org.jetbrains.dokka:dokka-gradle-plugin:$dokkaVersion"
        classpath "org.jfrog.buildinfo:build-info-extractor-gradle:5.2.5"
        classpath "androidx.navigation:navigation-safe-args-gradle-plugin:2.5.3"
        classpath "com.google.android.libraries.mapsplatform.secrets-gradle-plugin:secrets-gradle-plugin:2.0.1"
        classpath "org.jetbrains.kotlin:compose-compiler-gradle-plugin:$project.ext.kotlinVersion"
        classpath "com.google.dagger:hilt-android-gradle-plugin:$hiltVersion"
        classpath "com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin:$kspVersion"
    }
}

plugins {
    alias(libs.plugins.hilt) apply false
}

This build.gradle is the one that is outside for all of the project and the main module app since the app isn't modularized still and this is the one responsible for dependencies and inner plugins

buildscript {
    repositories {
        google()
        mavenCentral()
        mavenLocal()
        jcenter()
        flatDir {
            dirs 'libs'
        }
    }
    dependencies {
        classpath "com.android.tools.build:gradle:$project.ext.gradlePluginVersion"
        classpath "com.google.firebase:firebase-appdistribution-gradle:$project.ext.firebaseGradlePlugin"
    }
}

apply plugin: 'com.android.application'
apply plugin: 'project-report'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-kapt'
apply plugin: 'kotlin-parcelize'
apply plugin: 'kotlinx-serialization'
apply plugin: 'com.google.firebase.appdistribution'
apply plugin: "com.google.android.libraries.mapsplatform.secrets-gradle-plugin"
apply plugin: 'org.jetbrains.kotlin.android'
apply plugin: 'org.jetbrains.kotlin.plugin.compose'
apply plugin: 'org.jetbrains.kotlin.plugin.serialization'
//apply plugin: 'com.google.devtools.ksp'
//apply plugin: 'com.google.dagger.hilt.android'

here where I commented apply plugin --> Up. I was trying to add my hilt plugin -->

plugin {
id ("com.yinzcam.android.hilt")
}

but it's not detecting it any idea about it

line: 17

An exception occurred applying plugin request [id: 'com.yinzcam.android.hilt']
> Failed to apply plugin 'com.yinzcam.android.hilt'.
   > Configuration with name 'implementation' not found.

I have a Kotlin multiplatform gradle project, and I would like the generated code to contain the git change id and build date. Is there a way to pass that to the compiler so I can display it in the welcome screen?

Recently I start having this issue a lot If I have for example a custom group "nonWeb" and I add an expect in that "nonWeb" group I can create actual in android and desktop without issues, but it's not recognized by "ios", It's only recognized by "iosArm64", "iosX64" and "iosSimulatorArm64" Same for dependencies, if I add a dependency to nonWeb it's not added to ios

Can I disable some K/N tests (and their matching compile and link tasks) from the KGP API without having to rely on task names?

Is it possible to configure kotlinUpgradePackageLock task to execute automatically when needed? Now build sometime failing with message that kotlinUpgradePackageLock should be executed. I need in such cases silently execute kotlinUpgradePackageLock without breaking the build process.

What's everyone thoughts on making overloads for Kotlin consumers in Gradle code:

fun foo(action: Action<Bar>) {
        TODO()
    }

    /**
     * Overload for Kotlin callers
     */
    fun foo(action: Bar.() -> Unit) {
        TODO()
    }

Is it really that important to transform the lambda parameter in a receiver? If I really want to, isn't it the whole point of the sam-with-receiver plugin? Are there any upsides to do this?

This message was deleted.

How can I properly configure KMP modules to work with Android flavors so that dependencies between shared KMP modules resolve correctly? 🧵

Might be a weird question, can someone tell me where I can find plugin class for

org.jetbrains.kotlin.plugin.parcelize

? Specifically the class that is being called via apply when we put this dependency in

plugins { }

block of a build file

I’m seeing compile tasks for dependencies added for a KMP module being called during Gradle sync.

kotlin {
    sourceSets {
        androidMain {
            dependencies {
                api(projects.core.initializers.api)
            }
        }
    }
}

> Task :core:initializers:api:checkKotlinGradlePluginConfigurationErrors SKIPPED
> Task :core:initializers:api:processResources UP-TO-DATE
> Task :core:initializers:api:compileKotlin
> Task :core:initializers:api:compileJava NO-SOURCE
> Task :core:initializers:api:classes UP-TO-DATE
> Task :core:initializers:api:jar UP-TO-DATE

I could not find anything about it, but it does not seem normal to run them before task execution phase. Any idea what could it be?

We've missed adding it into initial Kotlin 2.2.20 what's new, but added now - in this release we've added a bunch of helpers for library publication to Maven Central: https://kotlinlang.org/docs/whatsnew2220.html#improvements-for-library-publication

I wanted to move to JDK 25 for Kotlin. That meant I also had to move to Gradle 9.20. Is it just me, or is JDK 25 with Gradle 9 much, much slower than JDK 21 with Gradle 8?

Instead of building and running my program in about 10 seconds, just rerunning the code (without a full rebuild, just a few files changed) takes over a minute now.

Often when running my tasks in a medium-size projects (7-8 modules), I get like 10 to 30s of just

> IDLE

and Gradle staying at 0%, I have this parameters in my

gradle.properties

# Gradle optimization flags
org.gradle.caching=true
org.gradle.configuration-cache=true
org.gradle.jvmargs=-Xmx4g -XX:MaxMetaspaceSize=1g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
org.gradle.parallel=true

And I don't understand why it's so slow to start tasks, even just a small run task for tests where I just changed 1 file it can take like 20s of Idling

Hello everyone. I've created a Kotlin coroutines validation package for spring. It's in Beta. It's my first package and I didn't want to publish it to maven until it's ready. Did I do the right thing to publish it on jitpack ? Any recommendation ? Here's the package: https://github.com/danygiguere/spring-validation-dsl

Hello guys, for some weird reason I need to download a project's dependencies, zip the cache and use it to build the project in a different environment, no downloading. Is this possible? If so, how?

Hello, after upgrading to Gradle 9.2.0 and JReleaser 1.20.0, I'm not able to publish anymore on Maven Central, it just refuses my GPG keys and I've tried for 8 hours to publish a new update of my library I have a GitHub Action for publishing, and on the 30 attempts for today, it always failed with

> Task :kore:jreleaserDeploy
...
[ERROR] JReleaser failed after 3.042 s
...
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':kore:jreleaserDeploy'.
...
Caused by: org.jreleaser.model.JReleaserException: Did not find public key for signing. Ensure a value has been configured and properly formatted without indentation

(all ... are skipped lines of logs) I've created a new gpg key, uploaded it to many servers, validated it locally many times, tried 25 times to upload it on GitHub, verified that it's LF, on the last attempt I even tried to encode it into base64 but still can't manage to publish my library I'm just very exhausted and feel like my day was a waste a time (only coded for like 10 minutes to fix a bug), what am I missing ? Why is it so hard ?

How can I create an integration test task using multiplatform plugin without executing it by default when running check? jvm { val jvmTest = compilations.getByName("test") val integrationTest = compilations.create("integrationTest") { associateWith(jvmTest) } testRuns.create("integrationTest") { setExecutionSourceFrom(integrationTest) } } }

Hello Good Evening every one. While a run the app not facing any error. But while i Generate Bundle then i getting the issue. Unable to find method ''com.android.tools.r8.D8Command$Builder com.android.tools.r8.D8Command$Builder.setBuildMetadataConsumer(java.util.function.Consumer)'' 'com.android.tools.r8.D8Command$Builder com.android.tools.r8.D8Command$Builder.setBuildMetadataConsumer(java.util.function.Consumer)' Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.) Any one have idea about this.

I'm trying to fix a deprecation error to make sure it still works in gradle 10. However, I have no idea where this comes from. This is the error:

The archives configuration has been deprecated for artifact declaration. This will fail with an error in Gradle 10. Add artifacts as direct task dependencies of the 'assemble' task instead of declaring them in the archives configuration. Consult the upgrading guide for further information: <https://docs.gradle.org/9.2.0/userguide/upgrading_version_9.html#sec:archives-configuration>
        at build_1i0wfhmjqf4vbrs7fnkm6eki1$_run_closure2.doCall$original(/home/elias/prog/array/array/build.gradle:80)

The code in question should work fine, it's just a

jvm() { ... }

block. The gradle file is here: https://codeberg.org/loke/array/src/branch/master/array/build.gradle Any suggestions as to what I should fix?

Are the compilation tasks for the new KMP Android library target

KotlinJvmCompile

implementations?

I got a KMP hierarchy like this, and I am interested in sharing some code inside

jvmAndAndroid

which calls functions from kotlinx.datetime which lives inside the

jvm

target of that library. Particularly I am trying to use

import kotlinx.datetime.toJavaLocalDate

. When I copy-paste the exact same code inside

androidMain

and

jvmMain

I can call

toJavaLocalDate

without issues. If I try to call

toJavaLocalDate

inside

jvmAndAndroid

it is unable to resolve it at all. Is there a way for me to make this work, or is this a limitation due to the android and the jvm targets kinda being both jvm but not exactly?

There's a bug somewhere in the compilation task inputs / outputs... every now and then I get a build that passes until I run a clean build with no build cache, when I get compilation errors. Alas, I haven't managed to track it down with a reproducer yet.

Sometimes while making Gradle sync project got exception (see in thread). Anybody know what might be the cause? Gradle 9.3.0-rc-1 Kotlin 2.3.0-RC2