Hi, colleagues. Any idea how to make Nested NavHosts with different NavControllers? My current code ...

# compose

[Александр Макаров]

Hi, colleagues. Any idea how to make Nested NavHosts with different NavControllers? My current code snapshot causes doubling of navigation event while calling navController::navigateUp()

[Александр Макаров]

Futhermore, on Compose Navigation 2.5.0-alpha03 this causes a crash because of attaching to existing lifecycle

[Stylianos Gakis]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1631295818240300?thread_ts=1631295578.239400&cid=CJLTWPH7S
https://kotlinlang.slack.com/archives/CJLTWPH7S/p1636640345295800?thread_ts=1636568932.266000&cid=CJLTWPH7S
Multiple NavHosts seem to always be a mistake, if I understood your question right.

[Александр Макаров]

As official docks recommend to hide\show bottom nav - it creates unintended glitch while it dissapears (especially with animation). That's not that good for UX, but that was my first approach before current decision. Multiple NavHosts was navigating as it expected, but navigatingUp creates a double event which causes a crash on 2.5.0-alpha03

[Александр Макаров]

If everybody had a good approach to single-activity case (e.g I want to open SettingsScreen composable, from MainScreen, which exist in parent navgraph) without bottomnav in nested navgraph destinations - that would be great

[Ian Lake]

it creates unintended glitch while it dissapears (especially with animation)

You are in complete control over the animation so any glitch is more that you aren't using AnimatedVisibility or aren't observing the animation state to know when to start your animation