android view InflateException Binary XML file Error inflating class fragment

Question

I have a very frustrating error that I cannot explain  I created an Android application that uses Android AppCompat to make it compatible with older versions  Here is my main activity layout file    lt android support v4 widget DrawerLayout     xmlns android  http   schemas android com apk res android      xmlns tools  http   schemas android com tools      android id    id drawer layout      android layout width  match parent      android layout height  match parent      tools context   MainActivity  gt        lt  -- As the main content view  the view below consumes the entire          space available using match parent in both dimensions  -- gt       lt FrameLayout         android id    id container          android layout width  match parent          android layout height  match parent    gt        lt  -- android layout gravity  start  tells DrawerLayout to treat          this as a sliding drawer on the left side for left-to-right          languages and on the right side for right-to-left languages           If you re not building against API 17 or higher  use          android layout gravity  left  instead  -- gt        lt  -- The drawer is given a fixed width in dp and extends the full height of          the container  -- gt       lt fragment android id    id navigation drawer          android layout width   dimen navigation drawer width          android layout height  match parent          android layout gravity  start          android name  com fragment NavigationDrawerFragment    gt    lt  android support v4 widget DrawerLayout gt    And here is main code of my activity    public class MainActivity extends ActionBarActivity    Override     protected void onCreate Bundle savedInstanceState            super onCreate savedInstanceState           setContentView R layout activity main            The main problem here is   above code run smoothly on almost devices  stimulated device  or some real devices   But when I run it on Samsung S3  It notices this error   java lang RuntimeException  Unable to start activity ComponentInfo view MainActivity   android view InflateException  Binary XML file line  25  Error inflating class fragment             at android app ActivityThread performLaunchActivity ActivityThread java 2081              at android app ActivityThread handleLaunchActivity ActivityThread java 2106              at android app ActivityThread access 700 ActivityThread java 134              at android app ActivityThread H handleMessage ActivityThread java 1217              at android os Handler dispatchMessage Handler java 99              at android os Looper loop Looper java 137              at android app ActivityThread main ActivityThread java 4856              at java lang reflect Method invokeNative Native Method              at java lang reflect Method invoke Method java 511              at com android internal os ZygoteInit MethodAndArgsCaller run ZygoteInit java 1007              at com android internal os ZygoteInit main ZygoteInit java 774              at dalvik system NativeStart main Native Method       Caused by  android view InflateException  Binary XML file line  25  Error inflating class fragment             at android view LayoutInflater createViewFromTag LayoutInflater java 704              at android view LayoutInflater rInflate LayoutInflater java 746              at android view LayoutInflater inflate LayoutInflater java 489              at android view LayoutInflater inflate LayoutInflater java 396              at android view LayoutInflater inflate LayoutInflater java 352              at com android internal policy impl PhoneWindow setContentView PhoneWindow java 316              at android app Activity setContentView Activity java 1901              at android support v7 app ActionBarActivity superSetContentView ActionBarActivity java 208              at android support v7 app ActionBarActivityDelegateICS setContentView ActionBarActivityDelegateICS java 111              at android support v7 app ActionBarActivity setContentView ActionBarActivity java 76    Please tell me how to fix error  thanks

User · Answer

Are android name and class  interchangeable   Presumably  yes  I have only used class  and that seems to be what most of Google s examples use  but I do see where they use android name in some samples  Unfortunately  there is no formal and complete documentation for fragment   use   class    com fragment NavigationDrawerFragment    insted of   android name  com fragment NavigationDrawerFragment    That seemingly means that program looks  class  attribute first  And on fail looks  name  attribute  So as far as it s true using  class  if more efficient

User · Answer

