Release updates archive

 

Emulator 30.1.1 is now available in the Canary and Dev channels.

General fixes available in this release

• Removed icebox run command from console
• Removed the redundant foldable snapshot
• Upgraded compiler toolchain to clang 11.0.2
• Vulkan: enforce page alignment host pointers of ColorBuffer
• Unlock foldable structure when calling UI change.

Android Studio 4.2 Canary 8 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 macOS). Otherwise, you can download it here.
For information on new features and changes in all preview builds of Android Studio 4.2, 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.

Database Inspector: Offline mode

In Android Studio 4.2 Canary 8 and higher, we've added the ability to keep inspecting your app's databases after a process disconnects, making it easier to debug your app after a crash. While offline, you can open and query tables. However, you cannot edit values or run modification statements until you reconnect to an app process.

To learn more, see the release notes.

General Fixes

This update includes fixes for the following issues:

Android Gradle Plugin

• Issue #162358733: make sure artifact collision do not conflict when replaced.
• Issue #161826152: Gradle ran out of memory with 4GB max heap
• Issue #160473003: Set Custom application id per variant bug
• Issue #163039193: prepareLintJarForPublish destination file already exists

C++ Import/Sync

• Issue #160272302: NDK resolution outcome should not be printed

Code Analysis

• Issue #36991569: Lint warning for animation created but not .start()ed
• Issue #149416536: Request: Lint Warning for AnimatorInflator.loadAnimator on API 23 and below

Data Binding

• Issue #161814391: Kotlin process annotation is busted starting in 4.2 canary 5
• Issue #152153710: Referencing a generic LiveData works with AGP <= 3.5.0 but fails for later versions.

Deployment

• Issue #160192216: Bug: still can't build&run a new project on Android Studio

Dexer (D8)

• Issue #160905482: Desugaring broken for subclasses of ConcurrentHashMap
• Issue #160909126: coreLibraryDesugaringEnabled seems to break ConcurrentHashMap when using Gson and reflection

Editing

• Issue #153616200: Lint produces false warnings on ProGuard config files

Import/Sync

• Issue #161963743: IDE fails to stop Gradle daemon when using 6.6-rc-2

Layout Editor

• Issue #162588517: Some exceptions by custom views are not reported in the issue panel

Lint

• Issue #158128960: AGP 4.0 false positive Instantiatable Lint check if Application extends java class
• Issue #67602844: Add Lint rule for unmodifiable SharedPreferences.getStringSet.
• Issue #161362796: False positives in lint check NonConstantResourceIdDetector
• Issue #159532832: Android Studio 4.2's lint error UI is confusing
• Issue #159935420: [Lint feature request]: Errors for using newer patterns in SimpleDateFormat
• Issue #118332958: Make whole file not translatable for pseudoLocalesEnabled true
• Issue #139100146: Request: each time we use RemoteViews, don't let code be built till unless all views in the layout are supported

Navigation Editor

• Issue #160195388: Can't connect two destinations in navigation map

New Code/Templates

• Issue #162565516: New Module button not showing Dialog
• Issue #162566204: underscore appends when caps is on while naming a new activity for the layout name

Project Structure

• Issue #162351817: AS treat whenObjectAdded clousere from android.productFlavors as flavour in Project Structure

Resources

• Issue #160865813: Required attributes are not automatically inserted for FQN view tag

Run

• Issue #162259273: Wrong Activity is use for launch when there is an alias

Shrinker (R8)

• Issue #161403944: With AGP 4.1.0.beta01+, minifyEnabled = true leads to runtime crash due to java.lang.VerifyError
• Issue #160901582: CompilationError during R8 phase when optimizations enabled

Additionally the issues below were addressed in this release but may not be necessarily fixed:

Android Gradle Plugin

• Issue #162528480: AGP 4.2.0-alpha07 fails with java.lang.IllegalStateException: Failed to pseudo-localize string
• Issue #161115878: GradlePlugin: Kotlin access to extra properties in ProductFlavor (it should be ExtensionAware)

Android Studio

• Issue #160271731: Set up integration test to make sure studio can open a compose file without issues

API

• Issue #69953968: Allow "packagingOptions" to be defined per build type/variant

Code Editor

• Issue #162196087: Frequent UI freezes

Import/Sync

• Issue #160909456: androidx compose project gradle sync breaks when upgrading to AS 4.2 Canary 4

Layout Inspector

• Issue #162448507: Add functionality to snapshot view hierarchy
• Issue #162656657: Add refresh button

Lint

• Issue #163080422: lint.xml: synchronize with IDE, allow directory nesting, support configurations, etc
• Issue #134987035: Use of LintOptions severity overrides breaks OTHER check validations
• Issue #122769438: [ConstantLocale] Use of Locale.getDefault() within an enum value method is incorrectly flagged as being assigned to a static final constant
• Issue #161584622: [lint] DiffUtilEquals false positive when type is exactly known

Memory

• Issue #161925082: The Instance View window is too small and cannot be made wider

Run

• Issue #151532381: [4.1-Canary2] Adding JVM agent flags breaks Run/Debug.

ConstraintLayout 2.0.1 is now available on the google maven repository: Documentation & Examples

