title: Should one leave asserts in production iOS apps?
body: <p>Common practice might be to put asserts in code to check input parameters, data integrity, and such, during app development.</p>
  <p>I test my apps, BUT, given that I'm not Knuth (and <strong>he</strong> writes $1 checks), and I can't afford to employ a large team of full-time QA people as do some medical and space systems software companies, I assume that all my apps will always have plenty of bugs that have never yet been seen during testing or QA.  Assuming otherwise seems quite intellectually dishonest.  So after testing an app (and obviously removing all bugs causing any previously seen ASSERT failures) and getting the app ready to ship to Apple, what should be done with all the ASSERT checks in the Release/Distribution build?  Leave or no-op?</p>
  <p>Here's one rationale for leaving them in:  If an app acts wonky for some users, the app might get rated by those users as 1-Star without anyone ever telling the developer why in sufficient detail.  But if the app crashes from an ASSERT failure, the app might still get rated 1-Star, but the developer could potentially get some crash dumps, indirectly via iTunes and iTunes Connect if enough users opts in, to figure out what is going wrong.  And if the app gets rejected by Apple due to a brand new ASSERT crash, that will prevent a bad version of the app from ever getting onto one's customer's devices.</p>