android view InflateException  Binary XML file line  16  Error inflating class com google android material bottomappbar BottomAppBar  The view can be anything that is failing to get inflated  this kind of error comes when there is a clash in resolving the class names or name attribute of a view referred in the XML file  When I get the same error I just got everything clean and safe in UI-XML file  the view I was using      lt com google android material bottomappbar BottomAppBar     android id  quot   id bottomAppBar quot      style  quot  style Widget MaterialComponents BottomAppBar Colored quot      android layout width  quot match parent quot      android layout height  quot wrap content quot      android layout gravity  quot bottom quot      app hideOnScroll  quot true quot      app menu  quot  menu bottom app bar quot      app navigationIcon  quot  drawable ic  menu 24 quot   gt   I was using a style attribute which was referring the Material components property  But my styles xml had     lt style name  quot AppTheme quot  parent  quot Theme AppCompat Light NoActionBar quot  gt        lt  style gt   Where the class resolving was facing the conflict  My view attributes referred a property that was not defined in my app theme  The right parent theme from material components helped me  So I changed the parent attribute to     lt style name  quot AppTheme quot  parent  quot Theme MaterialComponents Light NoActionBar quot  gt       lt  style gt   Which resolved the issue

User · Answer

I think the basic problem is with  android targetSdkVersion  which is defined in AndroidManifest xml  In my case  the initial value which I have defined as   android targetSdkVersion 16   I changed it to   android targetSdkVersion 22   which resolved my all of the error  So  setting up the correct  targetSdkVersion  is also important before building an android app

User · Answer

I also had this issue  I solved it by replacing the import in MainActivity and NavigationDrawerFragment  From  import android app Activity  import android app ActionBar    To  import android support v7 app ActionBar  import android support v7 app ActionBarActivity    I updated MainActivity to extends ActionBarActivity instead of Activity  public class MainActivity extends ActionBarActivity implements NavigationDrawerFragment NavigationDrawerCallbacks   Also use ActionBar actionBar   getSupportActionBar    to get the ActionBar  And I updated the following function in NavigationDrawerFragment  private ActionBar getActionBar         return   ActionBarActivity getActivity    getSupportActionBar

User · Answer

I have the same problem because I did not implement the listener  See the following code with   Add This       public class SomeActivity extends AppCompatActivity         implements BlankFragment OnFragmentInteractionListener   Add this            Override                                                    Add This        public void onFragmentInteraction Uri uri                    Add This                                                                     Add This        FYI  my fragment class is something like the following    public class SomeFragment extends Fragment        private OnFragmentInteractionListener mListener        Override     public void onAttach Activity activity            super onAttach activity           try               mListener    OnFragmentInteractionListener  activity            catch  ClassCastException e                throw new ClassCastException activity toString                           must implement OnFragmentInteractionListener                         public interface OnFragmentInteractionListener           public void onFragmentInteraction Uri uri               Edit    I also notice this same error message under another circumstances when there is an exception in the onCreate function of the Fragment  I have something as the following    Override public View onCreateView LayoutInflater inflater  ViewGroup container                           Bundle savedInstanceState        View rootView   inflater inflate R layout fragment main  container  false        int ID   getArguments   getInt  val         return rootView       Because I reuse this fragment  I total forget to set arguments  Then the result of getArguments   is null  Obviously  I get a null pointer exception here  I will suggest you keep an eye on mistakes like this as well

User · Answer

After long time of tries  this is how I solved the problem after none of the above answers could    Extend AppCompatActivity for your Main activity instead of Activity  Add android theme   style Theme AppCompat Light  to your  lt Activity      gt  in the AndroidManifest xml In your NavigationDrawerFragment Class  change your ActionBar instances to  ActionBar mActionBar   AppCompatActivity getActivity    getSupportActionBar       EDIT  It should be a consistency between the Activity and Layout  If the Layout has one of the AppCompat Theme such like Theme AppCompat Light  your Activity should extends AppCompatActivity   I wanted to have the burger icon and a Navigation Drawer that looks like the Android Gmail App  but I ended up with an ugly Navigation Drawer  All that because all my Classes extends Activity instead of AppCompatActivity   I re-factored the entire project to extend AppCompatActivity  then Right-Click on the Layout Folder  chose new -  Activity then Navigation Drawer Activity and Boom  everything is done for me

User · Answer

