Navigation Problem

[PrarabdhGarg]

When an item in the bottom nav is selected, the new fragment is replaced by the old one. This would cause problems when handling the back-stack. Hence the fragments must be added to the back stack, instead of replacing them

[IshitaAg]

I think we should use navigation component .....then we wouldn't have to deal with fragment transactions .....

[PrarabdhGarg]

Currently, if you are at any fragment other than the home fragment, and press the back button once, nothing happens. Ideally, the events fragment should open up

[PrarabdhGarg]

I think we should use navigation component .....then we wouldn't have to deal with fragment transactions .....

As far as I know, there are some bugs in there, and it is not that convenient to use as people generally think. Source of information is a podcast, so not very sure about it

[IshitaAg]

I think we can easily control the problem you are pointing to with nav component

[AnEnigmaticBug]

Can you be more precise about what you want and what is currently happening?

[PrarabdhGarg]

When we are on a different page other than the events page, on pressing the back button, the page should change back to the events page, and the fragment in the back stack must be removed. Currently, nothing of this is happening. At any time, the back stack is completely empty

[AnEnigmaticBug]

While you can do it manually, I would myself go with the navigation component:

• It's much easier to work with.
• To get some specific behavior, you'll often need to do some 'dirty' hacks. The component will often handle a lot of those hacks for you. And those hacks would have been coded by Google's team and would have been used by a big number of developers.
• You get to scope ViewModels by navigation graphs which is really nice for flows involving multiple screens.

While it was pretty buggy back when I was making the Oasis app, I do believe that it'll be fine now. I used it in the mess app and I've not encountered a single bug due to it.

[AnEnigmaticBug]

Your current requirement can be dealt pretty easily in the navigation component using the popTo parameter(or maybe the popUpTo parameter, I don't remember off-hand).