Platform | Package | Size | MD5 Checksum |
---|---|---|---|
Windows | android-studio-bundle-130.737825-windows.exe | 396091268 bytes | 6da1bc8effa048c8ff669e4c484eb11f |
Mac OS X | android-studio-bundle-130.737825-mac.dmg | 383326582 bytes | 2959bc5039238d286670cc6225342b89 |
Linux | android-studio-bundle-130.737825-linux.tgz | 409935592 bytes | dcd13922f7cf577e3c852b224205d843 |
Updating to 0.2.x
To update from Android Studio 0.1.x to 0.2.x, follow the installation instructions below and replace your existing installation.
Caution: Replacing your existing installation of Android Studio will remove any additional SDK packages you've installed, such as target platforms, system images, and sample apps. To preserve these, copy them from your current SDK directory under Android Studio to a temporary location before installing the update. Then move them back once the update is complete. If you fail to copy these packages, then you can instead download them again through the Android SDK Manager.
Also note that due to the update to Gradle 0.5, you will encounter errors when opening existing projects. See theTroubleshooting notes below for information about how to resolve them.
Installing Android Studio
- Download the Android Studio package from above.
- Install Android Studio and the SDK tools:
Windows:
- Launch the downloaded EXE file,
android-studio-bundle-<version>.exe
. - Follow the setup wizard to install Android Studio.
Known issue: On some Windows systems, the launcher script does not find where Java is installed. If you encounter this problem, you need to set an environment variable indicating the correct location.
Select Start menu > Computer > System Properties > Advanced System Properties. Then openAdvanced tab > Environment Variables and add a new system variable
JAVA_HOME
that points to your JDK folder, for exampleC:\Program Files\Java\jdk1.7.0_21
.
Mac OS X:
- Open the downloaded DMG file,
android-studio-bundle-<version>.dmg
. - Drag and drop Android Studio into the Applications folder.
Known issue: Depending on your security settings, when you attempt to open Android Studio, you might see a warning that says the package is damaged and should be moved to the trash. If this happens, go toSystem Preferences > Security & Privacy and under Allow applications downloaded from, selectAnywhere. Then open Android Studio again.
Linux:
- Unpack the downloaded Tar file,
android-studio-bundle-<version>.tgz
, into an appropriate location for your applications. - To launch Android Studio, navigate to the
android-studio/bin/
directory in a terminal and executestudio.sh
.You may want to add
android-studio/bin/
to your PATH environmental variable so that you can start Android Studio from any directory.
- Launch the downloaded EXE file,
That's it! You're ready to start developing apps with Android Studio.
Note: On Windows and Mac, the individual tools and other SDK packages are saved within the Android Studio application directory. To access the tools directly, use a terminal to navigate into the application and locate thesdk/
directory. For example:
Windows: \Users\<user>\AppData\Local\Android\android-studio\sdk\
Mac: /Applications/Android\ Studio.app/sdk/
For a list of some known issues, see tools.android.com/knownissues.
Starting a Project
When you launch Android Studio for the first time, you'll see a Welcome screen that offers several ways to get started:
- To start building a new app, click New Project.
This starts the New Project wizard, which helps you set up a project using an app template.
- To import an existing Android app project, click Import Project.
Note: If you previously developed your Android project with Eclipse, you should first use the new export feature in the ADT plugin to prepare your project with the new Gradle build system. For more information, read Migrating from Eclipse.
For additional help using Android Studio, read Tips and Tricks.
As you continue developing apps, you may need to install additional versions of Android for the emulator and other packages such as theAndroid Support Library. To install more packages, use theSDK Manager, which you can open from Android Studio by clickingSDK Manager in the toolbar.
Revisions
Note: There is not a patch update available from 0.1.9 to 0.2. To update from Android Studio 0.1.x to 0.2.x, you must install a new Android Studio bundle from this page. The reason for that is that we have made changes to the bundled SDK such that it includes a pre-configured local Maven repository which can serve up the v4 support library and which is required for creating new projects.
Android Studio v0.2.x(July 2013)
- Merged in the latest IntelliJ codebase changes. Includes fixes for issues reported by Studio users such as tweaks to Linux font sizes and font rendering.
- Android Gradle plug-in updated to 0.5.0.
Caution: This new version is not backwards compatible. When opening a project that uses an older version of the plug-in, Studio will show an error statingGradle <project_name> project refresh failed. See Troubleshooting below for details.
The updated Gradle plug-in includes the following changes:
- Fixed IDE model to contain the output file even if it's customized through the DSL. Also fixed the DSL to get/set the output file on the variant object so that it's not necessary to use
variant.packageApplication or variant.zipAlign
- Fixed dependency resolution so that we resolved the combination of (default config, build types, flavor(s)) together instead of separately.
- Fixed dependency for tests of library project to properly include all the dependencies of the library itself.
- Fixed case where two dependencies have the same leaf name.
- Fixed issue where Proguard rules file cannot be applied on flavors.
All Gradle plugin release notes are available are here: http://tools.android.com/tech-docs/new-build-system.
- Fixed IDE model to contain the output file even if it's customized through the DSL. Also fixed the DSL to get/set the output file on the variant object so that it's not necessary to use
- Gradle errors from aapt no longer point to merged output files in the build/ folder, they point back to the real source locations.
- Parallel Builds. It's now possible to use Gradle's parallel builds. Please be aware that parallel builds are in "incubation" (seeGradle's documentation.) This feature is off by default. To enable it, go to Preferences > Compiler and check the box Compile independent modules in parallel.
- Further work on the new resource repository used for layout rendering, resource folding in the editor, and more:
- Basic support for .aar library dependencies (e.g. using a library without a local copy of the sources). Still not working for resource XML validation and navigation in source editors.
- Cycle detection in resource references.
- Quick Documentation (F1), which can show all translations of the string under the caret, will now also show all resource overlays from the various Gradle flavors and build types, as well as libraries. They are listed in reverse resource overlay order, with strikethrough on the versions of the string that are masked.
- Fixes to handle updating the merged resources when the set of module dependencies change.
- XML rendering fixes to properly handle character entity declarations and XML and unicode escapes.
- Save screenshot support for the layout preview and layout editor windows.
- Template bug fixes.
- Lint bug fixes.
- Various fixes for crash reports. Thank you, and keep filing crash reports!