Stacked views in Android issue about mvvmcross-controlsnavigation

[ChristianRuiz]

You shouldn't have more than one instance of the same control in the same View, otherwise it would be impossible to determine witch one to be show in ShowViewModel.

The problem should be that the controls are not destroyed on navigation between Views, let me modify the sample to have multiple Views and work in a good approach.

If we just use the last one, when you press back, it wouldn't find the control. I'm working also on supporting Android fragments, hope to be able to release a new version with this issue and the fragments this week.

[ChristianRuiz]

You were right, Android its not destroying its controls on navigation, but that's the correct behaviour to allow going back. Its already changed.

[ChristianRuiz]

I've updated the NuGet package with it: https://www.nuget.org/packages/MupApps.MvvmCross.Plugins.ControlsNavigation/1.0.5