Hi there :slightly_smiling_face: I'm hoping someon...

# android

[Eran Boudjnah]

Hi there 🙂
I'm hoping someone can help. In KMP our project we have a debug and a release build types.
The app module is a plain Android module.
We have a second module that's a KMP module.
Every dependency from the KMP module shows in red in the app module.
I fixed it by replacing

androidMain {
    dependsOn(commonMain)
}

with

androidDebug {
    dependsOn(commonMain)
}

androidRelease {
    dependsOn(commonMain)
}

I'm wondering why this works. Is something wrong with my configuration, is this the expected behaviour, or...?

[Landry Norris]

What android gradle plugin version?

[Eran Boudjnah]

com.android.tools.build:gradle:7.3.1
org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.10

[Landry Norris]

I don’t see this on 7.3.1 and 1.7.10, so it’s likely not a gradle plugin issue. I believe androidRelease and androidDebug are separate source sets. I’d keep androidMain dependsOn commonMain and add android{Release,Debug} dependsOn androidMain

[Eran Boudjnah]

How come without adding dependencies for release and debug Android Studio isn't recognizing files from commonMain? I mean, it still compiles and runs, so it seems like a bug somewhere?

[Eran Boudjnah]

It's a good idea to have release/debug depend on one sourceset, so I'll definitely make that change.

[Landry Norris]

Not sure. There’s often issues in AS with recognizing uncommon source set configurations.

[Landry Norris]

I’d just make sure that your android configuration source sets depend on androidMain and androidMain depends os commonMain.

[Eran Boudjnah]

Yup. I'll do that, thanks Landy!
Is debug/release considered uncommon?

[Eran Boudjnah]

Just a quick update...

androidMain {
            dependsOn(commonMain)
        }

        androidDebug {
            dependsOn(androidMain)
        }

        androidRelease {
            dependsOn(androidMain)
        }

Does not work.

androidDebug {
            dependsOn(commonMain)
        }

        androidRelease {
            dependsOn(commonMain)
        }

Does.

[Eran Boudjnah]

I suspect the IDE actively chooses to ignore androidMain for some reason, so depending on it is no good.

[Landry Norris]

Can you send a snippet with your build.gradle.kts?

[Eran Boudjnah]

I can't unfortunately, client NDA 😞
But maybe I could share a relevant section, if that helps?
Also, I'm using groovy, so it's build.gradle 🙂

[Landry Norris]

Makes sense. I haven’t done the android app in a separate module in a while (I tend to put the MainActivity and manifest in androidMain directly), but I’d imagine that somewhere, there’s a dependency that’s not set right. How are you doing androidDebug { dependsOn(commonMain) }? Wouldn’t commonMain be in the KMP module and androidDebug be in the android app module?

[Landry Norris]

Are you using implementation(project(“:module-name”)) to depend on the KMP module?

[Eran Boudjnah]

I have one KMP library module with both commonMain and androidMain.
The main app module (and some other modules) are pure Android modules.
They depend on the KMP module, and compile and run fine. But in the IDE, sources aren't linked until I introduce the changes mentioned above.

[Eran Boudjnah]

Are you using implementation(project(“:module-name”)) to depend on the KMP module?

Yes 🙂