Recent Changes‎ > ‎

Android Studio 1.4 RC 1 Available

posted Sep 18, 2015, 9:35 AM by Tor Norbye   [ updated Sep 18, 2015, 10:57 AM ]
We've just released Android Studio 1.4 RC 1 to the canary channel.

We've also promoted 1.4 Beta 4 to the beta channel, since that build has been in testing for a few days now and there are no big problem. (However, if you're on Linux and using a high density display you may want to jump directly to RC 1 where there are important fixes for that configuration.)

RC 1 contains bug fixes in a number areas:
  • Fixes for high-density displays on Linux (and in general, we have more information on how to configure high density displays for Windows and Linux in this document)
  • Many more fixes to the templates (activities, etc), visual refresh, and removed misc warnings
  • Vector icons displayed properly in the editor margin
  • Layout editor bug with duplicate id's in RelativeLayouts
  • Auto completion of upper-cased permission names in manifest files
  • Inferring nullity in multi-module project
  • Lint warns about missing platform-tools 23.0.1 (prevents properly API checking Android M calls) or using buildTools pre-23.0.1 (to prevent crashes on some devices for RTL attributes)
  • Fix build errors with vector image generation on OSX when using Java 6 to run the IDE and Java 7 to run the IDE ("Could not find class: apple.awt.CGraphicsEnvironment")
  • Fix git module configuration bug
  • Misc theme editor bugs
  • Misc crash reporter bugs
Installation
If you are already using a 1.4 Preview/Beta build, you can use the builtin Update mechanism to upgrade directly to 1.4 RC 1.

If you are using 1.3.1, you can also update via a patch, but, you may not want to do that; patch-updating to this new version will replace your existing stable installation with a preview version. Instead, you can download a separate installation of 1.4 from the Android Studio 1.4 RC 1 page. You can keep 1.3.2 and 1.4 Beta 4 installed side by side; they use separate settings and cache directories.

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


Comments