Using a Side Menu on Tabs


Hey everyone, first post here so I’ll try to follow the format I have been seeing around the site.

The issue is that when I build and load the app onto my phone (iPhone 6+), the ion-buttons on the menu recognize the click event, but will only set the page as root if the page is already root. Push similarly doesn’t do anything. It seems like there have been a couple of people confused by this without any solution. Is there anyone who can weigh in?



<ion-menu [content]="content" side="right" type="overlay">
    <ion-toolbar [color]="'primary'">
      <ion-item (click)="openAccountPage()">
        <ion-icon name="contact" item-start></ion-icon>
      <button ion-item (click)="openContactPage()">
        <ion-icon name="call" item-start></ion-icon>
				Contact Information (Swap)
      <ion-item menuClose detail-none>
				<ion-icon name="exit" item-start></ion-icon>
				Close Menu
      <button ion-item *ngFor="let p of pages" (click)="openPage(p)">

<ion-nav #content [root]="rootPage"></ion-nav>


import { Component, ViewChild } from '@angular/core';
import { NavController } from 'ionic-angular';

import { Platform } from 'ionic-angular';
import { MenuController } from 'ionic-angular';

import { AlertController } from 'ionic-angular'; //for dev testing;

import { TabsPage } from '../pages/tabs/tabs';
import { LoginPage } from '../pages/login/login';
import { ContactPage } from '../pages/contact/contact';
import { AccountPage } from '../pages/account/account';

  templateUrl: 'app.html'

export class MyApp {
	@ViewChild('content') nav: NavController;
	title: any;
	pages: Array<{title: string, component: any}>;

  constructor(public platform: Platform, private alertCtrl: AlertController) {
    this.pages = [
      { title: '', component: TabsPage },
      { title: 'Contact', component: ContactPage },
      { title: 'Account', component: AccountPage }
		platform.ready().then(() => {
			/* GLOBAL AUTH EVENTS */'authentication:successful', () => {'init:begin');
			});'authentication:failure', (e) => {
				this.presentAlert("Auth Failed", e);
				this.rootPage = LoginPage;
  openPage(page) {
    // Reset the content nav to have just this page
    // we wouldn't want the back button to show in this scenario
		let alert = this.alertCtrl.create({
			title: "ContactPage",
			subTitle: "Should be displayed after this.",
			buttons: ['Dismiss']
		let alert = this.alertCtrl.create({
			title: "AccountPage",
			subTitle: "Should be displayed after this.",
			buttons: ['Dismiss']


Hi @raytri have you already looked at the sidemenu-tabs starter? Because I think that’s a good starting point for an app containing both sidemenu and tabs.


Thanks @luukschoen, and yes, I have. That is what I followed when I was writing out mine.

Here was the one I looked at:

This issue is not that it doesn’t work period, because I can get both push and setRoot to work in my browser via ionic serve without any problems, in fact 7 or 8 different ways. However, when it comes to actually building the app and installing it on my iPhone for more thorough testing, the navigation functions triggered by those menu elements stop working.


Okay that’s one very old repo which isn’t the one provided by the Ionic Team so probably not your best bet. Take a look at the ionic conference app over here:

clone the repo and test it out on your device :slight_smile:


@luukschoen I’ve done this and it does work on my device, however I should have been more specific in the behavior I am looking for.

Actually this response was preemptive. I didn’t see the functionality as I had described but now I do. I will be studying this thanks!


You’re referring to some other posts as well, can you reference them here by any chance? I would like to comprehend the context of your issue a little bit better. Maybe we can help those people too :wink:


Sure! Here was the other post I saw just a few hours ago who seemed to have a similar problem.


I figured out what the problem actually was, it had to do with the pages in question erroring out. On the iphone they were attempting to construct themselves using data from providers before the providers were properly loading their own data. I was able to catch the errors on iphone using:

		this.nav.setRoot(page.component).catch((err: any) => {
			let alert = this.alertCtrl.create({
				title: "Nav Error",
				subTitle: "There was a navigation error: "+err,
				buttons: ['Dismiss']

This led me to the end page where the problem actually was.