> Well, I never said I was catching everything indiscriminately. I catch
> things that I can do something about. Sometimes there's a silent fall-back
> and the app doesn't even need to bother the user about it. Sometimes I need
> to involve the user in what to do next. Sometimes I simply tell the user
> that something didn't work. In all those cases, the app doesn't crash, but
> in many of those cases, as a developer I'd like to see what happened; there
> may be an underlying flaw in our code or an unforeseen incompatibility with
> the user's device.
>
That was *exactly *my point - I never catch that kind of exceptions/singals
- if there is a bug in my code chances that app will recover are slim and I
application may end in even worse state, and with framework bugs it's even
worse: in one of my applications I used catch + retry to suppress bugs in
GL, and I ended with code that caused handset hard freeze.
To make it perfectly clear: I simply prefer letting app crash in that
situation, collect report and send it ("remove catch clauses" as you put
it).
That being said, I use ACRA like reporting + custom logging lib (I had a
lot of problem with making log collecting reliable on 4.2) + breakpad
minidump collector (my application has large native part), I'd also suggest
you take a look at crittercism, it's paid service (but has free tier).
--
Bart
--
--
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.
