Android Studio 3.3 Canary 1 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 ...

Read more

Android Studio 3.3 Canary 1 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:

• The flag for disabling incremental dexing (useDexArchive) has been removed.
• Android Studio 3.2 gave warnings when it found differences in versions between runtime and compile classpaths. Android Studio 3.3 reports these differences as errors.
• Android Studio 3.3 Canary 1 includes Kotlin 1.2.50. The ability to update the Kotlin plugin in Android Studio is temporarily disabled; this is to prevent the installation of incompatible plugins while we resolve some issues.
• The new getRawAndroidResources() method in the Gradle build API returns a file collection containing all resources for the variant. This method has been added primarily as a step toward migrating the Kotlin Android Extensions plugin to this API so that it will no longer need to use the MergeResources task. This new method is in incubation, meaning that it may be changed or removed without notice.
• The new applicationIdTextResource method in the Gradle build API returns the application ID of a variant. For feature variants, this returns the resolved application ID from the application; for application variants, this method behaves the same as getApplicationId().
• The Gradle signingReport task now also returns an SHA-256 hash.
• The SDK Manager now reports the size of files downloaded during the update process.

This update includes fixes for several bugs, including the following:

• Gradle was consuming large amounts of memory, leading to Java heap space errors, when packaging APKs.
• Some JAR files could not be opened for the reading of their class files for dexing. This has been fixed by switching to a new ZIP file decoder.
• Processing module-info.class during desugaring analysis caused failures with the message java.lang.IllegalArgumentException: Type without superclass: module-info. This file is now filtered out during desugaring analysis.
• The Force HTTP setting in the Android Studio SDK updater was not working.
• The SDK Manager command-line argument --package_file was not working.
• Android Studio did not use the ANDROID_SDK_ROOT environment variable when installing the Android SDK.
• The Android test plugin ignored the Gradle command-line parameters to select which tests to run.

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.

Android Studio 3.2 Beta 2 is now available in the Beta channel.

If you have Android Studio set up to receive updates on the Beta channel, you can get the update by choosing ...

Read more

Android Studio 3.2 Beta 2 is now available in the Beta channel.

If you have Android Studio set up to receive updates on the Beta 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:

• Resource configurations set with resConfigs were ignored when building an Android App Bundle.
• Resource processing was incorrect in some cases when the minimum SDK target was specified to be the preview version.
• Overrides set using the variant API were ignored when the version name and version code were published for dynamic feature modules for Android App Bundles.
• D8 failed to read some ZIP files with special characters.
• kotlin-stdlib-jre* artifacts are now deprecated, so kotlin-stdlib-jdk* are used instead.
• Lint checks failed when an invalid issue ID was used in the XML lint configuration file.
• Lint checks incorrectly reported some resources as unused if they were referenced through enum constructors.
• It was impossible to disbale the Auto verify option for a deep link in the Navigation Editor.
• Using the Rerun failed tests command in the Run window sometimes incorrectly returned the message "No tests were found".
• A conflict between the Android Gradle Plugin and kapt caused errors with data binding. See Issue #110198434 for information about how other annotation processors may need to account for this issue.

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

Jamal Eason, a product manager on the Android Developer Tools team, announced Android Studio 3.2 Beta 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.

We are very happy to announce the first alpha release of ConstraintLayout 2.0. It’s available from the google maven repository:

dependencies {
  implementation 'com.android.support.constraint:constraint-layout:2.0.0-alpha1'
}

This is the first release containing the new MotionLayout class. MotionLayout is a layout designed to provide a rich framework for declarative animation and input-driven motion.

Read more

We are very happy to announce the first alpha release of ConstraintLayout 2.0. It’s available from the google maven repository:

dependencies {
  implementation 'com.android.support.constraint:constraint-layout:2.0.0-alpha1'
}

This is the first release containing the new MotionLayout class. MotionLayout is a layout designed to provide a rich framework for declarative animation and input-driven motion.

Also included in this release:

