Cannot navigate back after nested Shell navigations
See original GitHub issueIf I navigate to some page using ShellNavigationManager, and then navigate again to some third page, I cannot go back from that page - back button has no effect.
Example in ControlGallery: Skia Playground -> Skia Canvas Paths.
Attempt to execute Shell.Current.Navigation.PopAsync leads to an error (sorry for screenshot):
Error

(Issue reproduces on older commits as well, so not related to #298 )
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
React Navigation 5 Nested Screen can't get back to ...
On my home tab, I have a horizontal scroll of the same stations as the stations page. Problem: When I navigate from the...
Read more >Navigating to Nested Stack Navigator Doesn't Show Go ...
When I navigate from a screen in a different tab to a nested page in a stack navigator, the goback button does not...
Read more >Navigate to a tabbed page in a xamarin shell application
I like the concept and it seems like a nice clean interface. Is it possible to have nested tabbed pages or for a...
Read more >Create a nested navigation flow
The app bar displays a back arrow and exits the setup flow when the back arrow is pressed. However, exiting the flow causes...
Read more >Navigation w deeplink not forming backstack as expected ...
According to the documentation, "When a user uses the Back button from a deep link destination, they navigate back up the navigation stack...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Sorry, my bad, I’ve lost “not” in the previous comment 😃.
I don’t think anything is required (apart from updating XF when it releases).
Got it! So we’ll hold onto this bug until we can pull in an update.