On Sep 21, 2012, at 5:20 PM, Sean McBride wrote: > The 10.7 release notes say: > > "AppKit now has the ability to report uncaught exceptions. It is controlled > by a user default: NSApplicationShowExceptions (YES/NO)...." > > My next version will require 10.7+, so I'm finally taking a look at this > thing. > > It seems that it only works for the main thread, that is, if there's an > uncaught exception on the main thread I get the nice error UI. But if an > uncaught exception occurs on a non-main-NSThread or dispatch queue I get no > nice UI. > > Can anyone confirm/deny? Anyone shipping with > NSApplicationShowExceptions=YES?
I have no inside knowledge, but I think you've misunderstood the purpose of this default. It's simply to change the behavior where AppKit would silently swallow exceptions which reached the event loop. Of course this only applies to the main thread, because that's the only thread which does that. The new default is described as a tool for developers during development. I wouldn't necessarily argue that it _shouldn't_ be enabled for a release version of your app, but it's not really an end-user feature. If you want to change how uncaught exceptions are handled more generally, you should look into Exception Programming Topics: Controlling a Program’s Response to Exceptions <https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/Exceptions/Tasks/ControllingAppResponse.html> and NSExceptionHandler. Of course, you should first strive to make sure your app doesn't raise exceptions, but no amount of programming care or testing can guarantee that it can never happen in the field. Regards, Ken _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
