Should one leave asserts in production iOS apps?

Question

Common practice might be to put asserts in code to check input parameters, data integrity, and such, during app development.

I test my apps, BUT, given that I\'m not K

Answer 1

My NSAssert failures indicate something went horribly wrong and proceeding further would result in undefined behaviour and data corruption. I can't imagine why people parrot disabling them in release builds.

If you can recover from it, you should be using an NSError instead.