It might not be needed for you anymore  but if further readers find it helpful  I have exact same android view InflateException    Error inflating class fragment  I had all right libraries included  Solved by adding one more user permission in the AndroidManifest xml file i e   lt uses-permission android name  android permission ACCESS NETWORK STATE   gt       Btw I was running Android Studio 0 8 9 on Ubuntu 12 04

User · Answer

I don t know if this will help   I had this problem with a TextView I had in the layout I was trying to inflate  android view InflateException  Binary XML file line  45  Error inflating class TextView    I had set the following XML attribute android textSize   android attr textAppearanceLarge  which wasn t allowing for the layout to be inflated   Don t know exactly why   I m still a bit new to Android - less than a year of experience   might have something to do with calling system attributes  idk  all I know is as soon as I used plain old  dimen md text 16sp  which is a custom of mine   problem solved     Hope this helps

User · Answer

Add this name field in navigation          android name  androidx navigation fragment NavHostFragment        lt fragment              android id    id container               android layout width  match parent               android layout height  0dp               android name  androidx navigation fragment NavHostFragment               app navGraph   navigation navigation               app layout constraintBottom toTopOf    id bottomNavigationView               app layout constraintTop toTopOf  parent  gt

User · Answer

FWIW  I was getting   Android Views InflateException   Message Binary XML file line  1  Binary XML file line  1  Error inflating class android view TextureView   I am new to android form design  In trying to put a border on some buttons I found an SO post that inspired me to create buttonborder xml that looks like    lt shape xmlns android  http   schemas android com apk res android  android shape  rectangle   gt   lt solid android color   android color transparent    gt   lt stroke android width  1dp  android color   android color white   gt      Then for each button I added  android background   drawable buttonborder    However  in my enthusiasm I also added it to a TextureView - which was my problem  When I removed the line from the TextureView  things worked

User · Answer

I couldn t solve my problem using provided answers  Finally I changed this    lt fragment android id    id fragment food image gallery  android name  ir smartrestaurant ui fragment ImageGalleryFragment  android layout width  match parent  android layout height  200dp  android layout   layout fragment image gallery  tools layout   layout fragment image gallery    gt    to this     lt FrameLayout android id    id fragment container  android layout width  match parent  android layout height  200dp    gt       private void showGallery         ImageGalleryFragment fragment   new ImageGalleryFragment       getSupportFragmentManager   beginTransaction                    replace R id fragment container  fragment                   commit            and it works  If you are using it inside fragment  use getChildFragmentManager instead of getSupportFragmentManager

User · Answer

As mentioned in a previous post  rename  android name  com fragment NavigationDrawerFragment    to  class    com fragment NavigationDrawerFragment    Still  it did not work for me  I then just used the Class Name without the com fragment part and voila it worked  So change it finally to   class    NavigationDrawerFragment

User · Answer

we must also need to add following in build gradle app   compile  com android support appcompat-v7 23 1 1  compile  com android support design 23 1 1    whenever we are using new layouts or new design features  hope this helps you

User · Answer

I had the same problem  issue  tried all the answers in this thread to no avail  My solution was  I hadn t added an ID in the Activity XML  I didn t think it would matter  but it did    So in the Activity XML I had    lt fragment     android name  com covle hellocarson SomeFragment      android layout width  wrap content      android layout height  wrap content   gt    But should ve had    lt fragment     android id    id some fragment      android name  com covle hellocarson SomeFragment      android layout width  wrap content      android layout height  wrap content   gt    If someone would be happy to comment on why this is  I m all ears  to other  I hope this helps

User · Answer

This exception may occurs when the activity which manages your fragments was stoped and you try to open it again  so in this case the NavHostFragment will be not reconized by activity which has losing the state  To fix it try to finish the cycle life of your activity in order to reload the NavHostFragment by the FrgamentManager again   Inside your Activity where you manage your fragments put the below     Override protected void onStop         super onStop        this finishActivity 0

User · Answer

For some of you that still haven t found a solution for this  in my case it was happening because I had an OOM  Out of Memory  issue  This can happen when you have for example a memory leak in your app when using it for a long time  In my stack trace  this was the main reason

