Fixed
Status Update
No update yet.
Comments
xa...@google.com
Thank you for reporting the issue. This should be fixed in: Android Studio JellyFish Canary 2
ga...@google.com
ls...@google.com
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 Jellyfish | 2023.3.1 Canary 1
- Android Gradle Plugin 8.4.0-alpha01
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!
ko...@gmail.com
Thank you!
Description
Jetpack Compose version: 1.2.0-beta02
Jetpack Compose component(s) used:
Android Studio Build: Dolphin Beta 4
Kotlin version: 1.6.21
Steps to Reproduce or Code Sample to Reproduce:
For a module "lib", I see these tasks being run in the two builds: first build - :lib:generateDebugSources :lib:createMockableJar :lib:generateDebugAndroidTestSources :lib:compileDebugUnitTestSources :lib:compileDebugAndroidTestSources :lib:compileDebugSources
second build - :lib:assembleDebug :lib:assembleDebugAndroidTest
Since each build has built in overhead (config, build scan uploading, etc) I’ve noticed that this slows down otherwise fast incremental builds. On a more selfish note, it confuses our build metrics in terms of number of builds and average build time since this produces two build scans with the work split across them.
Stack trace (if applicable): N/A