My bottom navigation can't navigate to the start destination after opening a deep link. Any idea why?

Thank you, that explains things

Hey, is there any updates on this, did you perhaps find a solution better than what is in the issue tracker ? I'm running into the same problem

The main issue I see with apps is that they aren't using a nested graph for each bottom nav item. As per that issue, that is a requirement to have each tab have its own back stack when deep linking into one of the other tabs

Hey Ian, I am actually using nested graphs on the bottom items. It works perfectly when the app is closed, however, if the app is in background and handling deeplink in

onNewIntent

then reselecting the last selected bottom item always navigates to the deep link destination. The above issue tracker link summerizes the issue I am also having perfectly. Note that I am handling the deeplink in

onNewIntent

with

navController.navigate with a deep link request param and nav options

instead of using

navController.handleDeeplink

because I don't want the synthetic back stack to replace my current back stack, I am trying to preserve the last back stack state before deep linking happens. But there is always some corner case that is not behaving correctly. I wonder how YouTube for example does that

So are the guidelines to have a Nested graph per bottom nav item? Is this mentioned anywhere in the docs?

Well yeah, if you call

navigate

, all that is going to do by default is add that on whatever back stack you are on. It just does exactly what you told it to do

For sure, but I've been following the guidelines for bottom nav in https://developer.android.com/jetpack/compose/navigation#bottom-nav and that one talks about Screens only, not graphs. Save & Restore state and singleTop seem to do the job without these being Nested Graphs.. So I'm just not sure what's right here - are we going to run into this behaviour mentioned in the issuetracker when we add deeplinks (in a full compose app if that matters) ?

If

handleDeepLink()

is working as expected (with the caveat of always putting the user in an understandable, consistent place rather than the merge kind of behavior you are trying for), then the problem is with your custom logic in

onNewIntent

I was probably not clear here - I've not hit any problems yet with my bottom nav setup (set up like the link in the docs, with screens not nested graphs), it was more of a worry/question whether I've just missed something and I was trying to get ahead of possible problems.

Yes, might be something with my implementation on

onNewIntent.

However, I'm struggling to find a proper solution. I'ma quickly highlight the issue maybe anyone is able to provide help. • The app has 3 bottom navigation tabs, each associated with a nav-graph, consider

GraphA, GraphB, GraphC.

• The user is on

GraphB

- the app is in the background. • The app receives a deep link to

C1

•

onNewIntent

calls

navController.navigate(deeplink)

• The app correctly navigates to

C1

Now the problem,

C1

is on top of

GraphB

and this is normal, because

I added no navOptions

to the navigate function, so when

NavItemB

clicked nothing happens since nav component just added the deeplink destination on top of it's stack. Adding

navOptions

popupTo

navController.graph.startDestinationId will make

C1

to be pushed on top of the right nav-graph

GraphC

BUT pressing back now goes back to

GraphA

, meaning it has not respected the previous destination before the deeplink happened. What

navOptions logic

can be added or any other logic so that pressing back goes back to

GraphB,

or in other terms to previous destination before the deeplink.

That's not how multiple back stack works by default - system back takes you to the start destination, then out of the app - users would need to reselect bottom nav B to get back to the back stack for B, which should be there with all of its state

Yes pressing the item B restores back the state and works, I just need to check whether the back press can have the same behavior. In the app, a normal backpress from any tab goes back to the start destination then out of the app, assuming deep linking did not happen. Adding popup to start destination restores back the normal behavior