User · Answer

I was having the same problem  in my case the package name was wrong  fixing it solved the problem

User · Answer

I had this on a 4 4 2 device  but 5  was fine   The cause  inside a custom view s initialisation  I was creating a TextView Context context  AttributeSet attrs   AttrRes int defStyleAttr   StyleRes int defStyleRes   which is API 21    Android Studio 2 1 doesn t complain about it even though it is annotated TargetApi 21    Apparently  Android Studio 2 2 will correct this and properly show it as an error   Hope this helps someone

User · Answer

Just in case someone needs this  Assumptions  Device phone hooked up to USB cable and your IDE reading to launch the app   Go to the command prompt to determine issue  enter adb logcat  Then launch your app from IDE  You will an exception    In my case  I was deploying an Android app of Version 2 3 to a mobile device  that did not support the widget   Space

User · Answer

I have had similar problems on and off   The error message often provides very little detail  regardless of actual cause   But I found a way to get more useful info   It turns out that the internal android class  LayoutInflater java   in android view package  has an  inflate  method that re-throws an exception  but does not pick up the details  so you lose info on the cause   I used AndroidStudio  and set a breakpoint at LayoutInflator line 539  in the version I m working in   which is the first line of the catch block for a generic exception in that  inflate  method             catch  Exception e                InflateException ex   new InflateException                      parser getPositionDescription                                        e getMessage                 ex initCause e               throw ex    If you look at  e  in the debugger  you will see a  cause  field   It can be very helpful in giving you a hint about what really occurred   This is how  for example  I found that the parent of an included fragment must have an id  even if not used in your code   Or that a TextView had an issue with a dimension

User · Answer

After none of the answers here helped me  I opted to run app in debug mode moving across every line of onCreateView in my fragment  NavigationDrawerFragment in your case   And noticed that fragment was having difficulty with inflating because of a NullPointerException  E g   mySeekBar    SeekBar  getActivity   findViewById R id mySeekBar   mySeekBar setOnSeekBarChangeListener this     Here mySeekBar was set to null  because I had missed adding the control in appropriate layout  and the next line got into NPE which came out as InflateException   Also  as suggested above  rename android name to class   This issue can arise for various reasons mentioned above  I would recommend  line-by-line debug flow to know what is wrong

User · Answer

I had this error too  and after very long debugging the problem seamed to be that my MainClass extended Activity instead of FrameActivity  in my case  the xml wasn t a problem  Hope to help you

User · Answer

Check Proguard  I had this error combined with a ClassNotFoundException for one of my classes  and ended up simply needing to check my proguard-rules pro   That file is found under the app directory in your YourAppName directory   I needed to append the following two lines   -keep class com gbros tabslite data           -keepattributes Exceptions  Signature  InnerClasses    Where tabslite is my app name  and the file I was getting a ClassNotFoundException was in the data folder

User · Answer

This problem arises when you have a custom class that extends a different class  in this case a view  and does not import all the constructors required by the class  For eg   public class CustomTextView extends TextView   This class would have 4 constructors and if you miss out on any one it would crash  For the matter of fact I missed out the last one which was used by Lollipop added that constructor and worked fine

User · Answer

In my particular case the problem was I added this line to a TextView    android background   attr selectableItemBackground    After removing this  everything started to work fine

User · Answer

After long time for debugging  I have fixed this problem   Although I still cannot explain why   That I change property android name to class   although on Android Document  they say those properties are same  but it works       So  it should change from     android name  com fragment NavigationDrawerFragment    to   class    com fragment NavigationDrawerFragment    So  new layout should be       lt  -- As the main content view  the view below consumes the entire      space available using match parent in both dimensions  -- gt   lt FrameLayout     android id    id container      android layout width  match parent      android layout height  match parent    gt    lt  -- android layout gravity  start  tells DrawerLayout to treat      this as a sliding drawer on the left side for left-to-right      languages and on the right side for right-to-left languages       If you re not building against API 17 or higher  use      android layout gravity  left  instead  -- gt    lt  -- The drawer is given a fixed width in dp and extends the full height of      the container  -- gt   lt fragment android id    id navigation drawer      android layout width   dimen navigation drawer width      android layout height  match parent      android layout gravity  start      class    com fragment NavigationDrawerFragment    gt      Hope this help

