Why my back button is not working?

I made a pen http://codepen.io/anon/pen/feFpE but the back button is working on this pen… I will check my code again… :confused:

@mhartington Descobri o problema. I found the problem. Maybe is a bug of Ionic or a feature…

Here is the Pen simulating the error http://codepen.io/felquis/pen/CvpDy

In the home.html view, I don’t have the ion-nav-back-button, see that the button is commented

In the post.html view, I have the ion-nav-back-button.

So, to use the ion-nav-back-button all the pages need to have a ion-nav-back-button.

1 Like

Actually you whole code is a bit off.

You have ion-nav-bars in all your ion-view. Instead you initial view should be

<ion-nav-bar class="nav-title-slide-ios7 bar-positive">
  <ion-nav-back-button class="button-icon ion-arrow-left-c">
<ion-nav-view animation="slide-left-right" name="app-view"></ion-nav-view>

Take a look at the docs.

Yeah! I fixed that. Thank you @mhartington

Is there any way to do a nav back button with a header bar and not a nav-bar?

build your own backbutton? and do history.back manually when you click an that button

1 Like

@mhartington I started from the sidemenu example.


  1. How can I replace the burger icon in some screens with a back or cancel button? How about add it in addition to the burger icon?

  2. Do I need to specify where back buttons will be in the menu template itself? (as I see mention of back buttons when inspecting the code)

2.a) How can I set back buttons for pages not directly accessible through the menu system?

  1. How can I fix the problems with the code I’ve tried below:

The example sidemenu index.html contains this:

<body ng-app="myapp">
  <ion-nav-view class="slide-left-right">

In attempt to fix back/nav-bar-buttons from sometimes not working, I’ve updated according to your post, to this:

<body ng-app="boosterapp">
  <ion-nav-bar class="bar-positive">
    <ion-nav-back-button class="button-icon ion-arrow-left-c">
  <ion-nav-view class="slide-left-right">

However, I still don’t always see my back button, in code like this for ba-comments-list.tpl.html which is added like so:

.state('app.photocomments', {
  url: "/photo/:selfieId/comments",
  views: {
    'menuContent': {
      template: "<ba-comments-list></ba-comments-list>"

And the code of the template is like this:

<ion-view hide-back-button="false" title="{{mytitle}}">
  <ion-content class="has-header" style="height:80%;">
      <ion-item ng-repeat="comment in comments">

In this case, the output page contains this:

<ion-nav-back-button class="hide"></ion-nav-back-button>

Where does this class=“hide” come from, and how can I show the back button? Btw, removing this class in the inspector doesn’t make the button show.

Or, in code like this I have for share, I try a cancel button like so:

<ion-view hide-back-button="false" title="Share">
  <ion-nav-buttons side="primary">
    <button class="button" ng-click="cancel()">

In this case, I simply don’t see any mention of the cancel button in the inspector. Actually, I’m not sure how can I search through the entire source code by right clicking somewhere.

  1. How can I do that?

Here is what I have in my ba-menu.tpl.html, which was based on the sidemenu example:

<ion-side-menus enable-menu-with-back-views="false">
    <ion-nav-bar class="bar-stable">
      <ion-nav-buttons side="left">
        <button class="button button-icon button-clear ion-navicon" menu-toggle="left">
    <ion-nav-view name="menuContent"></ion-nav-view>

  <ion-side-menu side="left" class="dark">
    <ion-header-bar class="bar-stable" id="menuHeader">

So I think there is some confusion about the navigation.
So showing/hiding or menu toggles and back buttons have been automated for the most part.

So most of your questions/issues can be resolved by setting up your project correctly.

For the back button not showing sometimes, it may have something to do with the directive you have defined in your startprovider.

Please put a codepen together demoing this.

@mhartington The problem with CodePen is you have to reproduce, in a manner different than you project, for each problem.

Can I share my Ionic View and github/bitbucket somehow? If Ionic could provide that ability, it’d be huge.

Hey @mhartington, my main issue is that the back button is replaced with menu icon where it shouldn’t.

I’m using ionic tabs only at the home page which is one of the menu items, but at the rest menu items I don’t use them.

My goal is to have the back button placed only at “inside” pages (pages that aren’t tabs or menu items), and at the rest of the time the menu icon should appear instead.

I’m working with adaptivedev and you can review some of the code snippet above, and if you need some further info, let me know and I’ll send it to you since it’s kinda difficult to reproduce with CodePen.

So you have tabs and side-menus combined together?
From the look things (checked out the code on bitbucket), seems like what you are describing is an issue with the two ui structures being used together.

You may want to open a new issue and reference this already opened issue.

@mhartington I have an idea about what might be causing problems:

It’d help to know which different transition types causes the menu/back/cancel/header buttons to dis/appear automatically.

  1. $state.go
  2. url redirect link (e…g a href #/app/tabs-page)
  3. Menu navigation (I’m not sure how that works internally)
  4. tabs clicking, and explicit $ionicTabsDelegate.select(i) (which I think works fine)

And, it’d be nice to have manual control over this automatic process for combination of UI components/usage that is bound to come up in real apps beyond core examples.

I looked over the docs for menu/header/buttons but I didn’t spot this information.

Should this be a new ticket? Or maybe it can be answered here?


What the back button is tied to any kind of transition types, but the history of the app in general.

So if there is a view to go back to, a back button will appear.
You can control whether a back button is hidden with ion-views


@mhartington I’m trying to understand your explanation.

But I’m seeing what seems contradictory: For example: why is it that if I switch between 2 menu pages, each of which are views, as shown below, I always see the menu button, and not a back button?

<ion-view hide-back-button="false" title="Profile"> 

Also, how can you control when the menu button will show?

Ie, to have both the back button AND the menu button?

And, how can I control when I’ll (also/instead) have some custom button (like cancel, or a custom ‘back’ button)?

I’ve tried to follow the ion-nav-buttons section in the docs, but maybe that didn’t jive with the side-menu setup?

It’d be great if there were a sample app like sidemenu and tabs that included menu+tabs+ion-nav-buttons. Should that be a feature request or?

So the main issue now I’m seeing is the overall structure of your side-menu…
So you have ion-items and a href="" inside of those, which is causing the issue.

You can just put the links on the ion-items and not use any a tags.

My back button is showing only every other time.

I’ve narrowed down the issue to the back button showing every other time I change from:

choose menu.page1 -> click burger icon -> choose menu.page1 -> click some button, go to -> menu.page2

I removed the tabs and it still does the same behavior, so it’s not the ion-tabs fault.

I placed breakpoints and looked at $ionicHistory.viewHistory() but I’m not sure what to make of the differences.

Here are those differences for the same page, reached in the same way, 2 times in a row, 1 not having a back button, and 1 having it:

Any ideas on what’s wrong here or some suggestions?

i’m having a similar problem.
Header buttons are not showing (not back button, neither secondary buttons).
i built a small codepen: http://codepen.io/anon/pen/bdrRoQ


Your Codepen demonstrates the ‘Back’ button issue:

  • Tap Reggae
  • Tap ‘< Playlists’
  • Tap ‘Nav’ Icon
  • Tap ‘Playlists’
  • Tap Reggae

Playlist has ‘Nav’ Icon, should have ‘< Playlist’ :frowning:

See Issue 4132: https://github.com/driftyco/ionic/issues/4132


1 Like

Thanks for bring this to our attention. Will continue this on the issue page.

1 Like