Status Update
Comments
fe...@aspire.se <fe...@aspire.se> #2
And create a non-compose app will just works fine.
fe...@aspire.se <fe...@aspire.se> #3
an...@google.com <an...@google.com> #4
Same issue here, app crashes on start when using android-gradle 7.1.0-alpha04 and AS Canary 4
al...@google.com <al...@google.com> #5
aurimas@, are you the right person for triaging Android Studio version-specific issues? I saw you upgraded AndroidX to Bumblebee Canary 3 last week. This bug report might be specific to Bumblebee Canary 4, I'm not certain.
bu...@google.com <bu...@google.com> #6
Tested this quickly locally, it seems that the studio template creates a project that crashes out of the box. Updating compose_version to 1.0.0-rc02
and kotlin-gradle-plugin to 1.5.10
fixed the crash for me locally. We likely want to update studio template to use the latest of compose and kotlin.
fe...@aspire.se <fe...@aspire.se> #7
Moving to studio component for triage.
This is a pretty bad user experience so ccing annachiarab@ to make sure this gets attention
al...@google.com <al...@google.com>
an...@google.com <an...@google.com> #8
It is likely to be addressed ag/Iafc18b104ff77fcd513d35db224d48f3b915a4e3
an...@google.com <an...@google.com> #9
I am running into this same issue on a project using compose 1.0.0-rc02, kotlin-gradle-plugin 1.5.10, AGP 7.1.0-alpha04, and AS 2021.1.1 Canary 4. It is only when I install app from AS. When I build from gradle via command line, I can run the app just fine.
Description
Jetpack Compose version:
BOM
2023.10.01
,2024.11.00
Jetpack Compose component(s) used:
androidx.activity:activity-compose
androidx.compose.material:material
androidx.compose.material:material-icons-extended
androidx.compose.ui:ui
androidx.compose.ui:ui-graphics
androidx.navigation:navigation-compose
androidx.constraintlayout:constraintlayout-compose
Android Studio Build:
Kotlin version:
1.9.22
Steps to Reproduce or Code Sample to Reproduce:
I don't really have a reproduction available at this time. The following is an untested simplification where I'd start writing a new repro from. Also, be aware that this code is executing from a dynamic feature module.
Stack trace (if applicable):