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:

Click the "Run" icon in the gutter next to a Compose Preview that builds and deploys the preview to device.
In the build output window notice that two sequential gradle builds are run before the preview is deployed.

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