You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using Compose multiplatform navigation, it seems that navigation with a nested NavGraph doesn't work and throws an error when trying to navigate to one.
Affected platforms
Desktop (Windows)
Web (K/Wasm) - Canvas based API
(I only tested these two)
Versions
Kotlin version*: 2.0.0-RC1
Compose Multiplatform version*: 1.6.10-dev1593
Compose Navigation version: 2.8.0-alpha01
OS version(s)* (required for Desktop and iOS issues): Windows 11
OS architecture (x86 or arm64): x86
JDK (for desktop issues): 17
To Reproduce
Steps and/or the code snippet to reproduce the behavior:
Use a navigation function to create a nested NavGraph and include a route which navigates to a sibling route. For example:
Launch app and try to navigate to the sibling route.
A similar error to the following will occur:
Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: Navigation destination that matches route b cannot be found in the navigation graph ComposeNavGraph startDestination={ComposeNavGraph route=subgraph startDestination={Destination route=a}}
Expected behavior
The navigation should act as it would in Android, no error should occur.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using Compose multiplatform navigation, it seems that navigation with a nested NavGraph doesn't work and throws an error when trying to navigate to one.
Affected platforms
(I only tested these two)
Versions
To Reproduce
Steps and/or the code snippet to reproduce the behavior:
Use a
navigation
function to create a nestedNavGraph
and include a route which navigates to a sibling route. For example:Launch app and try to navigate to the sibling route.
A similar error to the following will occur:
Expected behavior
The navigation should act as it would in Android, no error should occur.
The text was updated successfully, but these errors were encountered: