My app opens with a set of tabs for searching for ‘events’ by several different methods (location, next, recency). Each tab is more or less a list. Once a user selects an event, they move through a registration process, and the tabs go away since they aren’t relevant once an event has been selected.
This generally works fine, with one small exception: the back button (ion-nav-back-button) in the header. Since each ion-nav-view get’s it’s own history stack, it doesn’t show on the first page of the registration. However, the logic for the hardware back button is simpler and works fine (if there’s a backView, go there!).
Any ideas how to work around this?
Here’s a CodePen to illustrate: