[Solved] android.view.InflateException: Binary XML file line #12: Error inflating class

I am receiving many errors of kind displayed in the subj. These errors seems to be occasional and I cannot reproduce them. From stack I can learn that such error may occurs for my different layout resources. The line of XML is also varying.

Can anybody explain why this error occurs? And what I can do to fix this problem?


============================================================= generated the following exception:
java.lang.RuntimeException: Unable to start activity ComponentInfo{}: android.view.InflateException: Binary XML file line #12: Error inflating class <unknown>

--------- Stack trace ---------
5. android.os.Handler.dispatchMessage(
6. android.os.Looper.loop(
8. java.lang.reflect.Method.invokeNative(Native Method)
9. java.lang.reflect.Method.invoke(
12. dalvik.system.NativeStart.main(Native Method)

----------- Cause -----------
android.view.InflateException: Binary XML file line #12: Error inflating class <unknown>

1. android.view.LayoutInflater.createView(
3. android.view.LayoutInflater.createViewFromTag(
4. android.view.LayoutInflater.rInflate(
5. android.view.LayoutInflater.rInflate(
6. android.view.LayoutInflater.inflate(
7. android.view.LayoutInflater.inflate(
8. android.view.LayoutInflater.inflate(
11. com.solvek.sample.ui.BaseActivity.onCreate(
12. com.solvek.sample.ui.tour.TourActivity.onCreate(
18. android.os.Handler.dispatchMessage(
19. android.os.Looper.loop(
21. java.lang.reflect.Method.invokeNative(Native Method)
22. java.lang.reflect.Method.invoke(
25. dalvik.system.NativeStart.main(Native Method)

-------- Environment --------
Time =2010-12-20 08:27:35 AM
Device =tmobile/htc_espresso/espresso/espresso:2.1-update1/ERE27/216830:user/release-keys
Make =HTC
Model =T-Mobile myTouch 3G Slide
Product =htc_espresso
App, version 2.0.9 (build 1232)

Here is a result of XML, however such error occurs in other xmls

<?xml version="1.0" encoding="utf-8"?>
<merge xmlns:android="">
    <ViewFlipper android:layout_gravity="fill" android:id="@+id/flipper" android:layout_height="fill_parent" android:layout_width="fill_parent">
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_1"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_2"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_3"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_4"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_5"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_6"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_7"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_8"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_9"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_10"/>
        <ImageView android:scaleType="fitXY" android:layout_width="fill_parent" android:layout_height="fill_parent" android:src="@drawable/tour_11"/>

    <LinearLayout android:id="@+id/exit_bar" android:layout_gravity="top" android:layout_width="fill_parent" android:layout_height="wrap_content" android:background="@drawable/blue_bar" android:visibility="invisible">
        <Button android:background="@drawable/orange_btn" android:layout_height="wrap_content" android:layout_width="wrap_content" android:layout_gravity="center" android:textStyle="bold" android:textColor="#000000" android:shadowColor="#ffffff" android:shadowRadius="1.6" android:shadowDx="1.5" android:shadowDy="1.3" android:id="@+id/exit_tour_btn" android:text="Exit" android:layout_marginLeft="20dip"/>
        <TextView android:layout_height="wrap_content" android:textColor="#ffffff" android:layout_gravity="center" android:layout_width="110dip" android:layout_marginLeft="20dip" android:textSize="16dip" android:textStyle="bold" android:text="Life360 Tour"/>


    <Button style="@style/BlueBtn" android:text="Continue" android:layout_marginTop="40dip" android:id="@+id/continue_btn" android:visibility="gone" android:layout_height="wrap_content" android:layout_width="wrap_content" android:layout_gravity="center" />

    <FrameLayout android:id="@+id/bottom_bar" android:layout_gravity="bottom" android:layout_width="fill_parent" android:layout_height="wrap_content" android:background="@drawable/blue_bar" android:visibility="invisible">
        <ImageView android:layout_height="wrap_content" android:layout_width="wrap_content" android:id="@+id/left" android:layout_gravity="left|center" android:background="@drawable/tour_left" android:layout_marginLeft="10dip"/>
        <ImageView android:layout_height="wrap_content" android:layout_width="wrap_content" android:id="@+id/right" android:layout_gravity="right|center" android:background="@drawable/tour_right" android:layout_marginRight="10dip"/>               
Enquirer: Solvek


Solution #1:

The inflate exception is not actually the problem but really comes from another deeper issue in your layout that is then wrapped in an InflateException.
A common issue is an out of memory exception when trying to inflate an ImageView loading a drawable resource. If one of these resources has a high pixel resolution it would take a lot of memory causing then an inflate exception.

So basically verify that the pixel resolution in all your image drawables is just the minimum necessary for your layout.

Respondent: vnportnoy

Solution #2:

This can also happen if you use a VectorDrawable using support library and forgot to use app:srcCompat instead of android:src

Exact error is:
Binary XML file line #XX: Error inflating class ImageView

See that link

Respondent: lujop

Solution #3:

ViewFlipper loads all images into memory during layout inflating. Because my images are big it takes many memory, I replaced ViewFlipper with ImageSwitcher which can change the images with animation like ViewFlipper but it loads only one image at the time.

Respondent: Solvek

Solution #4:

I had the same error when creating custom view with only one constructor, try to define all constructor for your custom views.

   public CustomWebView(Context context) {

    public CustomWebView(Context context, AttributeSet attrs) {
        super(context, attrs);

    public CustomWebView(Context context, AttributeSet attrs, int defStyle) {
        super(context, attrs, defStyle);
Respondent: Wildan Muhlis

Solution #5:

I know the question is already answered but still I’m posting with thought that may someone run into this kind of problem.

In my case problem is i’m loading my application to phone which refer layouts from res/layout/ folder and values for @dimens from res/values/dimens here it’s font_22 which it’s trying to access and it’s define in res/values-xlarge/dimens.

I’m actually updating UI of existing project.

I ran into this problem because I’m using IDE Eclipse where I ctrl+space for hint while writing xml for layout folder it displays all values from values as well as values-xlarge folder regardless of for which folder I’m writing.

I also know that the values in both files should be same to mapped for different screens.

Hope this may help someone run into this kind of silly problem.

Respondent: MobileEvangelist

Solution #6:

I encountered the same bug and found the root reason is:

Use Application Context to inflate view.

Inflating with Activity Context fixed the bug.

Respondent: cox

Solution #7:

I found the same error, and it took two days to identify what the error was.

The error was simply because I was trying to use: android:background

Rather than: app:srcCompat

in an SVG file.

In your case, I believe this is it

    android:src="@drawable/tour_11"      <-- the error is here !

I recommend using it this way

add this to your build.gradle app

android {  
   defaultConfig {  
     vectorDrawables.useSupportLibrary = true  


<androidx.appcompat.widget.AppCompatImageView  <-- use **AppCompatImageView** not **ImageView**

I hope this helps.

Respondent: Williaan Lopes

Solution #8:

I had this error because i selected theme as Material theme. But as i was trying to run app on 4.4.2 it gave this error.

Solution : Select Theme_holo as theme

Solution #9:

My picture size is only 14Kb but the problem is that the designer gave me 1011px x 1819px (resolution too high hence causing the InflateException)

Respondent: Han Heong Ho

Solution #10:

In case someone gets similar issues, I had such an issue while inflating the view:

View.inflate(getApplicationContext(), R.layout.my_layout, null)

fixed by replacing getApplicationContext() with this

Respondent: hedisam

Solution #11:

For me, the error message was actually insufficient in the log cat, so here’s what I did to figure out what caused the problem:

(In the log cat error message, it said the error occurred while inflating a specific layout in my

  1. I put a breakpoint just before the layout was inflated
  2. I ran the application in debug mode until it reached that specific breakpoint
  3. I selected the line with my cursor and ran Evaluate expression on it:
    • Run > Evaluate Expression or alt - F8
  4. The result showed me more information about the source of the problem, which in my case, was a drawable file using tools:targetApi="lollipop" (the bug only occurred on older devices).
Respondent: Julian Honma

Solution #12:

For me, my issue was that I was


To a LinearLayout background, once I removed it the test passed.

Respondent: Val Okafor

Solution #13:

This link may help you. Try checking in your manifest for problems. If you can get it to happen again, post your entire stack trace so that we can see what the error actually is.

EDIT: I’m sure you’ve checked this, but what is on line 12 of the XML file you use for the TourActivity layout?

Respondent: Kevin Coppock

Solution #14:

I know it is an answered question, but I do not see the cause that I faced.

It was that Android Studio placed my drawables in /drawable-V24
My emulator is API 23. So, eventually it can not find it.

The solution was to move all drawables to /drawable folder (no -24).

Respondent: alsaleem

Solution #15:

You should copy the image files from the “drawable-24” folder to the “drawable” folder.

Respondent: Emre Aydemir

Solution #16:

I had the same error and I solved moving my drawables from the folder drawable-mdpi to the folder drawable. Took me some time to realize because in Eclipse everything worked perfectly while in Android Studio I got these ugly runtime errors.

Edit note:
If you are migrating from eclipse to Android Studio and your project is coming from eclipse it may happen, so be careful that in Android Studio things a little differs from eclipse.

Respondent: Mark

Solution #17:

In my case,this error happen when I use the Floating action button and set android:backgroundTint="#000". Then just don’t set backgroundTint and problem solved.
Hope it’s helpful for you.

Respondent: Luan Si Ho

Solution #18:

  • I just solve this issue just delete your images from drawable(v24) and just paste it in drawable folder this works for me.

Respondent: Muzammil

Solution #19:

I had this problem just now and managed to figure out what it was. Was referencing a colour in my values that was causing problems. So defined it manually instead of using one from the dropdown suggestions.Then it worked!

Solution #20:

I had same error when I ran my app on API lvl 16 (26 was fine). It was because I used ?attrr/colorAccent in my shape drawable:

<?xml version="1.0" encoding="utf-8"?>
<shape xmlns:android=""

    <corners android:radius="8dp" />

    <solid android:color="@attr/colorAccent" />


Replacing that with a regular color fixed my problem.

Respondent: Micha? Pow?oka

Solution #21:

i had the same issue and it solved by removing drawable-v24 with (24) in front of images in drawable folder and replacing them with ordinary drawables.

Respondent: ghane nikraftar

Solution #22:

I know this thread is old, but still answering it so that no-one else should spend sleepless nights.

I was refactoring an old project, whose layout files all contained hardcoded
attributes such as android:maxLength = 500. So I decided to register it in my
res/dimen file as <dimen name="max_length">500</dimen>.

Finished refactoring almost 30 layout files with my res-value. Guess what? the next time I ran my project it started throwing the same InflateException.

As a solution, needed to redo my all changes and keep all-those values as same as before.


step 1: All running good.

step 2: To boost my maintenance I replaced android:maxLength = 500 with <dimen name="max_length">500</dimen> and android:maxLength = @dimen/max_length , that’s where it all went wrong(crashing with InflateException).

step 3: All running bad

step 4: Re-do all my work by again replacing android:maxLength = @dimen/max_length with android:maxLength = 500.Everything got fixed.

step 5: All running good.

Respondent: iCantC

Solution #23:

Solved it by moving all my drawable items from drawable-v24 to drawable

Respondent: Eben

Solution #24:

I also faced a similar issue. While for anyone this may be an issue of various bad usages in Code such as

  1. Wrong Layout tag in XML
  2. Loading of heavy resource directly into ImageView resulting in OOM
  3. Issues with usage of styles.

One most ignored factor may be usage of correct Context while inflating views. Please check that you are not using ApplicationContext where an Activity context is required. While, ApplicationContext may not end up in error always, but depending upon your view hierarchy it may be crucial.

I resolved my issue with a BAD context (using ApplicationContext instead of Activity in a span of 4 days! So try if that solves. Happy Coding!!

Respondent: sud007

Solution #25:

I had faced the same issue, I had used view tag in xml instead of View. Replacing to View class fixed the issue.

Hope it helps for you too..

Respondent: Kavya Shravan

Solution #26:

We need to check API Version. I used to give background color to my LinearLayout like


for sure I had the same error, as_royalblue.xml inside drawable folder

<?xml version="1.0" encoding="utf-8"?>
<shape xmlns:android=""
        android:startColor="@color/royalblue_e" />

and how I fixed it, actually it seems Api problem so we need to check the api level if it is above API 24 so we are able to use the way we like. But if it is under 24 we need to avoid usage, juts give a normal color or one color not color gradential mixed one.

fun checkAPI_N(): Boolean {
        if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.N)
            return true
            return false

give id to your linearlayouts and set backgrounds if its ok

        }else {//todo normal color background setting}
Respondent: Sam

Solution #27:

In my case I’ve to specify the complete package name of library UI component that I use in my layout file.

Respondent: christian mini

Solution #28:

For me it happened because I tried to mix xml vector graphics images with ordinary png in the same layout file,

only after I replaced the xml vector graphics with pngs it started to work

Respondent: Daniel

Solution #29:

I had the same error in Crashlytics from a strange device:
Motorola One Vision Android 5.1 and 20 GB (free) RAM, rooted
This device comes originally with Android 9.0, 4 GB RAM

Probably someone is trying to hack the app I’m currently developing and has problems dealing with multi-APKs. So drawables can’t be found and the app delivers the crash

Respondent: GGK

Solution #30:

I had the same error on Kitkat which was because i had android:tint on one of the imageViews. It would work fine on Lollipop but crash on Kikkat with Error Inflating class .

Fixed it by using app:tint on the AppCompatImageView which i was dealing with.

Respondent: onusopus

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Most Popular

To Top
India and Pakistan’s steroid-soaked rhetoric over Kashmir will come back to haunt them both clenbuterol australia bossier man pleads guilty for leadership role in anabolic steriod distribution conspiracy