Emil Alipiev
Emil Alipiev
page and pagemodels are following your conventions. I am sure that there is no problem with that because this is all working fine but problem is described clearly in OPs...
@oddbear tuple is a good way of resolving this issue but requires c#7. @C0D3Name I dont think this is a good solution. because in some cases I might need to...
see my answer here. https://github.com/rid00z/FreshMvvm/issues/231
to be honest, when i started xamarin forms first time, I tried only master detail page, I dont remember experiencing this issue but never tried tabbed and then I met...
I changed the title for this because Tabbed page shouldnt be considered as @rid00z said this is default behavior from Xamarin forms itself but Master Details it not I believe....
I come back to this issue. It is a huge problem for me now. I am trying to improve my start up time and after doing a lot of tests....
download source code change FreshMasterDetailNavigationContainer.cs or create your own class and use it instead freshmvvm class. this class is totally independent than Freshmvvm implementation. Change the init function of class...
can you please close the issue if it works
maybe you can share your code with us. I didnt experience such behavior.
Do you mean that it appears 2 because once it is in the viewmodel ViewIsAppearing and 2nd in xaml.cs OnAppearing. this is the only 2 times I observed.