Good morning guys, I’m resurrecting a 2yo Multipla...

# multiplatform

[Davide Giuseppe Farella]

Good morning guys, I’m resurrecting a 2yo Multiplatform Project + Android compose.
I’m now on:
• Kotlin 1.7
• AGP 7.2.1
• Compose 1.2.0-rc03
• Compose compiler 1.2.0
I’ve got some Multiplatform modules and surprisingly I didn’t need to change the Gradle setup

// something/build.gradle.kts
plugins {
    kotlin("multiplatform")
}

kotlin {
    jvm()

    sourceSets {
        val commonMain by getting {
            dependencies {
                implementation("blablabla")

Then I got an Android module

// client/android/build.gradle.kts
plugins {
    id("com.android.application")
    kotlin("android")
}

dependencies {
    implementation(project(":something")

My Gradle Sync succeeds, but in the Android module, all the dependencies from other modules are unresolved ( screen )
The IDE suggests me to add the dependency to the classpath, but the action adds a weird line, without any progress:

implementation(project(mapOf("path" to ":client")))

[agrosner]

did you try deleting .idea files and reimporting via gradle importer

[Davide Giuseppe Farella]

Oh, is that still a solution in 2022? 🤦 I'll try

[Landry Norris]

I find that the current version of Android Studio has this issue a lot. I generally prefer to use IntelliJ IDEA for my KMM development. Maybe a future Android Studio version will fix this.

[Davide Giuseppe Farella]

@Landry Norris Wow, it’s still the case 😞 I remember back in 2019 I was working like that… Shred on IntelliJ and Android blindly on AS 😕