Android Studio 3.3 Canary 6 is now available in the Canary and Dev channels.

If you have Android Studio set to receive updates on the Canary or Dev channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

This update includes the following new features and changes in behavior:
  • You can now view a list of active Gradle Daemons in Android Studio. To do this, double-press the Shift key to bring up the Search Everywhere dialog, type "Show Gradle Daemons", and click on the Show Gradle Daemons result that appears.
  • Linter now produces a warning if using a vector image larger than 200 x 200 dp.
  • The Navigation Editor supports new argument types from library versions 1.0.0-alpha03 and 1.0.0-alpha04.
  • Single-variant project sync: Syncing your project with your build configuration is an important step in letting Android Studio understand how your project is structured. However, this process can be time-consuming for large projects. If your project uses multiple build variants, you can now optimize project syncs by limiting them to only the variant you have currently selected.

    When syncing your project using Android Studio 3.3 Canary 6 or higher, the IDE prompts you to enable this optimization.

    To enable this optimization manually, click File > Settings > Experimental > Gradle (Android Studio > Preferences > Experimental > Gradle on a Mac) and check Only resolve selected variants. Note: This optimization currently supports projects that include only the Java programming language. If, for example, the IDE detects Kotlin or C++ code in your project, it does not automatically enable this optimization, and you should not enable it manually.



This update includes fixes for several bugs, including the following:
  • Users were unable to install JetBrains plugins.
  • Android Studio wasn't properly resolving kotlinx.android.synthetic.* imports.
  • Linter was producing false positive MissingTranslation errors for Japanese strings.
  • When using synthetic properties from the Kotlin Android Extensions plugin, the linter was improperly marking some ID values as unused.
  • Quick fix for findViewById resulted in a compilation error.
  • Using @BindingAdapter with duplicate values now results in a warning along with a log entry.


For information on new features and changes in previous releases of Android Studio, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.