I have an App that was working perfectly, then I released an update and now suddenly some users cannot inflate the main view.. it is dying on inflation of the XML on line 28 with a nested exception of
Resources$NotFoundException: File From Drawable resource ID #0X10200004
on line 28 of the Binary XML inflate which references @drawable/pl
the pl.bmp file is in the res/drawable directory and is not corrupted, so the resource exists.
The only thing I can see that seems odd is the R.java file that is generated references this drawable with an id of #0X7F0200009, and there are no files reference id’s that start with #0X1…. at all.. so I am not sure how or why these particular users are even getting that ID as the reference for the drawable. There is an #0X7f0200004 in the R.Java drawable class but it is a completely different graphic.
This is certainly happening with some folks who have upgraded, and I suspect with some folks who have purchased new. I am unable to replicate this behvior on any device I have access to, or on the emulator, but it is clearly happening for some people.
Does anyone have any ideas? Is the upgrade not picking up the right R.java file? How is that even possible? At first I thought it might be a file name collision as earlier releases had p as a bmp and release where this started I changed it to a png, but I made sure to delete pl.bmp before build, and subsequently renamed it to pl, so there is no way even if the old p files both .bmp and .png were somehow on the device it would not possibly collide, but this doesn’t seem to be the problem.
Any help would be greately appreciated.
Thanks in advance.
Well this amazingly appears to be something related to an OS Drawable reference tied to the android.R.id.empty.
Don’t ask me why this worked fine, and then suddenly started not working for some users after I change my XML definition, but I have removed the reference to this and am now using my own transparent graphic instead and everything appears to be working fine.