A modern programming language that makes developers happier.

kotlinlang

Hi! I’m using navigation-compose alpha06 and having crashes whenever I tried to popBackStack from a nested navigation.
Does anyone having the same issue?
Sample code in :thread:

sample.kt

The error is because this line
```hiltViewModel(navController.getBackStackEntry("b")```


Whenever I tried to popBackStack from `nestedB` got this error
```java.lang.IllegalArgumentException: No destination with route b is on the NavController's back stack. The current destination is Destination(0xe5901274) route=a```

Issue created
<https://issuetracker.google.com/issues/195570271>

Sounds like the same issue as <https://kotlinlang.slack.com/archives/CJLTWPH7S/p1628012256418100?thread_ts=1628012256.418100&amp;cid=CJLTWPH7S|https://kotlinlang.slack.com/archives/CJLTWPH7S/p1628012256418100?thread_ts=1628012256.418100&amp;cid=CJLTWPH7S> where you aren't taking into consideration that the animations between destinations mean you're going to recompose multiple times even after you are popped (for the fade exit animations)

Have you tried wrapping your call to `getBackStackEntry()` in a `remember`?

I tried this but no luck
```navigation(startDestination = "nestedB", route = "b") {
                        composable(route = "nestedB") {
                            val backStackEntry = remember {navController.getBackStackEntry("b")}
                            ComposableB(navController = navController, hiltViewModel(backStackEntry))
                        }
                        composable(route = "nestedC") {
                            val backStackEntry = remember {navController.getBackStackEntry("b")}
                            ComposableC(navController = navController, hiltViewModel(backStackEntry))
                        }
                    }```

it throws
```java.lang.IllegalStateException: You cannot access the NavBackStackEntry's ViewModels until it is added to the NavController's back stack (i.e., the Lifecycle of the NavBackStackEntry reaches the CREATED state).```

Ah, I missed that you were accessing the nested graph, that'd be the same issue as this thread: <https://kotlinlang.slack.com/archives/CJLTWPH7S/p1626962860278800?thread_ts=1626960240.270300&amp;cid=CJLTWPH7S|https://kotlinlang.slack.com/archives/CJLTWPH7S/p1626962860278800?thread_ts=1626960240.270300&amp;cid=CJLTWPH7S>

Which resulted in this issue which we're tracking: <https://issuetracker.google.com/issues/194313238|https://issuetracker.google.com/issues/194313238>

Oh! Thank you! I’ll will comment on the duplicated issue of mine.