PSA for intrepid users of the Compose Multiplatfor...

# compose

[darkmoon_uk]

PSA for intrepid users of the Compose Multiplatform 1.2.0 Dev Alpha builds (e.g. 1.2.0-alpha01-dev745).
Some observations that may help:
• Resolution of Android Compose dependencies (not other platforms) is broken when using AGP `7.2.x`in Chipmunk, Dolphin and Electric Eel.
• Correct Android dependency highlighting was last seen working with AGP 7.1.2 in these IDE's.
• It appears fixed again when using Electric Eel with AGP 7.4.0-alpha08, which requires Gradle 7.5-rc-2
Summary: to use Compose Multiplatform 1.2.0 Alpha requires a fully 'bleeding edge' setup again 😅

[Greg Steckman]

I'm using AGP 7.2.1 with Chipmunk without a dependency resolution problem, but I'm using rc03 for my androidMain dependencies and alpha01-dev745 for jvm/js/common. What is "dependency highlighting"?

[eygraber]

Does this help fix your issue?

https://kotlinlang.slack.com/archives/C3PQML5NU/p1652779672225139?thread_ts=1652224566.469179&cid=C3PQML5NU

[eygraber]

Also check out https://issuetracker.google.com/issues/231701341

[Greg Steckman]

I'm not having any issues, but I am using

sourceSets {
  named("commonMain"){...}
}

[Greg Steckman]

And similar for other source folders.

[darkmoon_uk]

@Greg Steckman Is that maybe an unintentional hack/workaround for this very issue though? If you're depending on Compose Multiplatform in commonMain, then shouldn't the Android 'set' of C/MP dependencies be made available in androidMain too? It sounds like by also depending on rc03 in androidMain you're 'patching in' what Compost Multiplatform is possibly failing to provide, otherwise there'd be ambiguity (duplicated class issues)? Or you have a finer-grained Gradle setup that is making all this explicit per target. If you take rc03 out does it still work?

[Greg Steckman]

@darkmoon_uk I took out rc03, and everything seems to still be working. I was able to do a clean build and run Android, Desktop, and Web targets.