Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Component used: Navigation Version used: 2.7.6 Devices/Android versions reproduced on: Emulator API 34
The overall issue is that a standard Material design bottom navigation is very difficult to implement with the Navigation library in Compose. At minimum I would expect documentation or a sample showing how to implement it. At best it would be nice to have an additional API to easily implement it.
Specifically, since Compose navigation uses deep link logic under the hood, when navigating to a destination that can be reached from multiple tabs, the route that navigation library uses to get to that destination is based on which route was added to the graph first (basically indeterminate), rather than searching within the current graph.
See this link for another description of the problem:https://stackoverflow.com/questions/77307862/jetpack-compose-how-to-navigate-from-many-bottom-tabs-to-one-screen .
The workaround is to manually keep track of the parent graph context by constructing unique routes including the parent destinations in the route string. I call this a workaround because:
Here is a sample app describing the issue:https://github.com/Chozzle/sample-compose-tab-nav