When NavigationSegments is "/TabbedPage/NavigationPage/ContentPage",
ActiveAware method is called twice in ContentPage's ViewModel implemented IActiveAware.
This problem only occurs when the application is launched.
.OnAppStart((container,navigationService) =>
{
navigationService.CreateBuilder()
.AddTabbedSegment("MyTabbedPage", config =>
{
config
.CreateTab(t => t.AddSegment<MyNavigationViewModel>().AddSegment<MainViewModel>())
})
.Navigate(HandleNavigationError);
})The cause of this is the duplication of IsActive operations in the NavigationPageActiveAwareBehavior and the TabbedPageActiveAwareBehavior.
Perhaps this can be resolved by adapting the NavigatingPageActiveAwareBehavior after adding a child to the TabbedPage.
I think it can also be solved by applying TabbedPageActiveAwareBehavior after adding children to TappedPage.
Currently, behaviors are applied in the CreatePage method, so adding a CreatePage method that does not apply Behaviors may be a solution.
When NavigationSegments is "/TabbedPage/NavigationPage/ContentPage",
ActiveAware method is called twice in ContentPage's ViewModel implemented IActiveAware.
This problem only occurs when the application is launched.
The cause of this is the duplication of IsActive operations in the NavigationPageActiveAwareBehavior and the TabbedPageActiveAwareBehavior.
Perhaps this can be resolved by adapting the NavigatingPageActiveAwareBehavior after adding a child to the TabbedPage.
I think it can also be solved by applying TabbedPageActiveAwareBehavior after adding children to TappedPage.
Currently, behaviors are applied in the CreatePage method, so adding a CreatePage method that does not apply Behaviors may be a solution.