User · Answer

My error was caused by a different problem   I was passing a bundle from an Activity to its fragment  When I commented the code receiving the bundle in the fragment the error was gone  As it turns out  my error was due to the below  getArguments     part which was returning null   Bundle args   getArguments      Upon checking the Activity sending code  I realized I had a silly mistake in the below    Bundle bundle  new Bundle     bundle putInt  recipeID   recipe position    Fragment mainFragment   new MainActivityFragment     mainFragment setArguments bundle    FragmentManager fragmentManager   getSupportFragmentManager     -- gt  fragmentManager beginTransaction                            replace R id container  new  MainActivityFragment                                    DetailRecipeActivityFragment TAG                           commit      I was creating a NEW fragment in the line with the arrow  Whereas I should have used the pre-instantiated fragment that already had my bundle  So it should have been    Bundle bundle  new Bundle     bundle putInt  recipeID   recipe position    Fragment mainFragment   new MainActivityFragment     mainFragment setArguments bundle    Fragment mainFragment   new MainActivityFragment     FragmentManager fragmentManager   getSupportFragmentManager     -- gt fragmentManager beginTransaction                            replace R id container  mainFragment                                  DetailRecipeActivityFragment TAG                           commit      I don t know why exactly it throws this error instead of an NPE  but this solved my error in case someone is having the same scenario

User · Answer

Is your NavigationDrawerFragment extending the android support v4 app Fragment  In other words  are you importing the correct package   import android support v4 app Fragment

User · Answer

TL DR  An exception occurred during the creation of a fragment referenced from a higher-level layout XML  This exception caused the higher-level layout inflation to fail  but the initial exception was not reported  only the higher-level inflation failure shows up in the stack trace  To find the root cause  you have to catch and log the initial exception     The initial cause of the error could be a wide variety of things  which is why there are so many different answers here as to what fixed the problem for each person  For some  it had to do with the id  class  or name attributes  For others it was due to a permissions issue or a build setting  For me  those didn t fix the problem  instead there was a drawable resource that existed only in drawable-ldrtl-xhdpi  instead of in an applicable place like drawable   But those are just details  The big-picture problem is that the error message that shows up in logcat doesn t describe the exception that started it all  When a higher-level layout XML references a fragment  the fragment s onCreateView   is called  When an exception occurs in a fragment s onCreateView    for example while inflating the fragment s layout XML   it causes the inflation of the higher-level layout XML to fail  This higher-level inflation failure is what gets reported as an exception in the error logs  But the initial exception doesn t seem to travel up the chain well enough to be reported   Given that situation  the question is how to expose the initial exception  when it doesn t show up in the error log   The solution is pretty straightforward  Put a try catch block around the contents of the fragment s onCreateView    and in the catch clause  log the exception   public View onCreateView LayoutInflater inflater  ViewGroup contnr  Bundle savedInstSt        try           mContentView   inflater inflate R layout device detail frag  null                  rest of body of onCreateView             catch  Exception e            Log e TAG   onCreateView   e           throw e            It may not be obvious which fragment class s onCreateView   to do this to  in which case  do it to each fragment class that s used in the layout that caused the problem  For example  in the OP s case  the app s code where the exception occurred was  at android app Activity setContentView Activity java 1901    which is     setContentView R layout activity main     So you need to catch exceptions in the onCreateView   of any fragments referenced in layout activity main    In my case  the root cause exception turned out to be  Caused by  android content res Resources NotFoundException  Resource     com example myapp drawable details view   7f02006f   is not a    Drawable  color or path   TypedValue t 0x1 d 0x7f02006f a -1    r 0x7f02006f    This exception didn t show up in the error log until I caught it in onCreateView   and logged it explicitly  Once it was logged  the problem was easy enough to diagnose and fix  details view xml existed only under the ldrtl-xhdpi folder  for some reason   The key was catching the exception that was the root of the problem  and exposing it   It doesn t hurt to do this as a boilerplate in all your fragments  onCreateView   methods  If there is an uncaught exception in there  it will crash the activity regardless  The only difference is that if you catch and log the exception in onCreateView    you won t be in the dark as to why it happened   P S  I just realized this answer is related to  DaveHubbard s  but uses a different approach for finding the root cause  logging vs  debugger

