My android artifacts get published with a `-android` suffix and this ruins the build system. For exa...

# multiplatform

[Mendess]

My android artifacts get published with a -android suffix and this ruins the build system. For example I have my-module-core and my-module-foo that depends on core, these get published under com.example:my-module-foo-android:1.0.0. Which would be fine but when I try to pull this artifact in an android app I get this error: Could not find 'com.example:my-module-core:1.0.0', this I guess means that my-module-foo-android is expecting something without the suffix

[Matt Nelson]

Did you apply the kotlin-android plugin to your android app?

[Matt Nelson]

Did you publish the kotlin metadata (what would be published as my-module-foo containing pointer to the -android variant)?

[Mendess]

@Matt Nelson how do I check that?

[Matt Nelson]

Here's what directories look like on Maven Central , for example, my base32 encoding library.

[Mendess]

okay, looks pretty similar to mine

[Matt Nelson]

clicking on the encoding-base32 dir, then the 1.1.3 dir shows all the jars, javadocs, etc.

The one we wanna look at is encoding-base32-1.1.3-kotlin-tooling-metadata.json

[Matt Nelson]

And here's the output of that. https://repo1.maven.org/maven2/io/matthewnelson/kotlin-components/encoding-base32/1.1.3/encoding-base32-1.1.3-kotlin-tooling-metadata.json

[Matt Nelson]

so when your android app pulls from Maven for com.example:my-foo-module:1.0.0, it will pull down that module, check the available platformType, and then provide you with the appropriate -android variant.

[Mendess]

hmm, inside ~/.m2/repository/com/example/ I only have *-android folders, so I guess that means I don't have the metadata

[Matt Nelson]

that is probably why.

run from terminal ./gradlew tasks | grep "publish" and see if you have something that relates to publishing the kotlin metadata.

[Mendess]

[Mendess]

doesn't seem to be

[Matt Nelson]

publishKotlinMultiplatformPublicationTo*

[Matt Nelson]

`Local`/`LocalRepository`/`MavenRepository`

[Matt Nelson]

that should be getting called if you just did ./gradlew publishToMavenLocal

[Mendess]

okay, that makes sense, I was not calling publishToMavelLocal, was calling something else. This fixed it but I've hit another issue

[Mendess]

Execution failed for task ':app:checkDebugDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class com.example.client.BuildConfig found in the following modules: multiplatform-sdk-core-debug-runtime-debug (com.example:multiplatform-sdk-core-android:25.0.0), multiplatform-sdk-full-debug-runtime-debug (com.example:multiplatform-sdk-full-android:25.0.0) and multiplatform-sdk-listening-debug-runtime-debug (com.example:multiplatform-sdk-listening-android:25.0.0)

[Mendess]

(that class is not mine, it's generated by kotlin)

[Matt Nelson]

try changing in the AndroidManifest the com.example to something else, like com.mendess . Will need to create the new dirs and move some classes so the package updates accordingly.

[Mendess]

how so? Edit the android manifest file manually?

[Matt Nelson]

wait. do you have both of these declared in your android app's dependencies block?

dependencies {
    implementation(project(":my-module-foo"))
    implementation("com.example:my-foo-module:1.0.0")
}

If so, just comment out the project one after publishing to Maven Local.

[Mendess]

no, in the android app I don't have it duplicated