Stable Release: 15.3.2 Servicing Release

We are releasing a service release for our current major release called 15.3 into the Beta and Stable channels.

This release is now available as part of Visual Studio 2017 version 15.3 and in the Stable updater channels for Visual Studio 2017 for Mac and Xamarin for Visual Studio 2015.

Please check out the product release notes to see all the fixes and known issues for this release.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.

Bug reports are also welcome. If you see any suspicious behavior that you wish to report, please file a quick bug.

Products Released

  • Xamarin.VisualStudio
  • The only change in this version is to update the Xamarin.iOS and Xamarin.Android packages.

Included Fixes

This release targets 4 specific bugs that are the most commonly seen issues in the Xamarin 15.3 release:

  • 58789 and 58834 [Xamarin.iOS] – “error MT0000: Unexpected error – Please file a bug report …” and “error MT2102: Error processing the method … Value cannot be null” when attempting to build certain projects with linking enabled.
  • 57919 and 58625  [Xamarin.Android, Xamarin.iOS] – “System.PlatformNotSupportedException: Operation is not supported on this platform” at System.Runtime.InteropServices.Marshal.IsComObject() when trying to use dynamic types.

Other Common Issues from the Xamarin 15.3 Release

In case it might also be useful for reference, here are a few other in-progress progress commonly seen issues being tracked by the Xamarin team from the Xamarin 15.3 release. This list is not exhaustive: It does not include every issue user-submitted issue reported since the time of the Xamarin 15.3 release.

  • 58226 (non-public) [Xamarin iOS Designer] – “MonoTouch.Design.Client.DesignerRemoteException: System.NotSupportedException: Could not parse xml” when attempting to open a storyboard or .xib file, for example after editing the file with Xcode.
    • Temporary workaround: Open the problematic file as text (for example via the context menu for the file in the Solution window), and then remove the device element from the top of the file. It typically looks something like:
      <device id="retina4_0" orientation="portrait">
          <adaptation id="fullscreen"/>
  • 58829 [Xamarin.Android, Xamarin.iOS] – Application Output window flooded with “[Mono] worker parking, [Mono] worker unparking” messages when debugging with Android Emulator.
    • Temporary workaround: Set the MONO_LOG_LEVEL environment variable to message or higher.
      • For example, on Xamarin.Android in a command prompt using adb:
        adb shell setprop debug.mono.env "MONO_LOG_LEVEL=message"
      • For Xamarin.iOS, go to Project Properties > iOS Build > Additional Options > Additional mtouch arguments, and add:


Previous Versions

Using the latest versions is recommended. The previous versions of the Xamarin and Mono packages from the Xamarin 15.3 release are listed below for reference.