I haven't yet tried any of his suggestions, and since the article is from 2009, I don't know how much has changed.
In any case, from experience on other platforms, I heartily recommend making crash reporting straightforward (1-click, or even opt-in to 0-click) for users. Once you have a few hundred people using your software, "rare" crashes happen all the time and tracking them down can be much easier than with just your internal testing.
Note that OSX's built-in crash reports go to Apple, not the App developer, so they're not much use to those of us outside the Cupertino ivory tower.
http://www.red-sweater.com/blog/860/crash-reporter-roundup
I haven't yet tried any of his suggestions, and since the article is from 2009, I don't know how much has changed.
In any case, from experience on other platforms, I heartily recommend making crash reporting straightforward (1-click, or even opt-in to 0-click) for users. Once you have a few hundred people using your software, "rare" crashes happen all the time and tracking them down can be much easier than with just your internal testing.
Note that OSX's built-in crash reports go to Apple, not the App developer, so they're not much use to those of us outside the Cupertino ivory tower.