On Fri, Jan 6, 2012 at 12:00 PM, Leigh McRae <[email protected]> wrote: > So what would you do?
All I know is that you have identified a pattern of sporadic crashes due to loading resources and assets (and perhaps that NDK library -- not sure what causes that initialization error). And, since you are being relatively calm, I have to assume that the vast majority of your users are not experiencing this sort of problem. The next thing to try to determine is if the problem is tied to specific installs. IOW, if User A has the problem, is User A more likely to have the problem recur? Is it a *given* that the problem will recur? In those cases, perhaps your suggested reinstall would make sense. If, OTOH, you have no evidence to suggest that if User A has the problem that User A is any more likely than User B to have the problem occur in the future, a reinstall is unlikely to help. Generate a UUID per install (tuck it in a file or SharedPreferences) and include it in your crash reports, and see if the same UUIDs keep cropping up. After that, I'd aim for finding commonalities among platforms (OS version, device make/model, etc.), to see if this occurs across the board or is more isolated -- in the latter case, you have a few more options for trying to track down the difficulties or perhaps block out a few devices from your app on the Market (assuming that's how you are distributing it). Also, you can instrument particular cases that you have encountered (e.g., the font) and collect more data (e.g., upload a copy of the font file that failed to load, or run a checksum on it), or retry the operation and see if it succeeds the second time. In fact, for files that should be unchanging, adding checksums as part of a customized build process and reporting any issues when you have an unhandled exception might be worthwhile (e.g., as an adjunct to ACRA or whatever you're using). How much effort you put into this versus other work would be dependent upon the frequency of the errors. At your volume, a dozen or two reports a month wouldn't seem to be worth worrying much about; a dozen or two reports a day might be. A dozen or two reports an hour would have me be significantly less calm. :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: http://marakana.com/training/android/ -- 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
