If you happen to be experienced in development using Visual Studio, but a bit new to working in XCode for iOS development (like me), you are probably used to your application breaking on exceptions during debugging.  But by default, your iOS application may not act as you expect when it comes to debugging crash exceptions.  You may instead see something like this:

With an error message that says: 

*** Terminating app due to uncaught exception

What?  Why was my exception uncaught while I am debugging?  I, for one, would rather be taken to the point at which the exception ...

The Problem

The UISplitViewController is the flagship iPad user interface element, as it allows your application to optimize the use of the large screen.  This control manages 2 views, usually a master view (for navigation) and a detail view (for content).  When in landscape mode, the controller shows both views side-by-side, and when the device is rotated to portrait mode, the master view is hidden and the detail view occupies the full screen.  In this case, the SplitView controller places the master view in a hidden UIPopoverController, and the common MO is to add a button to a toolbar ...