On Tuesday, July 30, 2013 9:33:44 AM UTC-7, TreKing wrote: > > > On Mon, Jul 29, 2013 at 7:00 PM, Nathan <[email protected]<javascript:> > > wrote: > >> If I manage to get logs from the users, I might know what exception it >> is. > > > I wouldn't rely on waiting on users to send you anything. Have your app > automatically send you reports using something like ACRA, then flood your > app with log that are also sent in your report until you track the issue > down. >
I agree with that advice. I am finding any failure places and am treating them as a non fatal exception that should be reported in Crashlytics without user intervention. This probably means that it will take more than one update to fix, but that's the breaks. Nathan -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
