I am having an issue with my multiplatform library where I build an aar which is resolving correctly...

# multiplatform

[Rahul Rawat]

I am having an issue with my multiplatform library where I build an aar which is resolving correctly but it’s dependecies are not being resolved. Is there any way to transitively add depedencies while using implementation with a aar file inside the libs folder in android?

[Big Chungus]

Yes, declare them as api() as opposed to implementation ()

[Rahul Rawat]

I tried that but it says

Supplied String module notation 'libs/AddressLibrary-android-1.0-SNAPSHOT.aar' is invalid.

[Big Chungus]

Because it is 😀 how are you declaring your transitive dependencies?

[Rahul Rawat]

Like this

api('libs/AddressLibrary-android-1.0-SNAPSHOT.aar') {
        transitive = true
    }

[Big Chungus]

Yeah, that's bullshit. You should never hard code fs paths

[Rahul Rawat]

Than how should I do it. This was how implementation was being done 😅

[Big Chungus]

If that dependency is a module in your project, declare it as api(project("libsAddressLibrary"))

[Rahul Rawat]

It’s actually an aar file

[Big Chungus]

You mean it's not coming from maven central or some other repo?

[Big Chungus]

I.e. you just built and copied over aar file?

[Rahul Rawat]

Kind of but not just aar. I copied all the files inside maven local for the library for android

[Big Chungus]

Yeah, no wonder it doesn't work. Just publish your lib to maven local and add it as repository to your app. Then declare a dependency as usual implementation ("groupnameversion")

[Big Chungus]

Alternatively google about gradle included builds and link the two projects together that way.

[Big Chungus]

Here's an included build example for you to explore if you want to go that route https://github.com/mpetuska/kmdc/blob/master/sandbox/settings.gradle.kts#L18

[Rahul Rawat]

So I tried the implementation you said and changed it to api as well like

api("me.rahulrawat:AddressLibrary:1.0-SNAPSHOT") {
        transitive = true
    }

Now the library is linked but I still have to redeclare all the dependencies declared inside the library. That is still the pain for me 😅

[Big Chungus]

You're confusing your dependencies. You declare transitive dependencies in the library as api, but in your app as implementation

[Rahul Rawat]

So are you saying that for the following excerpt

val commonMain by getting {
            dependencies {
                implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:$coroutinesVersion"){
                    version {
                        strictly(coroutinesVersion)
                    }
                }
                implementation("org.jetbrains.kotlinx:kotlinx-serialization-core:$serializationVersion")

                implementation("io.ktor:ktor-client-core:$ktorVersion")
                implementation("io.ktor:ktor-client-serialization:$ktorVersion")
                implementation("io.ktor:ktor-client-logging:$ktorVersion")

                implementation("com.squareup.sqldelight:runtime:$sqlDelightVersion")
                implementation("com.squareup.sqldelight:coroutines-extensions:$sqlDelightVersion")

                implementation("org.kodein.di:kodein-di:$kodeinVersion")
            }
        }

I have to declare all the implementation to api with transitive true so I don’t have to reinclude them inside android app?

[Big Chungus]

Yes and no

[Big Chungus]

Transitive true is not required

[Big Chungus]

https://docs.gradle.org/current/userguide/core_dependency_management.html

[Rahul Rawat]

It works finally. I don’t know how to thank you now man. Can’t thank you enough 😄

[Big Chungus]

Sweet, glad to hear you got it sorted.