title: iMessage Extensions: Root Navigation Controller results in all delegate methods to not get called in my MSMessagesAppViewController
body: <p>I have a new iMessage Extension project where I tried 2 ways of structuring the navigation stack:</p>
  
  <ol>
  <li><p>In my storyboard I set the entry point to a UINavigationController that has my MSMessagesAppViewController as the root controller. </p></li>
  <li><p>Or I set my MSMessagesAppViewController directly as the Entry point in my storyboard.  (No UINavigationController that owns it). </p></li>
  </ol>
  
  <p>For scenario #1 above, the navigation controller works fine, and I can push new screens on the stack. (with the exception of the whole nav bar being hidden in Expanded view, which is a separate issue that I still have to figure out).   However, NONE of the delegate methods of my MSMessagesAppViewController get called with this configuration. Such as:
  willTransitionToPresentationStyle
  didTransitionToPresentationStyle,
  willBecomeActiveWithConversation,
  didSelectMessage
  (none of these get called)</p>
  
  <p>For scenario #2 above, the MSMessagesAppViewController methods DO get called.  (because the UINavigationController is not the entry point in the Storyboard). </p>
  
  <p>So my question is:  How can I have a UINavigationController be at the root of my iMessage Extension application, so I can perform Push navigation, but at the same time have the methods of MSMessagesAppViewController get called, as described by the Apple API?  </p>