• ConstraintProperties - an API for manipulating ConstraintLayout properties
• A new state management API for ConstraintLayout (see setState())

Documentation is available on
https://developer.android.com/reference/android/support/constraint/classes

A sample application for MotionLayout is also available on
https://github.com/googlesamples/android-ConstraintLayoutExamples

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 ...

Read more

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.

Android Emulator 27.3.8 is now available in the Canary and Dev channels.

This update includes a single change to fix an issue that caused videos to be rendered as all-white frames in some situations on older API levels.

Read more

Android Emulator 27.3.8 is now available in the Canary and Dev channels.

This update includes a single change to fix an issue that caused videos to be rendered as all-white frames in some situations on older API levels.

We are considering this build as a candidate for release to the stable channel, so we would especially appreciate your testing of this build and your reporting of any issues that you find.

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.

Android Emulator 27.3.7 is now available in the Canary and Dev channels. This update includes a single change:

• Fixed issue for emulators running on Windows Hypervisor Platform where system images with API level <= 25 were not able to boot.

Read more

Android Emulator 27.3.7 is now available in the Canary and Dev channels. This update includes a single change:

• Fixed issue for emulators running on Windows Hypervisor Platform where system images with API level <= 25 were not able to boot.

We just released ConstraintLayout 1.1.2. We recommend to update to this version. It’s available from the google maven repository:

dependencies {
  implementation 'com.android.support.constraint:constraint-layout:1.1.2'
}

This release fixes a few issues present with complex chains mixing ratio and weights.

Read more

We just released ConstraintLayout 1.1.2. We recommend to update to this version. It’s available from the google maven repository:

dependencies {
  implementation 'com.android.support.constraint:constraint-layout:1.1.2'
}

This release fixes a few issues present with complex chains mixing ratio and weights.
Note: There was a packaging problem with the AndroidX release of 1.1.1 which is now fixed in 1.1.2.

Documentation is available on https://developer.android.com/reference/android/support/constraint/ConstraintLayout.html

Android Studio 3.2 Canary 18 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 ...

Read more

Android Studio 3.2 Canary 18 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 includes fixes for the following bugs:

• Inclusion of a test library dependency caused the Navigation Editor to block waiting for build completion.
• The debugger crashed when debugging a layout with a text box.
• OnePixelDivider had a myDisposable instance that was not cleared when the instance was disposed.
• The default .gitignore didn't ignore .idea/caches/build_file_checksums.ser.
• Some lint warnings were not suppressed when tools:ignore was used.
• Android Studio crashed during fragment transitions when using profilers.
• Android Studio failed to download SDK packages on macOS after the default language was changed from English to Hindi.

In addition to the bug fixes mentioned above, the lint checker has been improved to no longer report several categories of false positives.
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.

Android Emulator 27.3.6 is now available in the Canary and Dev channels.

This update contains the following changes:

• Fixed crashes after initial snapshot load when loading color buffers from the snapshot.
• Fixed potential memory corruption when saving snapshots of OpenGL shader program info logs.
• Fixed potential memory corruption when checking CPUID of the host system.
• On AMD machines running the latest Windows 10 and where Windows Hypervisor Platform can be successfully enabled, the emulator can now boot API level 26+ x86 / x86_64 AVDs in accelerated mode.
• Warning: We have found that enabling Hyper-V or Windows Hypervisor Platform on many AMD Ryzen machines, especially laptops with Vega GPUs, can cause Windows to become unbootable. We only recommend trying this if your AMD system is already successfully running with Windows Hypervisor Platform enabled. 
• Fix: If Windows has become unbootable because of enabling Windows Hypervisor Platform, disable virtualization in your system BIOS and reboot, which should allow you to disable the feature.

Read more

Android Emulator 27.3.6 is now available in the Canary and Dev channels.

This update contains the following changes:

