[go: up one dir, main page]

Release updates archive

Android Emulator 28.0.10 is now available in the Canary and Dev channels.
  • Fixed an issue where the emulator would sometimes incorrectly report "Guest hasn't come online" if the currently running app lacked animation.


Android Studio 3.3 Canary 12 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:
  • CMake version 3.10.2: CMake version 3.10.2 is now included with SDK Manager. Note that Gradle still uses version 3.6.0 by default. To specify a CMake version for Gradle to use, add the following to your main module’s build.gradle file:

    android {
        ...
        externalNativeBuild {
            cmake {
                ...
                version "3.10.2"
            }
        }
    }
    
  • Delete Unused Directories Dialog: When a new major version of Android Studio is run for the first time, it looks for directories containing caches, settings, indices, and logs that are associated with old versions of Android Studio for which a corresponding installation can’t be found. When found, a dialog displays their locations, sizes, and last-modified times and provides the option to delete them.


This update includes fixes for several bugs, including the following:
  • Some deprecated kotlin-stdlib-jre* artifacts were still being used when creating new projects.
  • AAPT2 was crashing when project folders were on a different drive than the build folder.


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 is now available in the Stable channel. You can download it here.

Known issues

  • We strongly recommend against updating to Kotlin 1.2.70. Android Studio includes a version of Kotlin 1.2.61 that fixes a bug that can cause Android Studio to hang. Kotlin 1.2.71 and later also include this fix. Kotlin 1.2.70 does not include this fix.
  • Typically, you do not need to manually specify which verison of Android Build Tools for Android Studio to use. However, to use the current build tools when using Android Gradle plugin 3.2.0 with renderscriptSupportModeEnabled set to true, you do need to include the following in each module's build.gradle file:

    android.buildToolsVersion "28.0.3"


    A future update of the Android Gradle plugin is intended to address this issue.

What's new

For an overview of what's new in this release, see the release notes.

Jamal Eason, a product manager on the Android developer tools team, has an excellent overview of what's new in Android Studio 3.2 on the Android Developers blog.

For details, see these sections of the Android Studio documentation:


Android Emulator 28.0.9 is now available in the Canary and Dev channels.
  • -gpu guest (software rendering in the guest) has been deprecated. API 28+ system images will now auto switch to using Swiftshader (-gpu swiftshader_indirect).
  • We have received reports of emulator hangs on Mac when the AVD is configured with 4 GB of guest RAM. If you are experiencing this, please file an issue in Issuetracker: https://issuetracker.google.com/issues?q=componentid:192727


Android Studio 3.3 Canary 11 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:
  • When using Gradle Kotlin DSL, you can now set source and target compatibility in compileOptions via the following syntax:
    compileOptions {
      sourceCompatibility = JavaVersion.VERSION_1_8
      targetCompatibility = JavaVersion.VERSION_1_8
    }
  • Improved incremental Java compilation when using annotation processors: This update decreases build times by improving support for incremental Java compilation when using annotation processors.
    • For projects that include Kotlin code: Incremental Java compilation is enabled by default, even if your project uses the data-binding or retro-lambda plugin.
    • For Java-only projects:
      • If the annotation processors you use all support incremental annotation processing, incremental Java compilation is enabled by default.
      • If however, one or more annotation processors do not support incremental builds, incremental Java compilation is not enabled. Instead, you can include the following flag in your gradle.properties file:
        android.enableSeparateAnnotationProcessing=true
        When you include this flag, Gradle executes the annotation processors in a separate task and allows the Android plugin to enable incremental mode for the Java compilation task.
    Note: If your project uses the Lombok annotation processor, incremental Java compilation may be disabled.
  • Android App Bundles now support Instant Apps: Android Studio now includes support for building Android App Bundles with full support for Instant Apps. In other words, you can now build and deploy both installed app and Instant App experiences from a single Android Studio project, and include them in a single Android App Bundle.

    If you’re creating a new Android Studio project using the Create New Project dialog, make sure you check the box next to Configure your project > This project will support instant apps. Android Studio then creates a new app project as it normally would, but includes the following properties in your manifest to add instant app support to your app’s base module:

    <manifest ... xmlns:dist="http://schemas.android.com/apk/distribution">
        <dist:module dist:instant="true" />
        ...
    </manifest>
    

    You can then add dynamic feature modules that are instant app-enabled by selecting File > New > New Module from the menu bar and then selecting Instant Dynamic Feature Module from the Create New Module dialog.

    If you already have a project that supports Dynamic Delivery, you can still add instant app-enabled dynamic features using the New Module wizard, as described above. However, keep in mind that doing so also enables instant app support for your app’s base module.

    To deploy your app to a local device as an instant app, edit your run configuration and check the box next to General > Deploy as instant app.

  • Support for Clang-Tidy: Android Studio now includes support for static code analysis using Clang-Tidy for projects that include native code. To enable support for Clang-Tidy, you need to update your NDK to r18 or higher.

    You can then enable or re-enable the inspections by opening the Settings or Preferences dialog, navigating to Editor > Inspections > C/C++ > General > Clang-Tidy. When selecting this inspection in the Settings or Preferences dialog, you can also see the list of Clang-Tidy checks the IDE enables and disables by default under the Option section of the right-most panel. To enable additional checks, simply add them to the list and click Apply.

    To configure Clang-Tidy with additional options, click Configure Clang-Tidy Checks Options and add them in the dialog that opens.



