Really multi-platform modules can not be connected...

# multiplatform

[Loboda Deni]

Really multi-platform modules can not be connected to each other as usual? it's not very convenient to work with them in this case

[zalewski.se]

They can, why not?

[Loboda Deni]

when I try to connect it I get a message saying that I can't find the project with this path

[Loboda Deni]

only publication in the local maven repository helps

[zalewski.se]

I have a sample setup here (just to show the issue of navigation between modules) https://github.com/zalewskise/KMP-modules-issue Maybe it will help you

[Loboda Deni]

strange, everything seems to be the same, but I get an error: Unable to resolve dependency for ':core_network@debugAndroidTest/compileClasspath': Could not resolve project :core.

[Loboda Deni]

kotlin {
jvm("android")

sourceSets["commonMain"].dependencies {
implementation(project(":core"))
}

sourceSets["androidMain"].dependencies {
}
}

[Loboda Deni]

Do I need to specify any additional settings?

[Kris Wong]

is core included in settings.gradle?

[Loboda Deni]

Yes

[Loboda Deni]

include(":app")
include(":core_network")
include(":detect")
include(":core")
include(":domain")
include(":f_main")
include(":s_remote")
rootProject.name = "Sample MultiModule"

[Loboda Deni]

it is strange that when you try to connect this module to a regular android module everything works

[Kris Wong]

and project core is using Gradle metadata?

[Kris Wong]

i don't think i have tried adding a MPP as a common dependency in another MPP

[Loboda Deni]

what do you mean metadata?

[Kris Wong]

does core have a jvm target?

[Loboda Deni]

Yes

[Kris Wong]

and what version of Gradle are you using?

[Loboda Deni]

4.0.0

[Kris Wong]

that's your problem

[Kris Wong]

https://blog.gradle.org/gradle-metadata-1.0

[Kris Wong]

4.0 is ancient as far as Gradle is concerned

[Loboda Deni]

I confused in my opinion, in gradle-wrapper.properties version is 6.5.1, and in project classpath gradle 4.0.0

[Kris Wong]

one of those is Gradle and the other is the Android gradle plugin

[Kris Wong]

ok, in that case I am not sure what the issue is. everything seems to check out

[Loboda Deni]

sadly

[russhwolf]

It might help if you put an empty build.gradle.kts in common and also include :common in settings.gradle.kts. I think I've seen gradle fail to resolve nested modules without that.

[Loboda Deni]

I have all the modules at the root, I do not think that this will help

[russhwolf]

Oh sorry, I was looking at Sebastian's setup and thought it was yours

[Loboda Deni]

@Kris Wong I noticed that your project requires version of Android Studio 4.2. I am currently using version 4.0.0. can the problem be in the version of Android Studio?

[Loboda Deni]

I don't understand, I updated the studio, made the configuration identical to yours and at the same time everything works in your project, but not in mine. I haven't come up with anything better than remaking your project by adding my sources there, I still can't understand what the problem is

[Loboda Deni]

@Kris Wong which is funny, in your version, when connecting the module, a direct link is also not created, if I try to switch from the repository module to the class defined in the network module, I'm not going to this class directly, but to the kotlin_metadata file, which is obviously not editable

[Loboda Deni]

it seems this functionality is still not finalized

[zalewski.se]

I'm not going to this class directly, but to the kotlin_metadata file,

This is a known issue:
https://youtrack.jetbrains.com/issue/KT-39571

[Loboda Deni]

no solution yet?