Status Update
Comments
yo...@gmail.com <yo...@gmail.com> #2
to add some more detail:
with Kotlin 2.0.0, I would expect that this would be enough to activate all the IDE Compose support in studio:
plugins {
id("com.android.library")
kotlin("android")
id("org.jetbrains.kotlin.plugin.compose")
}
But unless I also add android.buildFeatures.compose = true
, the IDE compose support (Previews, Layout Inspector navigate to composable source, compose syntax highlighting, etc) does NOT work.
xa...@google.com <xa...@google.com> #3
Yes, it would be my expectation too that just applying the plugin is enough.
je...@google.com <je...@google.com> #4
fip : Change-Id: I720744177b71e3d40c02c79df664eee15255b913
xa...@google.com <xa...@google.com> #5
This looks like the wrong changeId?
je...@google.com <je...@google.com> #6
yes, sorry it's Change-Id: If74d806e666847cfd5a2a0c6892a8efd14854bec
je...@google.com <je...@google.com> #7
8.5.1 cherry pick in review.
je...@google.com <je...@google.com>
an...@google.com <an...@google.com> #8
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Koala | 2024.1.1 Patch 1
- Android Gradle Plugin 8.5.1
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
aq...@gmail.com <aq...@gmail.com> #9
Update
lo...@gmail.com <lo...@gmail.com> #10
Does it mean that android.buildFeatures.compose = true
is no longer necessary with Kotlin 2.0 as of AGP 8.5.1?
Description
From external report, it looks like if one is to use the compose plugin without setting
android.buildFeatures.compose = true
then it looks like Studio is not aware that the project is using compose and some compose specific features are not used.We should verify that the sync information contains the same whether the compose DSL or the compose Plugin is used.