The key part of the warning here seems to be on null-object
By default, MvvmCross View
s find their ViewModel
s during ViewDidLoad()
- so a solution to you current problem might be to call base.ViewDidLoad()
:
public override void ViewDidLoad()
{
base.ViewDidLoad();
// the rest of your Load code
}