ansaurus

Question

Android: How to track down the origin of a InflateException?

Answer 1

A:

04-09 10:28:17.830: WARN/WindowManager(52): Caused by: android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x2/d=0x1010059 a=-1

That line is the giveaway. The system isn't happy with one of your resources, probably a 'src' resource, probably android:src="@drawable/splash".

Jim Blackler 2010-04-09 08:46:39

I removed the src property and both background properties both without success now the splash screen is empty but the exception is still there.

Janusz 2010-04-09 09:22:36

Eesh. OK, next step, try removing the whole ImageView tag to see if it's something in that tag causing the problem.

Jim Blackler 2010-04-09 09:29:29

Done that too. No help. I think it may another XML file. Like the file defining the styles for the whole app etc but I don't know where to look.

Janusz 2010-04-09 11:30:20

Are you applying a theme to the Activity in AndroidManifest.xml?

Jim Blackler 2010-04-09 12:14:18

Answer 2

A:

The error is on line 24 of your XML file. What does that line contain? By the looks of the error message

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

you're using a custom class and haven't defined something properly. For example, did you define the package name properly? Maybe its constructor isn't formatted? We'd have to see the XML file, specifically what's around line 24, to be able to give more info.

Steve H 2010-04-09 10:45:10

The first screen that is shown after the exception occurs is the splashscreen and this xml file is not 24 lines long. And the binary in front of th XML says me that I won't find anyting at a line 24 in my XML files.

Janusz 2010-04-09 11:29:07

I don't know why it specifies `binary` before saying it's XML file line #24, but that *is* the line with the problem in it. I just introduced a deliberate error in one of my XML files (renamed a custom View to something that didn't exist) and I got a similar exception log to yours. It said `android.view.InflateException: Binary XML file line #90: Error inflating class (mypackage.myclass...)`. So, you need to figure out which XML file it's opening, then look at line 24. For example, do you have another activity beneath your splash screen?

Steve H 2010-04-09 11:58:52

Sorry, I meant to add more detail about my error message. It reported the line with the fault as being #90, and that was the exact line with the problem - I counted it by hand. Then the line number correctly changed as I modified the file and moved things around. So we know that there's a line 24 in one of your files causing trouble, even though the root cause might be somewhere else. If there's another activity visible beneath your splash screen, there might be an error inflating the XML file for that one.

Steve H 2010-04-09 12:23:59

Answer 3

+3 A:

I had the same exact error. The only xml line 24 that made any sense was my application manifest which happened to be the closing tag for application. I traced it down to my custom theme I was adding for the app -- I was not defining the parent of the style. All I needed to do was add parent="android:Theme" to my style and my error went away.

<style name="MyTheme" parent="android:Theme">
...
</style>

Garrett 2010-05-30 04:14:50

You are my hero, exact same issue seems to be solved now. Thanks

Janusz 2010-05-31 06:58:24

ansaurus

tags:

views:

answers:

Android: How to track down the origin of a InflateException?

related questions