title: Prism for Xamarin Forms - Navigating from a tabbedpage
body: <p>(Using Prism 6.1.0-pre6 and XF 2.3.0.107)</p>
  
  <p><strong>Summary</strong>: Navigating to a ContentPage from a TabbedPage doesn't show the toolbar/actionbar.</p>
  
  <p>I navigate to a TabbedPage (MainPage.xaml) from another page.  This looks like this:</p>
  
  <pre><code>&lt;TabbedPage xmlns="http://xamarin.com/schemas/2014/forms"
               xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
               xmlns:local="clr-namespace:Or.Console.Views"
               xmlns:prism="clr-namespace:Prism.Mvvm;assembly=Prism.Forms"
               prism:ViewModelLocator.AutowireViewModel="True"
               x:Class="Or.Console.Views.MainPage"&gt;
    &lt;local:APage/&gt;
    &lt;local:BPage/&gt;
    &lt;local:CPage/&gt;
  &lt;/TabbedPage&gt;
  </code></pre>
  
  <p>And in the ViewModel for APage, I'm calling</p>
  
  <pre><code>_navigationService.NavigateAsync("DetailsPage");
  </code></pre>
  
  <p>The DetailsPage is just a ContentPage, and I would expect that it would show with the back button and action bar at the top, but it doesn't.</p>
  
  <p>I'm guessing this is because Prism doesn't know about the tab child pages, only the TabbedPage itself.</p>
  
  <p>I've tried registering the tab child pages with Prism, but this doesn't seem to work.  Also tried wrapping each tab child in a NavigationPage, but this brings on some strange behavior with duplicate toolbars.</p>
  
  <p>What's the right way to navigate from within tabbed content?</p>
  
  <p><strong>EDIT</strong>:
  In response to Brian Lagunas answer, I tried wrapping the TabbedPage in a NavigationPage, so when I navigate to it, I'm calling </p>
  
  <pre><code> _navigationService.NavigateAsync("DeviceNavWrapper/MainPage");
  </code></pre>
  
  <p>But this gives an odd result:
  <a href="https://i.stack.imgur.com/v0eiC.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/v0eiC.png" alt="enter image description here"></a></p>
  
  <p><strong>EDIT2</strong>: Solution in my case ended up that I needed to call NavigateAsync from APage with the useModalNavigation set to false. So now APage has this:</p>
  
  <pre><code>_navigationService.NavigateAsync("DetailsPage", null, false);
  </code></pre>