Recent Changes

    The following features and bug fixes were recently checked in. For complete details, see the git changelogs at

    Android Studio 0.4.4 Released

    posted Feb 5, 2014, 3:59 PM by Tor Norbye   [ updated Feb 5, 2014, 4:56 PM ]

    We've just released Android Studio 0.4.4 with the following improvements:
    • Bug fixes. A lot of them. Thank you for filing bugs at http://b.android.com, and keep them coming! Of particular note we've fixed the bug where library dependencies were sometimes dropped (and resources and Java symbols show up in red.)
    • Merged to the latest IntelliJ 13 EAP build 133.696
    • Retina support on OSX. If you're displaying Android Studio on a retina-density screen on OSX, using JDK 6 or recent versions of JDK 7, we will render your layouts in full Retina resolution. This is not just for layouts, but for the editor margin previews of drawable resources too. It's hard to convey this on a web page without Retina density, but here's a zoomed in view of the editor preview before (with Retina density text, and non-Retina icon painting as handled in Studio versions prior to 0.4.4) :


      Here's the same editor now with Retina handling of these drawable resources:
      This makes an even bigger difference in the layout editor and with the XML layout preview feature, since the images in question are much larger. You can typically see your phone layouts in full resolution (no scaling involved.)
    • Lint
      • Lint now checks Gradle files. It will warn about
        • Obsolete dependencies (e.g. not using the latest play services, not using the latest build tools, etc)
        • Using absolute paths
        • Using Windows path separators
        • Using incompatible combinations of tools libraries (such as using a support library older than the target SDK version)
        • Using + syntax in dependencies (not enabled by default)
        • Accidentally calling DSL methods (such as attempting to set versionName by calling a local method named getName)
        • Using constructs not properly handled by the IDE support (such as reassigning a project's directory)
      • New lint check warning about using a <WebView> with size wrap_contents
      • Lint checks suggesting to use SparseLongArray and LongSparseArray
      • Lint running inside Android Studio now consults a project's lint.xml (to for example change the severity of an issue from warning to error or vice versa)
    • The layout editor now supports rendering device frames (which was only available in layout preview until this point). It also has a render settings menu (to turn off device frames) and a Refresh action.
    • Templates
      • Newly created projects are initialized with the right build.gradle setup such that you can simply put .jar and .aar files into the libs/ directory and they will automatically be used (similar to how the libs/ folder worked in Eclipse ADT.)
      • The New Notification template is back (found under New > Android Component)
    • Gradle Integration
      • The Gradle daemon is shutdown on IDE exit, which should fix the Android Studio update mechanism on Windows (starting after the next update.)
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.4.4 page.

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

    Android Studio 0.4.3 Released

    posted Jan 23, 2014, 12:49 PM by Tor Norbye

    We've just released Android Studio 0.4.3, with the following improvements:
    • Support for the new version of the Android Gradle plugin 0.8. It does not require updating; you can continue to use version 0.7 of the gradle plugin with this version of Studio.
    • Updated to the latest IntelliJ 13 EAP build, #133.609 (release notes)
    • Gradle IDE support
      • Updating from one version of the Gradle plugin to the next is easier; rather than just opening a search window showing .gradle files referencing the plugin, the upgrade quickfix now performs the edits to the plugin dependency and the gradle wrapper properties file directly and in one shot
      • We now automatically sync with Gradle's model after a build if we detect that the model is stale
      • Fixed a bug around library syncing (where library dependency classes and resources could suddenly not be found by the IDE)
    • Lint
      • New lint check which looks for cycles in style definitions, cycles in layout <include> definitions, cycles in resource aliases and cycles in color and drawable definitions.
      • New lint check for duplicate item definitions inside styles
      • New lint check for padding symmetry in right-to-left contexts
      • New lint check for a resource definition pattern which can cause some versions of aapt to crash
    • Layout editing
      • The layout editor property sheet now handles setting properties in custom namespaces
      • Improved threading behavior of layout rendering code (which should make editing in the XML editor with the layout render preview window more responsive)
      • In addition to creating new locales from the Locale menu you can now open up and edit existing translations
      • Fixed bug where the layout editor could show stale resource strings
    • Eclipse Import
      • You can now import Eclipse-style projects even if they don't have .classpath and .project files as long as they use the same directory structure
      • More graceful handling of imports if there is a problem such as a missing dependency
    • Many other bug fixes
    Version 0.8 of the Android Gradle plugin provides the following improvements:
    • Supports Gradle 1.10, requires Build-Tools 19.0.0+
    • Fixed issue 64302: Add renderscript support mode jar to the dependencies in the IDE model.
    • Fixed issue 64094: buildConfigField can now replace previous values inside the same type/flavors.
    • Add support for NDK prebuilts in library projects.
    • Parallelize pre-dexing to speed up clean builds.
    • Incremental dexing re-enabled (though it'll be automatically disabled in some builds for some cases that dx doesn't support yet.)
    • Added 'provided' dependency scope for compile only (not packaged) dependencies. Additional scope per buildtype and flavors are also available (debugProvided, myFlavorProvided,etc...)
    • Variant API improvements:
      • getPreBuild() returns the prebuild task for the variant
      • getSourceSets() returns the sorted sourcesets for the task, from lower to higher priority
      • createZipAlignTask(String taskName, File inputFile, File outputFile).
        This creates and return a new zipalign task. Useful if you have a custom plugin providing custom signing of APKs. This also makes the assemble task depend on the new zipalign task, and wires variant.getOutputFile() to return the result of the zipalign task.
      • project.android.registerJavaArtifact() now receives a Configuration object to pass the dependencies to the IDE. See artifactApi sample.
    • New "lintVital" task, run automatically as part of assembling release variants, which checks only fatal-severity issues
    • Replace Java parser in lint with ECJ; must faster and fixes bug where lint could hang on certain source constructs
    • Lint HTML report now writes links to source files and images as URLs relative to the report location
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.4.3 page.

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

    Android Studio 0.4.2 Released

    posted Jan 8, 2014, 8:01 PM by Tor Norbye

    We've just released Android Studio 0.4.2, which fixes an important bug related to building projects found in 0.4.1 released earlier today.

    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.4.2 page.
    Problems?
    If you run into problems, be sure to check the Known Issues page which we'll update as necessary.

    Android Studio 0.4.1 Released

    posted Jan 8, 2014, 12:31 PM by Tor Norbye

    We've just released Android Studio 0.4.1, with the following improvements:
    • Updated to the latest Intellij 13.0.2 release build, 133.471. This means we picked up 8 new EAP builds relative to Android Studio 0.4.0:
    • Gradle IDE integration
      • New option for setting command line flags passed to Gradle, which for example allows you to pass any Gradle command line flag to the build, such as --stacktrace:
      • The project structure dialog now handles build.gradle file editing better, such as preserving comments and code blocks inside lists that it is editing
      • For newly created projects, the plugin and repositories are defined in a single place, in the top level build.gradle, rather than in each module’s build.gradle file.
      • Gradle 1.10 has been released, but Android Gradle plugin 0.7.3 (which Studio 0.4.1 is using) does not work properly with Gradle 1.10, and the error message was very confusing (because the plugin crashes before it gets to the version check). In 0.4.1 we detect the mismatched version earlier and give a sensible message. We are working on an updated Android Gradle plugin which (among other feature work) will work with Gradle 1.10.
      • Streamlined import. If a project contains a gradle wrapper, or if Studio knows where Gradle is installed, the project is imported directly without asking for more information.
      • Many fixes around Gradle sync error handling and notification. We now give better feedback during a sync (with editor notifications), and especially after a sync if the sync failed, since in that case a lot of functionality will not work right. There are more diagnostics and suggestions which should help pinpoint and address the problems.
    • Eclipse project import
      • Supports importing instrumentation tests. When importing an ADT project, it looks at the sibling directories and the child directories of the imported project, and if it finds an instrumentation ADT project, the sources are merged into the Gradle instrumentation test source set of the project.
      • Supports importing NDK projects. If the imported project contains NDK sources, these are imported into the jni/ source set of the project, the module name is inferred from the Makefile and stored in the Gradle file, and the ndk.dir property is defined in local.properties.
      • Additional import diagnostics, warning about SDK installs missing needed Maven repositories, using obsolete build tools, etc.
      • The import now handles more complex dependencies, using Eclipse linked resources, path variables, and so on. If you point to an Eclipse workspace (or if the project is inside a workspace, the import will find it automatically), it can use the workspace metadata to resolve path expressions; otherwise, you can provide manual mappings for these as part of the import wizard:
    • DDMS
      • New Heap Dump action, which lets you select a process, generate a heap dump and save it as an HPROF file for use with a memory profiler.
    • Lint
      • New manifest warning which flags attributes in a manifest file which are ignored and can therefore be misleading:
      • Fixed some false positives in checks when used in Gradle projects
    • Layout Rendering
      • If you have the latest API 19 SDK installed, Nexus 5 is available from the device list
    • Bug fixes
      • A lot of bug fixes, including but not limited to issues 63534, 63624, 12222499, 63623, 63881, 63622, 58302, 63596, 63926, 64358, 63928, 64014, 63997.
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.4.1 page.

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

    Android Studio 0.4.0 Released

    posted Dec 18, 2013, 7:02 PM by Tor Norbye

    We've just released Android Studio 0.4.0, with the following improvements:
    • Support for the new Android Gradle plugin, 0.7.0, which has improvements for render script, lint, BuildConfig, ProGuard, and additional features around source folders and flavors, along with many bug fixes. For more information, see the Build System documentation.
    • Note that Studio 0.4.0 requires the the new version of the Gradle plugin, so you have to migrate your projects to 0.7.0.  If you just update your IDE, after loading your old project the IDE will show this error balloon:
      At this point you can click on the "Search in build.gradle files" link, which will locate the gradle version definition:
      Change those to "0.7.0" (or 0.7.+ to pick up the latest dot release) :
      Now you need to sync the project model. (Yes, we're still working on detecting these changes more intelligently). Click on the "Sync Project with Gradle Files" toolbar button:
      If you're using the Gradle wrapper, you also need to switch it from Gradle 1.8 to Gradle 1.9. If you don't, the sync will show the following error balloon:

      Just click the error link to have Studio automatically convert the wrapper and you're all set.
    • Studio now supports Gradle Offline mode. This is useful if you find yourself without a network connection, and your dependencies are using the plus-syntax to pick up the latest available version. In that case, Gradle will once per day (by default) connect to the artifact repository to see if there is a more recent version. If that network connection fails, the build fails. If you don't have a network connection, this is problematic. You can now open the Compiler > Gradle options and enable Offline mode, which will tell Gradle to ignore update-to-date checks:

      Note that if you add a new dependency you'll still need to have a network connection to download the artifact. If you somehow forget that you are in offline mode, there is a balloon tip for that:
    • Initial Eclipse (ADT) project import. You can now directly import Eclipse projects (rather than having to export them to Gradle from Eclipse as in the past). This importer also makes structural changes to the import:
      • It migrates the project structure from the old ADT directory structure to the new Gradle-build system one
      • It removes inlined library projects that it recognizes (ActionBarSherlock, v7 GridLayout) and replaces the source code with a simple Gradle dependency to the corresponding library
      • Similarly it removes .jar files that it recognizes and replaces them with Gradle dependencies
      • It generates an import summary where it lists potential import issues (for example, if you were using library projects without manifest merging, there is potential manifest registration duplication now)
      • (The import does not yet fully support path variables and linked resources; this will be fixed in 0.4.1)
    • The Asset Studio wizard is now available (until this point it was only available as part of the New Project wizard for generating launcher icons). Right click on a drawable folder and invoke "New > Image Asset":
    • You can also create nine-patch images now by right clicking on .png images and invoking "Create Nine Patch...".
    • A large number of bug fixes, particularly around SDK handling and project import/upgrade, but also to the rendering sandbox, custom view rendering, template handling, etc.
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.4.0 page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.4; you will need to install a fresh build due to a bug in the patch updater in those versions.

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

    Android Studio 0.3.7 Released

    posted Dec 3, 2013, 5:10 PM by Tor Norbye   [ updated Dec 3, 2013, 5:10 PM ]

    We've just released Android Studio 0.3.7, with the following improvements:
    • Gradle
      • The experimental "Direct Gradle Invocation" mode is now the default. This should result in builds being about 20% faster, and the raw Gradle error output can now be found in the Gradle Console window. (You can turn off this mode in Settings > Compiler > Gradle). (The bug related to this with unsaved edits in Studio 0.3.6 has also been fixed.)
      • Improved error diagnostics. In addition to fixing error parsing for manifest merging errors, dex exceptions and multi-line javac errors, there are now import hyperlinks for resolving common import problems, such as missing platforms, missing support library repositories, or errors in local properties.
      • Improved SDK management. When opening a project which points to a specific SDK (via its local.properties file), Studio will check whether that SDK corresponds to the IDE SDK, and if not, will ask the user whether to use the Studio one or the project one. This ensures that IDE and command line builds are consistent.
      • "Add Library As..." on .jar files now works for Gradle projects; it adds in a proper dependency in the build.gradle file
      • New projects now create an empty gradle.properties file (with some commented out suggestions) to make it easier to tweak VM parameters for Gradle
      • Repositories for dependencies can now be edited in the Project Structure Dialog

    • Layout Editing:
      • Layout rendering sandbox: Custom views in layouts are now rendered in a sandbox such that they do not accidentally overwrite files or mistakingly execute commands if they believe they are running in a real Android environment. Note that if you download third party custom view libraries and insert references to these in your own layouts, and then view the layouts in the layout editor, the layout renderer will execute the custom view code in the IDE process with your desktop privileges. We do not promise a completely secure environment for libraries on the desktop; when adding third party libraries you should trust the source or validate that the Gradle files (which are executed at build time) and its custom views (which are executed in the layout editor) are safe. However, the layout rendering sandbox takes some initial steps to locking down access for custom views from doing thing accidentally. Thanks to Lawrence Angrave for discovering and reporting this potential danger.
      • RTL Support Improvements: When editing RelativeLayouts in the layout editor, the editor now creates RTL-aware layouts (using start/end in addition to (or instead of, depending on the minSdkVersion) left/right.
      • RTL Multi-configuration Editing: You can now edit your layouts and simultaneously see your layout rendered in an RTL context:
    • Templates
      • New templates for adding custom views, services, broadcast receivers, fragments, daydreams, etc. To invoke, right click on the target package and invoke New > Android Component.
    • Lint
      • New check looking for potential PRNG (pseudo random number generator) problems. Looks for code which may be affected by issues described in http://android-developers.blogspot.com/2013/08/some-securerandom-thoughts.html.
      • New lint check which looks for calls to Context#checkCallingPermission without using the result of that call (which probably meant to call Context#enforceCallingPermission instead).
      • New lint check which looks in Gradle projects for permission for use of the mock location provider permission and makes sure these are only specified in debug manifests. This helps avoid accidentally requesting that permission in release builds.

        There's also a quickfix in Studio for migrating the permission to a debug-specific manifest, though a bug prevents it from working if the debug folder already exists (fixed for next release).
    • Bug fixes. Lots of them. Some notable ones:
      • Fix weight handling when resizing elements in a LinearLayout
      • Properly compute bounds of <include> tags in layouts
      • Fix GridLayout editing with API 19
      • Adding activities via templates no longer clobber dependencies in the build.gradle file
      • API check now properly checks nested calls
      • Detect and abort layout rendering on cyclic parent styles
      • Don't flag hex color definition characters as potential typos
      • Fix bug where on startup, layout XML files would be missing the layout editor tab
      • Make Add Translation and Render Locales use only local locales, not all locales referenced by libraries
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.3.7 page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.4; you will need to install a fresh build due to a bug in the patch updater in those versions.

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

    Android Studio 0.3.6 Released

    posted Nov 14, 2013, 9:02 PM by Tor Norbye   [ updated Nov 14, 2013, 9:07 PM ]

    We've just released Android Studio 0.3.6, which fixes several important issues in 0.3.4 and 0.3.5:
    • Issue 62146: Can't open New Module wizard, IDE freezes
    • Issue 61939: Recent edits are not reflected in compiled app. (Also fixed related issues 62129 and 62168).
    • New Intellij EAP merge (to 132.1045: Release notes)
    • Issue 60916: Studio unable to run tests of a Java module
    • Issue 61488 : exclude build/res folder
    • Issue 61860: File choosers in Project Structure should create relative paths
    • Issue 61829: Allow Project Structure to deal with relative module names
    • Issue 60729: Mark res folders as resource folders
    • Issue 61769: Fix template such thatNavigationDrawer does not crash on older versions
    • Other project template changes (for example, move name primary module "app" and don't always append "Project")
    • New lint check which finds usages of check*Permission without consulting the return value (probably meant to use enforce*Permission)
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.3.6 page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.4; you will need to install a fresh build due to a bug in the patch updater in those versions.

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


    Android Studio 0.3.5 Released

    posted Nov 11, 2013, 3:18 PM by Tor Norbye

    We've just released Android Studio 0.3.5, which fixes two issues from Android Studio 0.3.4:
    • Issue 62011java.lang.NoClassDefFoundError: Could not initialize class org.gradle.internal.nativeplatform.filesystem.FileSystems$DefaultFileSystem
    • Certain source folders were incorrectly marked as generated folders
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.3.4 page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.4; you will need to install a fresh build due to a bug in the patch updater in those versions.

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

    Android Studio 0.3.4 Released

    posted Nov 8, 2013, 9:25 AM by Tor Norbye   [ updated Nov 8, 2013, 3:40 PM ]

    We've just released Android Studio 0.3.4 with the following improvements:
    • Updated platform to IntelliJ 13 beta: Beta announcementWhat's coming in IntelliJ IDEA 13?
      This incorporates three EAP builds since our Studio 0.3.2 snapshot:
    • Gradle
      • New Module editor. In 0.3.2 we introduced the module dependency editor where you could add libraries graphically; this is now just one tab among many other categories of module data you can edit: flavors, signing configurations, build types, etc. This area is still being actively worked on.
      • Gradle will now build the selected modules rather than all modules when Make is invoked with a selection.
      • Gradle Console. If you enable the new experimental in-process Gradle build mode (Compiler > Gradle > Use in-process build (faster, experimental)), you can open a Gradle Console which will show the full, raw Gradle output rather than just the simplified errors listed in the Messages window. The window does not open automatically, but the Messages window has a "Show Console Output" button in the left-hand-side toolbar, and it also adds a "See complete output in console" message you can double click on to trigger.
      • "Clean project" now runs a clean target to clear all build output.
      • A file-locking bug affecting Windows users (issue 61300) has been fixed. This bug would prevent cleaning and rebuilding a project as soon as a layout file had been opened.
    • Layout Editor
      • Support for using sourceCompatibility 1.7 even the IDE is running on JDK 1.6 (as it is by default on Mac OSX for example, even when JDK 1.7 is installed). We now convert the bytecode of compiled classes on the fly such that they can be executed by the layout renderer.
      • Support non-rectangular shapes in Drawable render preview
      • Drop preview now shows more accurate widget bounds
    • XML editor
      • When editing layouts, the layout_width and layout_height attributes are inserted automatically
      • The quote-matching bug (issue 11332) has been fixed
      • Namespace prefixes are now highlighted separate from attribute names
    • DDMS
      • Dumpsys support. You can now click on the Dumpsys action in the toolbar, which will execute "adb dumpsys" on the connected device and display information in the editor about the selected process.
      • Nexus 5 device images for the screenshot feature (which optionally surrounds the screenshot with device art).
      • Nexus 5 metadata for creating virtual devices in the emulator
    • Templates
      • Linked field editing. Editing parameter names such as activity names and layout names now dynamically update other suggestions. For example, if you change the activity name to "HomeActivity", the layout and fragment resource name suggestions change to "activity_home" and "fragment_home". It will also automatically pick unique names when appropriate such that you can create new activities without conflicting with existing ones.
    • The SDK manager is now available from Welcome Wizard so you can configure SDKs before creating a project
    • Many other bug fixes!
    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build 0.3.4 page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.4; you will need to install a fresh build due to a bug in the patch updater in those versions.

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

    What happened to 0.3.3?
    We released Studio 0.3.3 this morning, and shortly after release discovered an important bug which we fixed as quickly as we could. 0.3.4 is basically 0.3.3 plus a couple of bug fixes.

    Android Studio 0.3.2 Released

    posted Oct 31, 2013, 11:07 AM by Tor Norbye   [ updated Oct 31, 2013, 11:22 AM ]

    We've just released Android Studio 0.3.2. The main feature in this release is support for Android KitKat:
    • Support for language features like the diamond operator, multi-catch, try-with-resources, strings in switches, etc.
      When creating a new project, you can specify a source language level:

      (For existing projects, make sure you are using at least version 0.6.1 of the Gradle plugin, and then set the android.compileOptions.sourceCompatibility and targetCompatibility flags in your build.gradle file, update your buildToolsVersion version to 19, and re-sync the project to take advantage of these features. For more details, see this section in the user guide.)

      The IDE will now for example flag identical catch clauses and suggest they be combined:

      You can apply the intention action to use a multi-catch statement:

      Note that you can use all these language features not just with Android KitKat, but with older versions of Android too! There is one exception to that: try-with-resources, which will require minSdkVersion 19. Therefore, Studio will flag any uses in your code of try-with-resources if your minSdkVersion is less than 19:
    • Support for recording the device screen as a movie.
      In the Android DDMS window, there is a new movie-record button below the screenshot capture button, which will capture a movie on the connected device and retrieve the MP4 file.
    • Debugger support for the new ArrayMap class
    • The Studio+SDK bundle now includes Android KitKat. With existing installs, open the SDK manager to install it.
    In addition to the above Android KitKat related features, Studio 0.3.2 also fixes a number of bugs reported in 0.3.2, and adds support for previewing additional resource types:
    • Drawable XML files. When editing drawable XML files, you get an instant preview on the right:

      (In 0.3.2 non-rectangular shapes will show the wrong background color; this is fixed in 0.3.3.)
    • Menu XML files. Studio provides a sample rendering of the menu. This may not be accurate (since menu files can be used in various different contexts, and unlike layouts and drawables we are not directly running the framework code), but should still be helpful:

    • Widget XML files.
    We also have a new,experimental build strategy that is 20 to 30% faster than the current one, making speed of project builds in Studio closer to command line builds. It is a work-in-progress and is disabled by default. You can enable it by going to the Preferences dialog, navigate to the Compiler > Gradle page and check the box "Use in-process build."


    Installation
    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.
    If you need to download a full install, visit the Android Studio Canary Build page. Note that if you are currently running 0.2.10 or 0.2.11, on Mac OSX, you will not be able to patch update to 0.3.2; you will need to install a fresh build due to a bug in the patch updater in those versions.

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

    11-20 of 154