I found cyclic navigation when the user tries to navigate ba

Question

I found cyclic navigation when the user tries to navigate back off of the stack I assume this is not the intended behavior

Bruno Hensel · Answer

Screen recording 20230424 203317 mp4

mbonnin · Answer

Going from `SessionDetails gt Speaker gt SessionDetails gt Speaker` right

Bruno Hensel · Answer

Yeah then pressing back button

mbonnin · Answer

What would be the intended behaviour It s a bit weird here because it loops on Chet s talk but you can theorically do something else `Some UI Talk` `Chet Haase` `Some Other Comedy Talk` `Romain Guy` `Some Romain Guy Talk` etc

mbonnin · Answer

Looking in the backstack for similar ids maybe

mbonnin · Answer

But then it becomes really hard to predict the logic

Bruno Hensel · Answer

Yeah it s a bit tricky Maybe check the back stack if the destination composable is the last added to back stack we just navigate back instead of creating a new composable Wdyt

Bruno Hensel · Answer

But then we would need to know the ids used in the route so we can compare them to know that the exact same composable is the previous one

mbonnin · Answer

Works for me I m not sure there s a generally good answer to that probelm

Marcello Galhardo · Answer

There is an option on navigation that navigates to the route back in the back stack if it already exists

mbonnin · Answer

But then it s potentially an issue if you have a permutation with more than 2 destinations

Marcello Galhardo · Answer

I m out of my computer now can look for it later But should be in the options lambda

mbonnin · Answer

A gt B gt C Navigating to A pops B forever

mbonnin · Answer

At least this is how I would imagine things to work

Marcello Galhardo · Answer

< mbonnin> I think it brings the navigation entry to the top actually Not super sure

mbonnin · Answer

Mmm I see

Bruno Hensel · Answer

do you mean the `launchSingleTop = true`

Marcello Galhardo · Answer

Anyway we may be overthinking a little The current behaviour or skip a few won t cause much issues IMO

Marcello Galhardo · Answer

What I would personally do is to not navigate the whole screen

mbonnin · Answer

Agree at the end of the day it s okay

Bruno Hensel · Answer

I ve tried a couple of approaches but didn t get it right so far =

Marcello Galhardo · Answer

But only the content of the tab so if the user presses the tab it cuts the back stack

Marcello Galhardo · Answer

That is the main advantage of having multi back stack support which Navigastion has

mbonnin · Answer

Ah yea allowing to go back to top level without having to press back 50 times sounds interesting slightly smiling face

mbonnin · Answer

I ve seen apps where clicking to the currently focused tab would also reset it to the top level

Marcello Galhardo · Answer

Yes exactly