Android logcat - "Resources don't contain package for resource number 0xHHHHHHHH"

In testing an app with Robotium (this is an awesome tool), I noticed the following messages in logcat when things were deployed from eclipse


W/ResourceType( 52): Resources don't contain package for resource number 0x7f0700e5
W/ResourceType( 52): Resources don't contain package for resource number 0x7f020031
W/ResourceType( 52): Resources don't contain package for resource number 0x7f020030
W/ResourceType( 52): Resources don't contain package for resource number 0x7f050000
W/ResourceType( 52): Resources don't contain package for resource number 0x7f060000
W/ResourceType( 52): Resources don't contain package for resource number 0x7f060001
D/dalvikvm( 98): GC freed 4323 objects / 249512 bytes in 291ms
W/ResourceType( 52): Resources don't contain package for resource number 0x7f0700e5
W/ResourceType( 52): Resources don't contain package for resource number 0x7f020031
W/ResourceType( 52): Resources don't contain package for resource number 0x7f020030
W/ResourceType( 52): Resources don't contain package for resource number 0x7f050000
W/ResourceType( 52): Resources don't contain package for resource number 0x7f060000


The app and tests work as expected.

Because I am using images and layouts specific to different resolutions/screen-sizes, I am a little concerned that this message indicates a potential problem with something being missing for one of the cases. My understanding is that the Android framework should be able to substitute a resource if it has to, using the hdpi image for the ldpi case, for example.  This would mean that the only way something is missing is if the resource doesn't actually exist in any of the scenarios.  Of course, eclipse should find this... or at leas the build process should catch it.

Based on some quick googling, I think this is likely an innocuous warning.  Well, the message itself is reported as a warning!

No comments:

Post a Comment

Popular Posts