Recent Changes‎ > ‎

    Android Studio 0.2.10 Released

    posted Sep 24, 2013, 5:33 PM by Tor Norbye   [ updated Sep 24, 2013, 5:37 PM ]
    We've just released Android Studio 0.2.10. This release contains the following improvements:
    • Updated the IDE base to the IntelliJ EAP build #132.325 sources. The release notes for this version of the IDE which lists the bugs fixed are here:
      • This fixes the dark theme todo-token color many users reported
    • New integrated performance trace file viewer:
      If you already have .trace files that you have generated programmatically or with DDMS, just open it in Android Studio with File > Open. Otherwise, open the DDMS view (View > Tool Windows > Android), select your application, and click on the “Start Method Tracing” icon:
      For more information about traceview, see the traceview document.
    • Improved Quick Documentation (View > Quick Documentation, or F1)
      • Now resolves framework resources as well, such as @android/string/ok => "Ok"
      • The quick documentation now shows the resource resolution chain. Here we're showing quick documentation for @android:color/primary_text_dark; in addition to resolving this to the color #ffffff, which is shown, it also shows the color reference chain was @android:color/primary_text_dark, which pointed to a statelist file primary_text_dark.xml, and from there we picked up the default state to go to @android:color/bright_foreground_dark, which resolves to @android:color/background_light, and that color is finally defined as #ffffffff. (There are some additional fixes for this feature to handle theme attributes (?name) in the preview build.)
      • As shown above, we now preview colors (previously we only showed drawable bitmaps, and textual resources such as strings and dimensions).
      • For array resources, we now display the elements of the arrays
      • In Java files, resource documentation and editor margin previewing now properly handles android.R resources.
      • The feature which displays icons in the left hand gutter for drawable references is now finds the smallest density bitmaps of a resource to use for editor margin previews. Since large images are ignored for performance reasons, this makes more icons eligible for editor preview.
    • Layout Rendering
      • Layout rendering now detects <include> cycles in layout dependencies and displays the invalid chain
      • Added new Nexus 7 device specs to the preview render device list along with device frame art (which also works for the Screenshot action)
      • If you have the Android source code installed for the Android version currently being rendered, and a custom view throws an exception during painting, the stack frame displayed in the error output will hyperlink directly to the relevant code in the Android source code for frames in the android package.
    • Editing
      • Indirect AAR library dependencies are now handled correctly
    • Gradle Integration
      • Much faster project import! When using Gradle 1.8 and the Android Gradle plug-in 0.5.7 you'll experience considerably faster project imports.
      • Android Studio now saves Gradle's VM options across sessions
      • Further improvements to the Gradle output parser: it now recognizes duplicate resource errors specifically, and adds separate error messages pointing directly to each of the declaration locations in the separate files
      • Fixed bug where it was not possible to import a project using the Gradle wrapper with Gradle 1.6
    • Fixed miscellaneous bugs, including a deadlock
    If you are already running Android Studio, just restart it, or manually check for updates via Help > Check for Update... (on OSX, look in the Android Studio menu).  This will download and install a small patch rather than download a full IDE image. We are not posting full installers for each weekly update. If you do not already have Android Studio, install the latest full install from . When you run that version, it will check for updates and upgrade itself via the patch mechanism.

    If you run into problems, be sure to check the Known Issues page which we'll update as necessary.