Hi Kevin, On Thu, Mar 11, 2010 at 08:30, Kevin Walzer <[email protected]> wrote: > I'm encountering a frustrating customer support issue. > > My apps are all 64-bit, and make heavy use of command-line stuff on OS > X, including osascript and afplay. On Snow Leopard, I get frequent crash > reports from users, and the culprit is invariably some third-party ... > > I have the technical solutions for these all worked out and documented > on my blog, in user forums, and in e-mails I send to users after seeing > crash reports from them: update the osax and other conflicting files, > move them out of the way if you run my app, etc. Still, I keep getting > crash reports.
It'd worry me to ship something that I knew would crash (even through no fault of my own) on common-ish configurations. Is there any way you can trap the error instead of crashing when it happens, and direct the user to these solutions you've already worked out? That would most likely bring user perception up from "buggy/crashy" to "a little fiddly to get it working sometimes," which could well be the difference between no sale and a sale. I'm sure there are more appropriate avenues for the technical discussion, but it doesn't seem like a crash in a child process should take the parent down under normal circumstances. Geoff
