[go: up one dir, main page]

Release updates archive

Emulator 29.1.7 is now available in the Canary and Dev channels. Changes:
  • Fixed a Unicode path handling issue on Windows where the -kernel command line option did not work with paths that contained non-ASCII characters.
  • Added a command line option to name a particular run of the emulator with an ID. In the CI use case, this can make it easier to distinguish emulators and find out which one has been running on which ADB port, even when running multiple instances of the same AVD (via -read-only). Usage:
    • emulator -avd <avd-name> -id <id> [other-args]
    • Retrieve the ID via adb -s <device-serial> emu avd id
HAXM 7.5.2 for Windows is now available in all channels and HAXM 7.5.1 for macOS is now available in all channels. HAXM 7.5.2 should address the Windows BSOD on QT Beta 5 issue that users have pointed out recently (https://www.reddit.com/r/androiddev/comments/cbspgk/bluescreen_when_starting_android_q_emulator/).

Emulator 29.1.6 is now available in the Canary and Dev channels. Change:
  • Fixed issue where virtual scene camera would show a black screen.
Update on BSOD on Windows with Q Beta 5 system images


Android Studio 3.5 Release Candidate 1 (RC1) 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 macOS). Otherwise, you can download it here.

General fixes

This update includes fixes for the following public issues:

Gradle
  • Issue #130740393: Error running unit tests in Android Studio 3.4
  • Issue #133092984: DataBinding modules cause MergeDebugResources to run
  • Issue #126775254: aapt2FromMaven task input prevents build cache from being shared across different OSes
  • Issue #136150634: transformClassesWithMergeClassesForRelease fails with duplicate entry: META-INF/versions/9/module-info.class
  • Issue #130102823: StackOverflowError with DefaultPropertyState.getOrNull
Kotlin
  • Issue #128835109: resources.srcDirs = ['src'] option in gradle leakes .kt source code in artifact (APK)
Lint
  • Issue #131844902: DefaultJavaEvaluator.getProject sometimes returning /media for /media2/player/...MediaPlayer.java
Navigation
  • Issue #133280833: <nav-graph> element can only be included in application manifest
Shrinker (R8)
  • Issue #132549918: Using -keepparameternames has no effect
  • Issue #134304597: VerifyError: kotlinx/coroutines/AbstractCoroutine at API 17, 18
  • Issue #135210786: NoClassDefFoundError in runtime on API 19 and below when using AGP 3.5.0-beta04
  • Issue #134858535: Execution failed for task ':app:transformClassesAndResourcesWithR8ForDebug'.
For information on new features and changes in all preview builds of Android Studio 3.5, 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.6 Canary 5 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.

General fixes

This update includes fixes for the following public issues:

Core IDE
  • Issue #135132378: "Generate Signed Bundle or APK" => "Module" list order problem
Data Binding
  • Issue #135147332: Make sure "safeUnbox" doesn't show an "unresolved reference" error
Gradle
Kotlin
  • Issue #128835109: resources.srcDirs = ['src'] option in gradle leakes .kt source code in artifact (APK)
Layout Editor
Lint
New Project Wizard
Project System
  • Issue #129994596: IllegalStateException: buildOutput.apkData must not be null when building with obfuscation [3.4.0-rc03]
  • Issue #129612500: Opening 2nd Project causes Indefinite display of "Indexing paused due to batch update"

For information on new features and changes in all preview builds of Android Studio 3.6, 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.

Emulator 29.1.5 is now available in the Canary and Dev channels. Changes:
  • Added entry points for configuring multiple displays from a hardware INI file. This will require further changes to the AVD manager along with a future Q system image update.
  • Increased accuracy of YUV conversion.
  • Added NV21 to the set of potential YUV formats converted via OpenGL.
  • Unified the set of YUV formats used for camera versus media buffers. This requires a future Q system image update.
  • Improved performance of OpenGL and Vulkan graphics.
  • For better debuggability of OpenGL issues, we now make it easier to log GL calls from the guest. The following environment variables control whether or not each GL call is logged:
    • ANDROID_EMUGL_FINE_LOG=1 whether to log individual GL calls
    • ANDROID_EMUGL_LOG_PRINT=1 whether to instead print out the current GL debug log versus saving it to disk (the default)
Update on BSOD on Windows with QT Beta 5 system images
  • We noticed that some users on Windows are getting BSODs when running QT Beta 5 system images. There is a post on reddit that goes into more detail: (https://www.reddit.com/r/androiddev/comments/cbspgk/bluescreen_when_starting_android_q_emulator/). We're sorry about this and are proceeding with fix steps.
  • We found that one cause may be not having HAXM 7.5.1 installed, though some users are still having the issue with HAXM 7.5.1 installed. We haven't yet been able to reproduce the second case.
  • There is an upstream fix in the pipeline for a future HAXM release (https://github.com/intel/haxm/pull/216)
  • We have rolled back the QT Beta 5 system images for now while we re-land QT Beta 5 to non-Windows platforms only.
  • After HAXM with the fix is released, we will re-land QT Beta 5 to Windows.
  • If you would like to use the QT Beta 5 system image before it is re-landed, a manual download is available at http://dl.google.com/android/repository/sys-img/google_apis/x86-29_r06.zip . To use it, make sure you have the QT Beta 4 system image installed from the SDK manager (rev 5) and AVD setup, then replace the x86/ folder in $ANDROID_SDK_ROOT/system-images/android-29/google_apis/ with the one in the zip file.

Android Studio 3.4.2 is now available in the Stable channel.

If you already have an Android Studio build on the Stable channel, you can get the update by clicking Help > Check for Update (Android Studio > Check for Updates on macOS). Otherwise, you can download here.

This minor release improves stability and performance, and includes fixes for the following issues:

Gradle
  • Issue #131167099: Gradle Sync error: No value has been specified for property 'manifestOutputDirectory'.
IntelliJ
Shrinker (R8)
  • Issue #131167099: Gradle Sync error: No value has been specified for property 'manifestOutputDirectory'.
  • Issue #131140696: AbortException: Error: Undefined value encountered during compilation.
  • Issue #131207184: Android Studio 3.5 Canary 13 - Undefined value encountered during compilation, invalid dex input
  • Issue #130789358: java.lang.IllegalArgumentException: Multiple entries with same key
  • Issue #131443760: Android Gradle Plugin 3.5.0-alpha13 fails with R8 1.5.20-dev (build a85ccd499f6d149322870a8aedddc92152071a01
  • Issue #131505760: R8 don't support obfuscationdictionary on field

For information on new features and changes in all releases of Android Studio, see the Android Studio 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.