I was surprised to see

android.content.Context

being suggested/autocompleted in commonMain code earlier today. Just to verify, I created a new KMP project, and that was no longer the case. After some digging, Ive found that a couple of ios related lines in the gradle file is what changes this behavior. Is this expected given that I only have commonMain and androidMain sourcesets?

listOf(
        iosX64(),
        iosArm64(),
        iosSimulatorArm64(),
    ).forEach {
        it.binaries.framework {
            baseName = "shared"
        }
    }

As of right now, commonMain allows anything that is available in all defined targets. If you only have an android() target set up, then you can use android.content.Context, but once you add ios targets, this should not happen.

Gotcha! I thought it might be something along those lines. I guess keeping an extra empty sourceSet available just to stop this from happening for now would be suitable?

I usually add a linuxX64 or iosArm64 to prevent this.

Arent dependencies resolved for all targets, even if theyre just placeholders? For example, declaring a linux sourceset results in the following: • Could not resolve androidx.annotation:annotation:1.5.0 for :feature:preset:linuxX64Main This might just be a result of the way Ive set things up as well, Im not sure yet!

androidx.annotation stable is not available for multiplatform (the dev01 version is, though). If you add a non-android target, you can’t use it in commonMain.

Youre right! Looks like I have some rethinking to do now that my understanding of how this works has changed 😅 Thanks for the quick responses Landry, I appreciate that!