Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: for multiplatform deps, only include target platform

See original GitHub issue

If a kotlin multiplatform lib is depended on and has, say, org.jetbrains.compose:runtime as a common dependency, it gets included in an android dependency guard classpath even though there is no android platform exposed for that dep.

Issue Analytics

State:
Created a year ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

ZacSweerscommented, Oct 13, 2022

I looked a little more closely at it and I think this is actually “correct” by the letter of the gradle law. There is an android compose-jb artifact, but it’s just a shim pointing at the real androidx compose dep

+--- org.jetbrains.compose.runtime:runtime:1.2.0
|    \--- androidx.compose.runtime:runtime:1.2.1 -> 1.3.0-rc01 (*)

0reactions

handstandsamcommented, Oct 11, 2022

☝️ I included a list of configurations that could be depended on. In the example above, you would probably only need the jvm configuration to exclude, but with HMPP (https://kotlinlang.org/docs/multiplatform-hierarchy.html) you might be depending on multiple parent configs.

The intersection result is I think what you’d be looking for here?