User · Answer

This error is really confusing  In my case I was missing a default empty parameter less constructor for my fragment  After adding empty constructor in my fragment the problem resolved

User · Answer

i faced this problem and solved it by using following codes  I was beginning fragment transaction by using childfragment manager   layout                      lt fragment                     class  com google android youtube player YouTubePlayerSupportFragment                      android id    id youtube fragment                      android layout width  match parent                      android layout height  wrap content   gt    this is how i began fragment transaction      youTubePlayerFragment    YouTubePlayerSupportFragment  getChildFragmentManager   findFragmentById R id youtube fragment     the following codes explains how i removed the fragment which added by using childfragmentmanger    Override     public void onDestroyView             super onDestroyView             youTubePlayerFragment    YouTubePlayerSupportFragment  getChildFragmentManager   findFragmentById R id youtube fragment            if  youTubePlayerFragment    null                        getChildFragmentManager   beginTransaction   remove youTubePlayerFragment  commitAllowingStateLoss                       youTubePlayer   null

User · Answer

Open the gradle properties and add the following line   android enableAapt2 false   Reference  https   github com chrisjenx Calligraphy issues 417 issuecomment-365177808

User · Answer

I had this error when I had my RecyclerView at the root of my fragment xml   but when I wrapped it with a ViewGroup  the app worked fine

User · Answer

I am a bit late to the party but Non of these answer helped me in my case  I was using Google map as SupportMapFragment and PlaceAutocompleteFragment both in my fragment  As all the answers pointed to the fact that the problem is with SupportMapFragment being the map to be recreated and redrawn   But I also had problem with PlaceAutocompleteFragment  So here is the working solution for those who are facing this problem because of SupportMapFragment and SupportMapFragment   mapFragment    SupportMapFragment  getChildFragmentManager   findFragmentById R id mapFragment       FragmentManager fm   getChildFragmentManager         if  mapFragment    null            mapFragment   SupportMapFragment newInstance            fm beginTransaction   replace R id mapFragment  mapFragment  commit            fm executePendingTransactions               mapFragment getMapAsync this          Global PlaceAutocompleteFragment autocompleteFragment        if  autocompleteFragment    null            autocompleteFragment    PlaceAutocompleteFragment  getActivity   getFragmentManager   findFragmentById R id place autoCompleteFragment            And in onDestroyView clear the SupportMapFragment and SupportMapFragment   Override public void onDestroyView         super onDestroyView          if  getActivity      null            Log e  res   place dlted            android app FragmentManager fragmentManager   getActivity   getFragmentManager            android app FragmentTransaction fragmentTransaction   fragmentManager beginTransaction            fragmentTransaction remove autocompleteFragment           fragmentTransaction commit             autocompleteFragment   null

User · Answer

In my case     The layout i was trying to inflate had    lt include   layout             gt    tag  removing it fixed it   I was trying to inflate a previous layout designed for a Actvity into the view-pager adapter

User · Answer

In case someone else comes here and the answers do not help solve the problem  one more thing to try   As others have mentioned  this usually is caused by an issue nested in the XML itself as opposed to something you did wrong in your Java  In my case  it was a super easy  and stupid  mistake to fix    I had code like this    lt view     android layout width  fill parent      android layout height  1dip      android id    id view44      android background   color gray        gt    When all I had to do was capitalize the v in  View  so that the system recogized it  Check that your custom views  Or Fragments  recyclerviews  etc  all have the proper capitalized declaration up front so that the XML auto-complete will match it to the appropriate view

[android] android.view.InflateException: Binary XML file: Error inflating class fragment

Examples related to android