Update 2: They have added an option to enable it again in Support Library 23.4.0:
For AppCompat users, we’ve added an opt-in API to re-enable support Vector Drawables from resources (the behavior found in 23.2) via AppCompatDelegate.setCompatVectorFromResourcesEnabled() – keep in mind that this still can cause issues with memory usage and problems updating Configuration instances, hence why it is disabled by default.
This no longer works starting from version 23.3.0
For AppCompat users, we’ve decided to remove the functionality which
let you use vector drawables from resources on pre-Lollipop devices
due to issues found in the implementation in version 23.2.0/23.2.1
[https://code.google.com/p/android/issues/detail?id=205236, https://code.google.com/p/android/issues/detail?id=204708]. Using app:srcCompat
and setImageResource() continues to work.
Using AppCompat and app:srcCompat is the most foolproof method of integrating vector drawables into your app.
That quote is from the official blogpost for the release of version 23.2.0 of the Support Library.
The post also mentions the following:
You’ll find directly referencing vector drawables outside of
app:srcCompatwill fail prior to Lollipop. However,
AppCompatdoes support loading vector drawables when they are referenced in another drawable container such as a
RotateDrawable. By using this indirection, you can use vector drawables in cases such as
android:drawableLeftattribute, which wouldn’t normally be able to support vector drawables.
This translates to the steps below:
Create or import a vector resource which you require for the app. For example, one can create a vector drawable for the search icon and name it
Create another proxy drawable resource for the vector drawable previously created. Say, for the previous
ic_action_search.xml can be created as a simple
StateListDrawable which could contain the lines below:
<?xml version="1.0" encoding="utf-8"?> <selector xmlns:android="http://schemas.android.com/apk/res/android"> <item android:drawable="@drawable/ic_action_search_vector"/> </selector>
This step can be skipped if you have referenced the vector drawable from another drawable resource which you will use with your View.
Use the drawable resource (here,
ic_action_search.xml) that refers to the vector drawable (
ic_action_search_vector.xml) instead of the vector drawable directly. For a menu, it would look like:
<item android:id="@+id/search" android:title="@string/search" android:icon="@drawable/ic_action_search" app:showAsAction="always"/>
This is the solution to that problem!