Android Studio 3.2 Canary 16 now available
Tuesday, May 29, 2018
Android Studio 3.2 Canary 16 is now available in the Canary and Dev channels.
If you already have an Android Studio build 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 fixes several bugs, including the following:
- Use of the Layout Editor caused Android Studio memory usage to continually increase. We have addressed a memory leak underlying this issue. If you have experienced this memory leak, please try Android Studio 3.2 Canary 16 and let us know if the issue is resolved for you.
- Setting the
android.useAndroidX
andandroid.enableJetifier
flags totrue
in yourgradle.properties
file forced dependencies on missingandroidx.multidex
artifacts. For information on AndroidX, see the Android Studio Preview release notes. - You couldn't scroll within the Select a system image list in the Virtual device configuration dialog box to select older system images.
- Some Android virtual devices (AVDs) created from the command line could not be used by Android Emulator.
- The Android Virtual Device Manager would fail to operate if it encountered a corrupt or badly formed
.ini
file. - By default, ProGuard was using the
-dump
option, which tells ProGuard to write out a text version of the processed bytecode to the build directory. This data can be hundreds of megabytes, and its unnecessary inclusion can make many processes slower. - Android Studio crashed when attempting to add or remove a module by importing a Gradle project.
- The keyboard shortcut (Control + C or Command + C) to copy a screenshot from the Screen capture window did not copy the screenshot unless you had first clicked within the window.
For information on new features and changes in previous Canary builds, see the Android Studio Preview release notes.
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.