Documentation is available on https://developer.android.com/reference/androidx/constraintlayout/widget/ConstraintLayout and https://developer.android.com/reference/androidx/constraintlayout/motion/widget/MotionLayout

Examples are available on https://github.com/android/views-widgets-samples/tree/master/ConstraintLayoutExamples

Bugfixes

This release fixes a compatibility issue with MotionEditor for all version of Studio.

 Emulator 30.1.0 is now available in the Canary and Dev channels.

General fixes available in this release:

# Foldables support

• Allow using (percentage on screen, width) to replace (x, y, width, height) to config hw.sensor.hinge.area. The old style is still supported.

We are very happy to announce the stable release of ConstraintLayout 2.0 -- a long journey, but this version adds a very long list of capabilities to v1!

Emulator 30.0.26 is now available in the Canary and Dev channels.

General fixes available in this release:

• Fixed FD_SETSIZE error on Windows. We now use WSAEventSelect() instead of select() for establishing non-blocking connections to loopback servers.
• Added F16C CPUID feature support to Linux emulator; macOS/Windows in progress.
• If hw.audioInput=no and hw.audioOutput=no in config.ini, emulator audio is now properly disabled.
• Added support on the host side for virtio-gpu host coherent blob resources.
• Due to how emulator rendering works, we now process virtio-gpu virtqueue in the vcpu thread (because rendering is offloaded to other threads anyway). virtio-gpu rendering will be enabled in a future system image + emulator version.
• Fixed an issue where if the emulator window was minimized while the extended controls window was open but not active, the extended controls window would keep showing up when resizing the emulator window. We will completely remove the behavior (the case with active extended controls window) in a future update.

Emulator 30.0.25 is now available in the Canary and Dev channels. 

• Fixed a flaky bug with Wi-Fi not connected when the emulator starts.

• 3D foldable view and hinge parameters are now integrated with the existing foldable presets. The following can be a used with, for instance, the 7.3 foldable AVD's config.ini:

• hw.sensor.hinge = yes

• hw.sensor.hinge.count = 1

• hw.sensor.hinge.type = 1

• hw.sensor.hinge.ranges = 180-360

• hw.sensor.hinge.defaults = 180

• hw.sensor.hinge.areas = 54.7-0

• hw.sensor.posture_list=4, 3

• hw.sensor.hinge_angles_posture_definitions=210-360, 180-210 

• hw.sensor.hinge.fold_to_displayRegion.0.1_at_posture=4

Continuous Testing with Android Emulator Containers

Setting up and running the Android Emulator on continuous integration (CI) or deployment (CD) is now easier than ever before with our pre-built Android Emulator Containers. These containers allow you to find and run the right version of the Emulator without the headache of dependency management, which makes it easy to scale automated tests as part of a CI/CD system without the upkeep cost of a physical device farm.

Earlier this year, we released Android Emulator download and Docker image generator scripts to help developers who were struggling to deploy and debug remote emulators. These scripts made it easier to find the right system image, manage system dependencies, and run the Android Emulator.

We are now taking this one step further and experimentally providing pre-built Android Emulator Containers for each major Emulator release. These containers remove the need to manually run the generator yourself, saving time and complexity. Don’t worry, the pre-built containers still support all of the features offered by those built with the Docker scripts, like adb and web access.

Linux KVM is required to run these containers and can be enabled by running on bare metal or on a virtual machine with nested virtualization. The correct option depends on your cloud provider, so read our documentation for recommendations.

The script below is an illustration of how you can integrate an Android Emulator Container into your system and use it to run tests.

#!/bin/bash

# This is the remote image we are going to run.
# Docker will obtain it for us if needed.
DOCKER_IMAGE=us-docker.pkg.dev/android-emulator-268719/images/r-google-x64:30.0.23

# This is the forwarding port. Higher ports are preferred as to not interfere
# with adb's ability to scan for emulators.
PORT=15555

# This will launch the container in the background.
container_id=$(docker run -d \
  -e "ADBKEY=$(cat ~/.android/adbkey)" --device /dev/kvm --publish \
  8554:8554/tcp --publish $PORT:5555/tcp  \
  $DOCKER_IMAGE)

echo "The container is running with id: $container_id"

# Note you might see something like:
# failed to connect to localhost:15555
# this merely indicates that the container is not yet ready.

echo "Connecting to forwarded adb port."
adb connect localhost:$PORT

# we basically have to wait until `docker ps` shows us as healthy.
# this can take a bit as the emulator needs to boot up!
echo "Waiting until the device is ready"
adb wait-for-device

# The device is now booting, or close to be booted
# We just wait until the sys.boot_completed property is set to 1.
while [ "`adb shell getprop sys.boot_completed | tr -d '\r' `" != "1" ] ;
do
  echo "Still waiting for boot.."
  sleep 1;
done

# Now you can use the emulator as usual for example:
# ./gradlew installDebug
# ./gradlew connectedAndroidTest
# etc..

echo "The device is ready"
echo "Run the following command to stop the container:"
echo "docker stop ${container_id}"

Check out our README for further information on getting started and taking advantage of the Android Emulator Containers. This is our first time offering pre-built Emulator Containers, so please report any problems or feature requests on our issue tracker.

Emulator 30.0.24 is now available in the Canary and Dev channels.