You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I have a structure with just a lazy module that contains several children, one of these childrens is my "home" page, but no matter what child I am in, the app always closes ...
Let the apps only close when I am on the "/ test" route, if it is in "/ test2" it should not close, I would not like to hear suggestions for signing up for backpress events :D
The text was updated successfully, but these errors were encountered:
The framework has no way of knowing what you consider "home" screen, the back button will put the app in the background if navigation stack is empty (you are on the first Frame). In your case the only Frame that's created is FeatureComponent, since the other components are used in a router-outlet, if you want them to be part of native mobile navigation use page-router-outlet.
@nikoTM It is horrible to have to handle backpressed events, as this causes a headache with the modals, so I have a large volume of code that I would not need to have inside the app, but if this is really the only solution thank you
So I have a structure with just a lazy module that contains several children, one of these childrens is my "home" page, but no matter what child I am in, the app always closes ...
https://github.com/juniorschen/IGivenUp
what i hope:

Let the apps only close when I am on the "/ test" route, if it is in "/ test2" it should not close, I would not like to hear suggestions for signing up for backpress events :D
The text was updated successfully, but these errors were encountered: