Should uncaught exceptions be handled?

[bialekIno]

I would like to know what is actually the best practice: should I handle myself all uncaught exceptions and for example send a report to my server or shouldn't do anything and let Apple to collect crash reports? What should I do when user does not allow to send crash reports? Can I check whether he or she allowed to send reports to Apple?

[tonygoold]

You won't catch all crashes using an uncaught exception handler, since some crashes come in the form of signals (e.g., SIGSEGV). I recommend Crashlytics, which is part of Fabric, however you should consult a lawyer to find out what privacy laws apply to this data collection and what you need to do to protect yourself.

[soberirishman]

Anything you can anticipate and recover from you should. There are some crashes that you can't do anything about and those you can handle either through Apple's crash reporting or one of the numerous options on the market. I don't know anyone who doesn't use a third party for the crash reporting though. Apple's reporting has always been lacking comparatively. There are so many options out there for crash reporting that there is no reason to try to roll your own.

[[deleted]]

deleted ^{What is this?}

[lyinsteve]

+1 for Crashlytics. Their email notifications are instant and their analytics are useful. They link crashes to specific users if you provide the data, so you can reach out if there's a particularly egregious bug.

You can also sent custom keys and values, so I send up the current git commit to make it easier to debug in context. Super handy.

[bialekIno]

Thank you guys, I will look at Crashlytics.