"and one trying to fetch a custom .9.png that I had put into my own app" I see a fair few crash dumps similar to this.
I suspect that the user has (e.g.) rotated the phone and at that split moment, the activity is being dropped and restarted by android. But things running in other threads may still linger and if they try to access app resources, the context may respond with "resource not found" while it is temporarily in a limbo state. I think there are other scenarios that could also cause this - maybe a user exiting an app while a thread is still running and again the resources are no longer retrievable but a running thread tries to access them before it is shut down by android. I can't think of any other way how a user can suddenly get a missing resource when I can clearly see in the code that the user must have retrieved that very resource successfully earlier in the app without a problem. I don't have proof on this, just my own wild'n'wacky ideas! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
