title: Replacing aborts() for unresolved errors in iPhone/CoreData
body: <p>I have quite a few places in my iPhone application with a line like this:</p>
  
  <pre><code>if (![context save:&amp;error]) {
    /*
    Replace this implementation with code to handle the error appropriately.
  
    abort() causes the application to generate a crash log and terminate. 
    You should not use this function in a shipping application, although 
    it may be useful during development. If it is not possible to recover 
    from the error, display an alert panel that instructs the user to quit 
    the application by pressing the Home button.
    */
  
    NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
    abort();
  }
  </code></pre>
  
  <p>I'm sort of at a loss on what to actually replace abort() with in a production application.  I don't suppose there's any simple way to allow users' devices to send the errors back to you.  What's the standard practice here?</p>