GoBackAsync does not trigger OnNavigateTo if using FlyoutPage
See original GitHub issueNo projeto de amostra, ao navegar a partir do exemplo “FLYOUT PAGE”, o GoBackAsync
não dispara o OnNavigatedTo
da viewModel MainPageViewModel
:
https://github.com/dansiegel/Prism.Plugin.Popups/blob/b35e05473e23493b75cdd2ab617fde0300d84ce3/samples/src/PopupPluginSample/ViewModels/PopupViewModel.cs#L52
private async void OnNavigateBackCommandExecuted() { await _navigationService.GoBackAsync(new NavigationParameters{ { "message", "Hello from the Popup View" } }); }
I noticed that when navigating from the example “MASTER DETAIL PAGE” it works normally.
What could it be ? should i configure something specific or would it be a navigation issue with FlyoutPage ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Why doesn't GoBackAsync() fire on OnNavigatedTo ...
I have two pages pageA and pageB. When I navigate from pageA to pageB and later execute _navigationService.GoBackAsync() , it works correctly ...
Read more >GoBackAsync not firing OnNavigatedTo · Issue #977
I have a problem with the navigation service on version 6.3 when I call _navigationService.GoBackAsync(navParams) it does not fire the ...
Read more >Navigation doesn't work when trying to GoBack ...
I have a HelpPage in my project that has a BackButton with this command on BaseViewModel: DelegateCommand _goBack; public DelegateCommand ...
Read more >Navigation Basics
Page navigation in Prism is accomplished by using the INavigationService. ... If you do not register your Pages with Prism, navigation will not...
Read more >Page Navigation | Prism
When navigating within the context of a NavigationPage, the Navigation Service understands that the next page will be added to the NavigationPage and...
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 FreeTop 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
Top GitHub Comments
This problem is already solved in the master branch. So we need to do one of the following:
@davibittencourtome Wait for an update of PrismLibrary/Prism (current version 8.1.97) or dansiegel/Prism.Plugin.Popups (current version 8.0.76)? The Prism.Plugin.Popups alredy references 8.1.97 in its csproj. I think this issue should be reopened.