Jim Bennett (88) [Avatar] Offline
There are a number of moving parts when it comes to building mobile apps using Xamarin, including different Visual Studio and Xamarin versions, Xcode, and the various Android SDKs. There is also different versions of MvvmCross to consider as well when using this to build cross-platform apps.

This thread is designed to highlight known issues with different versions and give workarounds.

MvvmCross 5.2.0
There are two known issues with MvvmCross 5.2.0:

Crash on startup
When you launch your app it may crash with an MvxException, failing to construct the CountersViewModel.
The Messenger plugin NuGet package is meant to install a bootstrapper file-a class that ensures the messenger is registered with the IoC container, but with newer project types this file is not created correctly. If you see this exception, create a folder called Bootstrap in the Android and iOS app projects, and add a class called MessengerPluginBootstrap to that folder containing add the following:

using MvvmCross.Platform.Plugins;

namespace Countr.Droid.Bootstrap
   public class MessengerPluginBootstrap
      : MvxPluginBootstrapAction<MvvmCross.Plugins.Messenger.PluginLoader>

substituting iOS for Droid for the iOS app.

Hang on startup
The Initialize method can hang when awaiting async methods, such as when you await the call to LoadCounters in CountersViewModel. The fix is to update to MvvmCross 5.2.1 or later.
appDevNewToXamarin (1) [Avatar] Offline

I have only recently purchased your book and so far it seems to be exactly what i'm looking for. But the problem is when I create a MVVM cross project I have endless errors. I can't run the appliaction on any version at all of the android emulator. It's incredibly frustrating. The android emulator wont start at all when i hit run. It says there were build errors, would you like to continue? should I send some screen shots? I've spent a good few days trying to figure this out. I really need to fix this issue ASAP. please help, any advice is greatly appreciated.
Jim Bennett (88) [Avatar] Offline
That doesn't sound good. Can you send me the list of errors and a copy of the build output so I can take a look?
398977 (1) [Avatar] Offline
I enjoy the book and it starts out with good pace towards making some progress in learning Xamarin, but I not sure if it a problem with fast moving, fast breaking nature of Xamarin or the amazing mind numbing complexity and constant change/breaking MvvMcross, but I am still trying to get a single example to compile and run without a galaxy of errors and message about incompatibilities. Just seems like a great waste of money and time to get a book or video and by the time you have read the first chapter the technology is broken in the sense that all the supporting frameworks and libraries have been out dated. Visual Studio is a wonderful warm place to develop from but when each day your greeted with another 300 messages about this library doesn't work with this version of something only a day apart from running ok, it just seem like swimming upstream with no fixed point of sanity. I suspect that Xamarin and it desperate attempt to encompass all mobile development might be just to much complexity. MvvMCross is a perfect partner for Xamarin because they move and shift every few days into something new that doesn't work with what you had yesterday. Perhaps even something a static as a printed book(PDF) is just madness to think it could be a learning aid to something this fluid and mercurial. Sadly, the book is just passed from being early access to printed and largely worthless other than architectural overview.I wish I could have my money back becuase the book as product is flawed, perhap not by intention, but by the impossibility of documenting this @#$* storm of technology