posted Oct 3, 2013, 1:13 PM by Tor Norbye
updated Oct 3, 2013, 1:59 PM
We've just released Android Studio 0.2.11. This release contains the following improvements:
- Updated the IDE base to the IntelliJ EAP build #132.425 sources. The release notes for this version of the IDE which lists the bugs fixed are here:
Of particular interest to Android Studio users is the new support for Gradle code insight and dependency resolving
- Canary and Dev channels
- Layout rendering
- Support for designtime attributes, which allow you to show sample data in your layouts without affecting the runtime app. For more details, see Designtime Layout Attributes.
- Included layouts now render the edited (unsaved) contents of other editor buffers
- The layout preview is smarter about when to trigger a re-render; for example, it will ignore edits that affect only whitespace or comments, edits to an attribute that does not yet have a value, etc.
- There's now a large progress indicator in the center of the view for the first render, and a smaller indicator in the upper right corner when re-rendering after editor switches.
- Fixed issue where the render preview window sometimes didn't open automatically on IDE restart, and fixed issue where switching between files would sometimes briefly show the old layout contents.
- Improved error message when you accidentally use a drawable resource in place of a color resource
- Text editing
- Resource inlining: Dimension and integer resources are now also inlined, as well as string resources outside method calls. Perhaps more importantly, the long standing issue of resource folds showing stale contents or appearing on the wrong code statement has been fixed (see bug 60529).
- The editor spell checker is now aware of the target language used in a Android string resource file, and will no longer use the English dictionary to flag "errors" in for example Spanish text in values-es/strings.xml. If your base
values/ folder is not in English, use the
tools:locale attribute on the root <resources> element to let the tools know what your default language is.
- Theme resolution chain display (added in 0.2.10, see Android Studio 0.2.10 Released) now also handles theme attributes (such as
- Fixed XML validation for dimensions to allow floating point numbers
- Android Device View, LogCat
- Console code folding for elided stack frames. When an exception is nested, the VM will truncate the stack display of the inner exception. It does this when it gets to a point where the rest of the stacktrace is the same as in the outer stacktrace, but many users were not aware of that and thought they were missing vital information. In LogCat inside Android Studio, we now create a fold region on the "4 more ...lines" section, and when you expand it we reconstruct the full stack trace.
- You can now view the logcat output of a particular process by just clicking on the process in the device panel. If you don't want this behavior, you can deselect the toggle button "Only show logcat from selected process" on the logcat toolbar.
- New check for duplicate words in strings
- Fixed some bugs (which had resulted in false positives in source code involving enums or string arrays)
- New projects: Improved package validation. Android application package names have stricter package name requirements than Java packages: Package segments cannot start with an underscore, and only ASCII letters (and digits, dots and underscores) can be used.
- Misc bug fixes in the gradle build area.
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 http://developer.android.com/sdk/installing/studio.html#download . 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.