A modern programming language that makes developers happier.

kotlinlang

_[compose-navigation]_
Given an authentication flow in an app, which can go deeper with sign ups, mfa and stuff, how should I go about on going back to the auth-required screen with compose? I was looking to use something like `navController.popBackstack(route="authParent")` but there’s no API like that.
I can’t point to a specific route from the navigation flow because the app can navigate to Auth from different screens.

Untitled.kt

Thinking of something like this. Or is there a better way of “finishing” a flow with compose-navigation

You can pop the whole graph by using the route of the graph with `popBackStack()`

:thinking_face: I’m in compose beta05 and compose-navigation alpha10 but I can’t find a `popBackStack(route)`

Or do you mean something like
```navController.navigate("auth_nav") {
    popUpTo("auth_nav") { inclusive = true }
}```
?

That would pop the whole auth_nav, then navigate to a new copy of it, which isn't what you want

trying to find this api from the source… sorry if I missed it.
There is a `popBackstack(id)`  but the id is implementation detail in compose-nav

This is probably a hacky solution, but I used nested navigation graphs. The reason why I used it is that the google docs said a potential use of nested navigation is "self contained login flow." Still feels kinda hacky...

Yeah, looks like we're missing that overload. <https://issuetracker.google.com/issues/172823546|https://issuetracker.google.com/issues/172823546> tracks bringing routes entirely up to par with IDs in every API surface

Yeah my auth flow is a nested navigation. Do you have a way to pop the whole nested graph currently? <@U01PSM6FE0P>

Yes, you would want your login flow to be its own graph (and never the start destination of your whole app, as per the Principles of Navigation)

So you know how you have 2 navigation host controllers, right? I had to pass in the one that was nesting (let's call this host A) into the nested graph (host B),  so if I wanted to go back to the login within host B, i would call host A and navigate back to the login route. Again, feels kinda hacky, and I'm open to improvements here

Yes, I try to follow principles as much as I can :slightly_smiling_face:
Thanks! Will this update get pushed it on the next version?
Otherwise I would need to think of some workaround for now.

You shouldn't and don't need to use separate NavHosts for this, no

(actually I have already tried copying the internal `createRoute(route).hashCode` to make use of other APIs but for another use case :laughing:)

What I'd suggest is using `navController.getBackStackEntry("auth_nav").destination.id`

Oh :face_palm: I haven’t thought of that.

This should be good enough for now, thanks!

<@U01PSM6FE0P> I’ve tried working with multiple navhosts in another thing and it just makes the navigation behavior questionable in a lot of things :sweat_smile:.

Yah definitely. My solution just happened to work and I was like, aight :sweat_smile: