Getting Exception System.ArgumentNullException.

[Naveen9453]

Steps to reproduce 📜

1.Created Project using MvvmCross and setup iOS project, Done changes in AppDelegate, Added ViewModel Class to Core part and Added App.cs file,Added LinkerPleaseInclude.cs file.

2.Created All changes as per this link https://github.com/nickrandolph/MvxPlus1DaysOfMvvmCross

3.Getting exception in ViewController while set.Apply() Line in ViewDidLoad method of ViewController.

       var set = this.CreateBindingSet<LoginViewController, LoginViewModel>();
        set.Bind(valueLbl).To(vm => vm.Value);
        set.Bind(entryTxtField).To(vm => vm.Value);
        set.Apply();

Expected behavior 🤔

It should run without exception and should work with data binding from viewmodel property.

Actual behavior 🐛

It Throwing System.ArgumentNullException.
Please see attached png file of exception.

Configuration 🔧

Version: 6.1.x

Platform:

• 📱 iOS

[nickrandolph]

Hi @Naveen9453 would you be able to try to reproduce this in the playground sample and issue a PR so that we can investigate?

[Naveen9453]

Hi @nickrandolph I am running your sample from this link https://github.com/nickrandolph/MvxPlus1DaysOfMvvmCross and getting same exception

[nickrandolph]

Sorry I meant the playground sample that's included within the mvvmcross source code (https://github.com/MvvmCross/MvvmCross/tree/develop/Projects/Playground)

[Naveen9453]

I have cloned the projects from below link: https://github.com/MvvmCross/MvvmCross/tree/develop/Projects/Playground
still getting this errors. I'm not able to build project from this link.

[nickrandolph]

@martijn00 @Cheesebaron is the mvvmcross solution buildable on VS Mac yet?

[Cheesebaron]

@nickrandolph the build script will most likely run fine. However, not sure how well VSfM handles the solution. We are very much on the bleeding edge here.

[nickrandolph]

@Naveen9453 are you able to build mvvmcross using VS (PC not Mac) and submit a PR demonstrating the issue in the playground?

[jamespettigrew]

I'm 99% sure this issue can be solved by updating LinkerPleaseInclude (see this issue).

@Cheesebaron @Naveen9453, I think this can be closed. Naveen can reopen if the solution I linked is not helpful.