Hi folks! Is there a way to trace where some klib ...

# multiplatform

[Bernd Prünster]

Hi folks! Is there a way to trace where some klib "comes from"? Kontext: in our KMP build, a dependency shows up out of nowhere and is causing trouble, but not even gradle dependencies lists it (yes, I tried a dozen configuration, still not showing up). yet, the klib is present in the .kotlin directory and the build for iOS fails. how do I debug this?

[mbonnin]

dependencies should list all dependencies. There might be more than 12. Are you sure it's not there?

[Bernd Prünster]

there are more than 12 configurations. is there a way to print all the configurations relevant to a a task?

[mbonnin]

Don't think so

[mbonnin]

If it's not there, maybe it's in a detached configuration

[mbonnin]

The error message should the task if the configuration is one of its input

[Bernd Prünster]

let's be very concrete: https://github.com/a-sit-plus/kmm-vc-library/actions/runs/10045582156/job/27763139417#step:5:486

[mbonnin]

I’ve seen that sometimes with incompatible dependencies (using a too old or too new version of Kotlin)

[mbonnin]

But that wouldn’t explain why it doesn’t show up in the dependencies...

[Oleg Yukhnevich]

The error is coming from KLib compiler which also resolves dependencies from manifest file inside klib
I saw such issues with dependencies with cinterop, but never with ordinary dependencies
May you can check youtrack by searching “KLIB resolver: Could not find” there

[Bernd Prünster]

thanks! this may be a bit particular, because the library got renamed last year, so it has to be some kind of remnant from somewhere that is just now showing up. I'm pretty sure it is pulled in as a transitive dependency, but without any way to list the configurations relevant for the task that tirggers the issue, I am just lost, because I can't even print the dependency tree to help me move forward

[Bernd Prünster]

i'm fairly confident i found the offenders: two test dependencies, which pull the library in (even though gradle says, there is no such dependency, I know for a fact there is, because I put it there myself. now my question is: why are exclusions simply ignored by gradle?

[CLOVIS]

Can you share a build scan for the task in question? And the maven coordinates of the offending dependency

[Bernd Prünster]

where's the buildscan located (i did ./gradlew build --scan)?

[Bernd Prünster]

io.matthewnelson.kotlin-components:encoding-core is the ghost dependency that is causing trouble

[CLOVIS]

In the very last line in the output, Gradle should print a URL, that's what I'm interested in

[Bernd Prünster]

well that log is gone for good. I'll rebuild

[Bernd Prünster]

if the activation mail ever gets through our greylisting filter I'll share the scan

[CLOVIS]

You don't need to activate it, if you send me the link I can activate it myself

[Bernd Prünster]

just got it. i can tell you the dependency is not in the build scan

[Bernd Prünster]

gradle is convinced the dependency is nonexistent but klib

[CLOVIS]

can you send it to me?

[CLOVIS]

[continuing in DM]

[Bernd Prünster]

it's a bug: https://youtrack.jetbrains.com/issue/KT-70146/KLIB-resolver-fails-for-nonexistent-transitive-dependency