Bumped into a strange behaviour in the IDE. There ...

# compose

[Arkadii Ivanov]

Bumped into a strange behaviour in the IDE. There is a KMP project created using the Multiplatform Wizard, it uses Kotlin 1.9.20. It has the composeApp module that uses Multiplatform Compose 1.5.10. As soon as we add com.arkivanov.decompose:extensions-compose:3.0.0-alpha01 dependency to composeApp module, some imports (like for example Column) are shown as unresolved in commonMain. The added dependency uses Compose 1.6.0-alpha01 . If I update Compose to 1.6.0-alpha01 in the project, then imports are good again. The module compiles just fine in all cases. Updaing Kotlin to 1.9.21 and Compose to 1.5.11 is also affected.

Were there any breaking changes in Compose 1.6.0-alpha01? More details here.

[Robert Jaros]

See: https://youtrack.jetbrains.com/issue/KT-62398/KMP-Compose-breaks-resolution-of-stdlib-declarations-in-common-source-set

[Robert Jaros]

In my project upgrading compose to 1.6.0-alpha01 fixed the issue 🙂

[Arkadii Ivanov]

Thanks! Yeah, updating Compose fixes the issue.

[Arkadii Ivanov]

Though, the linked issue is about stdlib, whereas my issue is about Compose imports being unresolved. Still the same root cause?

[Robert Jaros]

In my case the problem was both stdlib and other dependencies as well (compose, coroutines).

[Robert Jaros]

Upgrading compose fixed all problems.

[Robert Jaros]

Strangely the issue is still open (targets 2.0.0-beta3).

[Robert Jaros]

So I assume something was fixed on the compose side.

[Arkadii Ivanov]

Awesome, thanks!