• Fixed crashes after initial snapshot load when loading color buffers from the snapshot.
• Fixed potential memory corruption when saving snapshots of OpenGL shader program info logs.
• Fixed potential memory corruption when checking CPUID of the host system.
• On AMD machines running the latest Windows 10 and where Windows Hypervisor Platform can be successfully enabled, the emulator can now boot API level 26+ x86 / x86_64 AVDs in accelerated mode.
• Warning: We have found that enabling Hyper-V or Windows Hypervisor Platform on many AMD Ryzen machines, especially laptops with Vega GPUs, can cause Windows to become unbootable. We only recommend trying this if your AMD system is already successfully running with Windows Hypervisor Platform enabled. 
• Fix: If Windows has become unbootable because of enabling Windows Hypervisor Platform, disable virtualization in your system BIOS and reboot, which should allow you to disable the feature.

We greatly appreciate your bug reports, which help us to make Android Emulator 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.

Android Studio 3.2 Canary 17 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 ...

Read more

Android Studio 3.2 Canary 17 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.

Changes in this update include the following:

• Among the bugs fixed in this update is a source of memory leaks that occur when you use the Layout Editor. For details of this fix and how it relates to other updates for Android Studio, see this post by Android Studio product manager James Lau.
• Applications built with Navigation Architecture Component (android.arch.navigation) libraries crashed because the libraries were not being processed during AndroidX refactoring. This has been fixed.
• Kotlin methods that return Unit in databinding layouts are now handled correctly.
• Data Binding v2 compilation failed in cases of one module having a very large number of layouts. This has been fixed.
• Test coverage data was incomplete when using Android Test Orchestrator. This is fixed.

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.

The Android Studio 3.1.3 bug-fix update is available in the stable release channel.

This update fixes several bugs. For a list of fixes in this update, see the Android Studio 3.1.3 release notes ...

Read more

The Android Studio 3.1.3 bug-fix update is available in the stable release channel.

This update fixes several bugs. For a list of fixes in this update, see the Android Studio 3.1.3 release notes.

Among the bugs fixed in this update are some sources of memory leaks that occur when you use the Layout Editor. For details of these fixes and how they relate to other updates for Android Studio, see this post by Android Studio product manager James Lau.

If you already have Android Studio installed, you can get the update by clicking Help > Check for updates (Android Studio > Check for updates on Mac). Otherwise, you can download it here.

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.

We just released ConstraintLayout 1.1.1. We recommend updating to this version. It’s available from the google maven repository:

dependencies {
implementation 'com.android.support.constraint:constraint-layout:1.1.1'
}

This release fixes a few issues present in 1.1.0 ...

Read more

We just released ConstraintLayout 1.1.1. We recommend updating to this version. It’s available from the google maven repository:

dependencies {
implementation 'com.android.support.constraint:constraint-layout:1.1.1'
}

This release fixes a few issues present in 1.1.0:

• When animating layout by marking Views as GONE an extra measure was made, causing some visual artifact with TextViews
• Some regressions related to ratio support
• A few minor issues in chains (gone elements / margins) 

Documentation is available on https://developer.android.com/reference/android/support/constraint/ConstraintLayout.html

Android Emulator 27.3.5 is now available in the Canary and Dev channels.

Read more

Android Emulator 27.3.5 is now available in the Canary and Dev channels.

This update contains the following changes:

• The emulator would sometimes experience memory corruption and crash when creating color buffers. This is fixed.
• We fixed issues in color buffer reference counting, which should increase the reliability of snapshot saves and loads while the emulator is running.
• In some cases, the emulator failed to initialize because it couldn’t find a wgl...ARB function, such as wglGetExtensionsStringARB. This issue has been fixed by having the emulator also search for equivalent wgl...EXT versions of WGL functions in addition to the wgl...ARB versions. (Issue link)
• On Linux, the Extended controls panel now has a more prominent close button.
• The emulator now generates userdata.img based on the data/ folder of the system image, if available. In future system image revisions for API level P and higher, we will not include userdata.img in the system image zip file, which will make for smaller downloads and faster patching of system image updates.

We greatly appreciate your bug reports, which help us to make Android Emulator 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.