Related to @Val Salamakha’s observation above, I had AS Canary update to Beta 1, and was surprised to find Compose functionality stripped. I first checked the Compose docs thinking that maybe there was something I needed to do to re-enable it. The Android Studio + Compose page (https://developer.android.com/jetpack/compose/setup) currently leads you to the preview page, which has you download Beta 1. Might be good to update that link + docs to point to the preview archive page (https://developer.android.com/studio/archive), with directions to look for the most recent canary build?

thanks for pointing this out. i believe someone is trying to get this fixed.

Does "get this fixed" refer to getting 4.0 beta releases to support Compose? Or does it refer to fixing the docs to steer developers towards 4.0 Canary 9? (or perhaps to 4.1 Canary 1?) I'm just trying to wrap my head around what IDE versions are and are not Compose-friendly. UPDATE: I just noticed the 4.1 Canary release notes saying that Jetpack Compose was moved out of 4.0 and into 4.1. Does this mean that 4.0, when it hits a stable release, will not be Compose-friendly?

@Mark Murphy To your first question, Leland was referring to the docs/AS Preview page, which has since then been updated to have a link to both the beta and canary versions of AS. To your later question about AS 4.0 and compose, 4.0 will not support Jetpack Compose. What will likely happen is that Compose functionality will remain in canary builds for the foreseeable future and when a beta is cut, it will be moved to the next canary version. So when 4.1 is ready for a beta release, it's likely that Compose functionality will be stripped for the beta, and there will be a AS 4.2 Canary build that supports Compose. If you want to do Compose testing, you'll want to ensure you stay on Canary builds, and don't upgrade to a beta build.