Updates archive

► 2018 2018 (90)
- ► September September (7)
- ► August August (16)
- ► July July (10)
- ► June June (13)
- ► May May (9)
- ► April April (11)
- ► March March (12)
- ► February February (9)
- ► January January (3)

▼ 2017 2017 (48)
- ▼ December December (3)
- ► November November (2)
- ► October October (8)
- ► September September (3)
- ► August August (4)
- ► July July (3)
- ► June June (3)
- ► May May (4)
- ► April April (5)
- ► March March (5)
- ► February February (6)
- ► January January (2)

► 2016 2016 (5)
- ► December December (3)
- ► November November (2)

Subscribe to updates

Posts

Atom

Posts

Release updates archive

Android Studio 3.1 Canary 6 is now available

Wednesday, December 20, 2017

Android Studio 3.1 Canary 6 is now available in the Canary and Dev channels.
If you are upgrading from 3.1 Canary 1, 2, or 3, you need to download the latest version of the IDE from the Android Studio Preview site.
You might receive an error when updating your project to 3.1 Canary 6. If so, you need to manually change the Android Gradle plugin version to 3.1.0-alpha06 as shown here:buildscript { dependencies { classpath 'com.android.tools.build:gradle:3.1.0-alpha06' } } Then click Sync Project with Gradle Files

. The first sync will fail and you'll see a message asking you to upgrade the Gradle version in the wrapper, so follow the Quick Fix to apply the update.
This release includes general bug fixes and the following new features:

Upgrades the base IDE to IntelliJ 2017.3. You may notice changes in behavior and performance as a result of this merge. If you encounter changes you believe to be regressions, please report a bug.

Updates the Kotlin plugin to version 1.2.

Updates to Data Binding:

You can now use a LiveData object as an observable field in data binding expressions. The ViewDataBinding class now includes a new setLifecycle method that you need to use to use to observe LiveData objects.
New compiler: You can preview a new incremental compiler for your data binding classes. To enable this compiler, add android.databinding.enableV2=true to your gradle.properties file, or include the following command line argument: -Pandroid.databinding.enableV2=true. Keep in mind, this compiler is not backwards compatible, so you need to recompile all of your data binding classes with this feature enabled to take advantage of incremental compilation. Note the following behavior changes when using the new compiler:

The Android plugin for Gradle now generates Binding classes for your layouts before compiling your Java code.
If a layout is included in more than one target resource configuration, the data binding library now defaults the view type to android.view.View for all views that share the same resource id but not view type.
Binding classes for library modules are compiled and packaged with its AAR. That is, app modules that depend on those library modules no longer need to regenerate those classes.
A module’s binding adapters can no longer change the behavior of adapters of the module’s dependencies. That is, binding adapters now only affect code in its own module and downstream consumers of the module.

The ObervableField class can now accept other Observable objects in its constructor. The ObservableField object registers a change when one of its Observable dependencies register a change.

Known issues:

Updating existing projects to the alpha 6 Android Gradle plugin fails. You must manually update to 3.1.0-alpha06 as described above.
When using Java 8 language features, the intentions menu item to “Set Language Level to 8" is missing.
AAPT2 may throw an error when adding a tabbed activity to a project which is created with Maps activity.
You may get an IsolationException error while building LintTest project.
Certain devices may cause a java.lang.AssertionError while working with profilers.
You may receive a "File Creation failed" error while recording espresso tests for Instant Apps that include code written in Kotlin.
You may receive a fatal exception when using Java 8 language features with Android Instant Apps projects.
Your app may see FATAL_EXCEPTION "Error inflating class ImageView" when adding color resources to an ImageView using the theme attribute.
You may receive a TimeoutException while deploying a Wear project to the emulator.
When creating a Android Instant Apps project that includes a BottomNavigationView, you may get a null pointer exception.

If you already have an Android Studio build on the Canary or Dev channel, you can get the update by clicking Help > Check for Update (or Android Studio > Check for Updates on Mac). Otherwise, you can download here.

Google

ConstraintLayout 1.1.0 beta 4

Friday, December 15, 2017

dependencies { compile 'com.android.support.constraint:constraint-layout:1.1.0-beta4'}https://developer.android.com/reference/android/support/constraint/ConstraintLayout.html

Fixes issue with incorrect spread in Chain

Fixes RTL issues (guideline, chains, bias)

Fixes missing percent handling in ConstraintSet

Fixes various barriers issues

Improved xml inflation speed

Google

Android Studio 3.1 Canary 5 is now available

Tuesday, December 5, 2017

Android Studio 3.1 Canary 5 is now available in the Canary and Dev channels, and includes general bug fixes and the following new features:

Includes in-process desugaring to decrease compile time when using Java 8 language features. To try this preview feature, set android.enableD8.desugaring=true in your project’s gradle.properties file.
In the Network Profiler, a new Request tab provides network request details, as shown below.

In the CPU Profiler, a new search feature allows you to highlight relevant trace results in Trace Pane, as shown below. This feature is also available in the Memory Profiler to filter the results of your memory allocations or heap dumps. To enter a search query, click the icon at the top-right corner of the pane and then click on the search box.

In the CPU profiler Flame Chart pane, call stacks that include the search query are highlighted and moved to the left side of the chart.
Known Issue: In the Top Down and Bottom Up CPU profiler charts, relevant search results are prioritized above others when a column is sorted in a descending order. However, this prioritization does not take place when columns are sorted in an ascending order.
Known Issue: When pausing while entering a search query in the CPU profiler, the IDE updates the results with your query and disables the cursor within the search field. That is, you need to click into the search field again to continue typing.

If you already have an Android Studio build on the Canary or Dev channel, you can get the update by clicking Help > Check for Update (or Android Studio > Check for Updates on Mac). Otherwise, you can download here.

Google