You should catch errors but be very careful about swallowing it and not re-throwing the exception.
I have seen this in certain projects where exceptions are swallowed and the developer of the offending code never even knows that this happened.
So months can go by without any testing, you are doing early testing … right?!… and then one day, you get a bug report that just doesn’t make sense.
So, in my case, where the exception is being eaten up by the host application, I can actually break on objc_exception_throw in GDB, which, by the way, you can also do this using the UI in Xcode to stop on exceptions.
