Thursday, June 21, 2018

Android Studio 3.2 Beta 1 available


Android Studio 3.2 Beta 1 is now available in the Beta, Canary, and Dev channels.

If you already have an Android Studio build on the Beta, 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 fixes for several bugs, including the following:
  • The Kotlin plugin didn't recognize the com.android.feature module, so you would mistakenly receive the following message when performing a Gradle sync: 'kotlin-android' expects one of the Android Gradle plugins to be applied to the project:...
  • The resource shrinker was mistakenly enabled for test variants, causing failures with the following error message: Execution failed for task ':app:transformClassesAndDexWithShrinkResForStagingAndroidTest'.
  • Android Studio gave superfluous warnings about folders generated by kapt.
  • Android Studio crashed because of an uncaught exception in the parsing of a malformed date and time.
  • The dynamic feature template incorrectly used just include where it should have used dist:include.
  • Tests for Kotlin code reported 0% coverage.


For information on new features and changes in all preview builds of Android Studio 3.2, see the Android Studio Preview release notes.

Jamal Eason, a product manager on the Android Developer Tools team, announces the Android Studio 3.2 Beta 1 release in a post on the Android Developers 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.

Known issue: Missing javaCompilerTask error

When using Android Studio 3.2 Beta 1 and higher, you may get the following build error if your project uses the Protobuf Plugin for Gradle:

No such property: javaCompilerTask for class: com.android.build.gradle.internal.variant.TestVariantData

To resolve this issue, update the protobuf plugin to version 0.8.6 or higher. For more information, see Issue #110564407.