• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSApplicationShowExceptions - useful on main thread only?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSApplicationShowExceptions - useful on main thread only?


  • Subject: Re: NSApplicationShowExceptions - useful on main thread only?
  • From: Keith Duncan <email@hidden>
  • Date: Tue, 25 Sep 2012 09:44:30 +0100

We use NSApplicationCrashOnExceptions which avoids the silent logging and the interface, and just plain crashes, akin to the iOS approach to exceptions.

When we turned this on in one of our products we found (and fixed) four unreported issues by merit of the crash reports it generated.

Cheers,
Keith

On 25 Sep 2012, at 01:03, Sean McBride <email@hidden> wrote:

> On Sat, 22 Sep 2012 00:38:36 -0500, Ken Thomases said:
>
>> I have no inside knowledge, but I think you've misunderstood the purpose
>> of this default.
>
> I guess I have.  Thanks Ken & Corbin for straightening me out. :)
>
>> 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.
>
> Yes, I agree with and am aware of all that.  I currently use FeedbackReporter:
> <https://github.com/tcurdt/feedbackreporter>
>
> to handle the (mostly rare) exceptions that make it to the user.  I was thinking that NSApplicationShowExceptions was maybe meant to replace such things.
>
> FeebackReporter works mostly well but I'm unsure of the correct way to handle uncaught exceptions on non-main threads/queues.  It seems to always result in the app being killed no matter what I do.
>
> Cheers,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 email@hidden
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


References: 
 >NSApplicationShowExceptions - useful on main thread only? (From: Sean McBride <email@hidden>)
 >Re: NSApplicationShowExceptions - useful on main thread only? (From: Ken Thomases <email@hidden>)
 >Re: NSApplicationShowExceptions - useful on main thread only? (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: NSApplicationShowExceptions - useful on main thread only?
  • Next by Date: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?
  • Previous by thread: Re: NSApplicationShowExceptions - useful on main thread only?
  • Next by thread: NSSearchField(Cell) changes size with typing
  • Index(es):
    • Date
    • Thread