This issue has existed for a while, and we implemented some work around using nested routes. This was, however, a temporary workaround that only solved a limited number of use-cases.

This actually arises from an underlying issue with Ionic, but the Ionic team has decided that they won't support this type of navigation so we should do something with our temporary workaround. One possible solution would be to prefix all routes with a random hash (similar to what we already do in private files).

An easy way to reproduce this issue is to create two Page activities that link to each other. If you click through the links, when you go back the navigation stack will only hold one activity instead of the entire navigation history.