Thanks for the feedback. Thankfully the user provided a message "force crash on keyboard input". So maybe he's using a keyboard which does something dodgy to the compose text. The app has over half a million users, and this is the only example of this crash that I know of. So I'm not worried, just curious.
On Friday, 11 May 2012 19:30:11 UTC+8, JTeagle wrote: > > >Subject: [android-developers] Error reports where none of the stacktrace > >elements > >relate to your code? > >For example, in the Developer Console, I got this: > > >Does this indicate a bug in the SDK? > > Unfortunately, not necessarily. Consider a situation where you set some > undesirable data into a View-derived object. At that time it might have > not > checked it and dutifully stored it; when it came to render time, it then > tries to use the data and falls over. At the point where it falls over it > would appear to be entirely within the system - but the worst the SDK > could > be accused of here is not sanity checking the data for possible faults. > > It appears that this came simply from starting your app and it trying to > display the contents of the layout, correct? Does the content of your > layout > have anything unusual in it? (If it's not too long a layout, paste it > here.) > > If it was triggered by some action you took from another activity [that > started the one that failed] or if this activity did show and then this > error triggered from some action you took on this activity, then let us > know. > > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
