On 1/29/2011 11:36 PM, Felipemnoa wrote: > I've gotten this type of message too unfortunately no way to help them > without acess to the logs.
Isn't it common practice to collect logs from crashes? Or at least stack traces? Wrapping the entire (Java part of the) app in a try/catch and sending that stack trace back to the developer seems like an invaluable feature to include in any app. I've seen the latter done, and have been planning to do something similar with the game I'm working on. As most of my code is C++/NDK code, though, I'm not as sure I'll be able to trap crashes at that level. So I guess I'll just have to be sure there aren't any. :) Tim -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
