Yeah, I’m having a similar problem. I have a detail page that is the root of a nav stack. You can open a modal and press the Edit button therein to get to the edit page, or you might end up on the edit page directly by deep-linking in. So you’re on the edit page, but the nav stack may look like either:
[item-detail] - [modal] - [item-edit]
So, upon item publication, I want to go back to item-detail, preferably with the modal closed. If I clicked in to the page, what I need to do is pop twice. If I deep-linked, I need to do a set-root.
if I clicked in and set-root out, the menu button stops working. Investigating the DOM tree leads me to believe it’s some kind of weird rendering bug - the ion-menu actually shows up, gets it’s translateX property set properly, as does the main content (I’m using push, but changing it to some other animation doesn’t help), but the menu doesn’t render in the view. Mousing over the view element highlights the right place for both the menu and pushed-over main content, but the rendered window doesn’t match the highlights when selecting elements in the DOM tree.
if I clicked in and pop once or twice everything is fine.
if i deeplinked in and set-root out everything works fine.
if I deeplinked in and pop once or twice the whole thing collapses as I don’t have a root to go to.
This seems to be a path-dependent bug, therefore. I can work around it by capturing all calls to navCtrl, investigating the current state of navCtrl, and either popping or set-rooting to actually do the navigation, but this is a pretty atrocious thing to have to do. Super-brittle (and more or less removes any benefit to actually using a navCtrl).
If anyone has any advice about further documentation / medium posts / tweets / stackoverflow questions to look at, I’d love something, as I’ve dug through (a) the documentation and (b) the source code and am stuck.