OnActive doesn't fire on VM if you navigate in OnInitialize method

Topics: Bugs
Sep 11, 2014 at 4:31 PM
Hello!
I have 3 VM: StartVM, ListItemsVM, ItemDetailsVM
Let\s say, I ran app from secondary tile and I need to open ItemDetailsVM with some Id. But I also need to open ListItemsVM for create navigation back entries stack.
So, in StartVM I do navigation:
 base.navigationService.UriFor<ListItemsVM>()
.WithParam(vm=>vm.ItemQueryParameter, 1)
.Navigate();
base.navigationService.RemoveBackEntry(); //drop StartVM from stack
Then, in ListItemsVM in OnInitialize method I navigated to ItemDetailsVM.
And there, if I do navigationService.GoBack in code or user tap Back button, I will return to the ListItemsVM and OnActive event won't fire because it had activated after my navigation to new VM.

I know that I could navigate to the ItemsDetailsVM and then open the ListItemsVM. It's not good for me now, but I'll do that if I won't have any other way,
I just interested can it be fixed in framework? Because it looks like a bug.
Thanks.
Sep 15, 2014 at 3:28 PM
Actually, how to delete navigation parameter in INavigationService? I've tried to replace Source in BackStack item but it still has one when I navigated back.