This update includes fixes for several bugs, including the following:
  • Fixed an issue in Layout Editor that was causing java.lang.NoSuchMethodError when previewing a customized date.


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 Emulator 28.0.8 is now available in the Canary and Dev channels.
  • Users have reported that the emulator has been slow recently. We have found that a possible cause of slowdown is that the temp directory for the emulator ends up with too many stale files inside. As a workaround, in 28.0.8+, we do not store ADB liveness check files in that directory anymore. However, it may also help to delete the contents of that folder. Make sure that no emulator is running when deleting those files.
    • Windows: C:\Users\<username>\AppData\Local\Temp\AndroidEmulator\*
    • Mac/Linux:/tmp/android-<username>/*
  • The Quick Boot notification icons have been revised to be more understandable to non-English-speaking users.
  • The MIPS build has been removed. If you still require MIPS, please file an issue.


Android Studio 3.3 Canary 10 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 Android Gradle plugin now requires Gradle 4.10 or higher.
  • Improved classpath dependency synchronization: When resolving dependencies on your runtime and compile time classpaths, the Android Gradle plugin attempts to fix certain downstream version conflicts for dependencies that appear across multiple classpaths.
  • Lazy task configuration: The Android Gradle plugin now uses a new task configuration API, which avoids the cost of creating and configuring tasks during Gradle’s configuration phase when those tasks are not going to be executed. This lets the plugin do less work when building just one of many variants in each module.
  • New projects now contain the /.idea/caches path in .gitignore.


This update includes fixes for several bugs, including multiple linter fixes.

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.3 Canary 9 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:
  • IntelliJ IDEA 2018.2.2: The core Android Studio IDE has been updated with improvements from IntelliJ IDEA through the 2018.2.2 release.
  • When you change the width or height of a view in the Layout Editor without specifying a unit, Android Studio now appends a default dp unit value in both the Layout Editor and the corresponding XML.
  • Gradle now copies extracted ProGuard rules to the local project build directory instead of the root project build directory. This ensures that tasks from different projects do not share the same output directory, which can lead to Gradle synchronization issues.


This update includes fixes for several bugs, including the following:
  • gradlew clean command was occasionally failing.
  • Android Studio wasn't correctly reporting some of the possible values for android:fontFamily.
  • Layout Editor Preview window wasn't scaling images properly.


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 Release Candidate 3 (RC3) is now available in the Beta channel.

RC3 is expected to be the final release candidate for Android Studio 3.2. If we find no additional blocking issues, this is the version of Android Studio 3.2 that we will release to the Stable channel. We’ve worked to fix a number of memory issues and bugs, as well as to bring a set of improvements and new features, and now we need your help to ensure that we're ready. Please, try this preview version in all of your regular workflows, and let us know if you encounter any issues that you think need to be addressed before we release Android Studio 3.2 to the Stable channel. We know that many of you have come to rely on Android Studio in your day-to-day work, and we greatly appreciate your help in ensuring that we have a high-quality release for you.

This update include fixes for the following bugs:

  • There were known issues with Kotlin 1.2.60 that are addressed with the Kotlin 1.2.61 components in this build.
  • "Manifest merger failed" and "Failed to resolve" errors occurred when using design libraries.
  • Errors and hangs occurred after migrating a project to AndroidX.
  • Incorrect libraries were being used after migrating a project to AndroidX.


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.

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

As requested above, 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 28.0.7 is now available in the Canary and Dev channels.

Changes:
  • Fixed an issue where -writable-system / -system command line arguments resulted in a failure to launch the emulator.