Beta Release: Cycle 7 Service Release 1 (updated)

We are publishing a newer preview of our second bugfix release on top of Cycle 7, called Service Release 1. As this is a Beta build, there may be some known issues and the possibility of new issues being found during testing.

NOTE Regarding .NET Standard and NuGet Client – These builds introduce compatibility with the new .NET Standard 1.6.  This in particular allows developers to consume NuGet packages that have been built against the .NET Standard 1.6.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the beta channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.Android / 42168] – Error thrown when attempting to deploy a test app from Visual Studio to Android.
  • [Xamarin.Mac] – Some Xamarin.Mac Unified Mobile applications may fail linking with errors related to System.Security.dll. This can be worked around by disabling linking or downgrading to SR0. This will be fix in a future update.

Products Released 


Upcoming Release Dates

Beta – July 6th, 2016

Beta 2 – This Release!

Stable – July 2016

Preview: iOS 10 / Xcode 8 / Sierra Support

We are releasing a set of preview builds with support for Xcode 8, iOS 10, watchOS3, tvOS 10, and MacOS Sierra. Be sure to check out the supporting documentation on all these products as well. 

NOTE – These builds have been tested against Xcode beta 2. It has compatibility with Xcode beta 3, however we are still testing against beta 3 to find any issues that may exist.

There is no target stable date final iOS 10 support at this time, as we have to wait until Apple finalizes and publishes their support before we can release ours. That being said, we will do additional preview releases between now and the final Apple release, so be sure to check back and see if newer versions become available in the coming months.

As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla. You can also jump into the discussions on the forum thread posted below.


Known Issues 

  • [Xamarin.iOS/Xamarin.VS] 42647: The Designer is not supported for Visual Studio in this preview.
  • [Xamarin.iOS/Xamarin.VS] 42573: watchOS projects will not build in Visual Studio with debug device configuration
  • [Xamarin Studio] 42568: WatchInterface.storyboard fails to load.
  • [Xamarin.iOS]41329: You will need to  disable, then enable, the ‘Show app on apple watch’ option on iPhone to install WatchKit app on watch device.

Products Released

  • Xamarin for Visual Studio 99.0.0.2978 [Download]

Beta Release: Cycle 7 Service Release 1

We are publishing a preview of our second bugfix release on top of Cycle 7, called Service Release 1. As this is a Beta build, there may be some known issues and the possibility of new issues being found during testing.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the beta channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.iOS / 41836] – Breakpoints in ‘async’ methods in PCL projects are not hit if the linger is enabled when debugging on iOS projects.
  • [Xamarin.Android / 42168] – Error thrown when attempting to deploy a test app from Visual Studio to Android.

Products Released 


Upcoming Release Dates

Beta – This Release!

Stable – July 2016

Xamarin Studio Stable Hotfix for Incompatible XS Addins

We are releasing an updated Xamarin Studio build to the Stable channel in order to address an issue causing addins for Xamarin Studio 6.0 to show as incompatible with Xamarin Studio 6.0.1 for some users.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.


Issues Addressed 

  • 42089 – Fixed an issue where addins for Xamarin Studio 6.0 were showing as incompatible with Xamarin Studio 6.0.1.

Products Released 

Stable Release: Cycle 7 Service Release 0

We are publishing the stable builds of our first bugfix release on top of Cycle 7, called Service Release 0.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the Stable channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.VS]41836 – For iOS apps, breakpoints within async methods in PCL projects are not hit if the linker is enabled.
  • [Xamarin.VS/Xamarin.iOS] – Under certain conditions, downgrading from our Xamarin products in the Alpha channel to the Beta or Stable channel versions may result in the Xamarin.iOS plugin failing to load correctly.
    • Workaround – Delete the component cache  (steps here).
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”
  • [Xamarin.Android] – AOT+LLVM compiling is disabled in this release due to a crash discovered while trying to fix a compiler issue. It will be re-enabled in a future release.

Products Released 


Upcoming Release Dates

Beta – June 20th, 2016

Stable – This Release!

Beta Release: Cycle 7 Service Release 0

We are publishing a preview of our first bugfix release on top of Cycle 7, called Service Release 0. As this is a Beta build, there may be some known issues and the possibility of new issues being found during testing.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the beta channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.VS]41836 – For iOS apps, breakpoints within async methods in PCL projects are not hit if the linker is enabled.
  • [Xamarin.VS/Xamarin.iOS] – Under certain conditions, downgrading from our Xamarin products in the Alpha channel to the Beta or Stable channel versions may result in the Xamarin.iOS plugin failing to load correctly.
    • Workaround – Delete the component cache  (steps here).
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”
  • [Xamarin.Android] – AOT+LLVM compiling is disabled in this release due to a crash discovered while trying to fix a compiler issue. It will be re-enabled in a future release.

Products Released 


Upcoming Release Dates

Beta – This Release!

Stable – June 2016

Preview: Xamarin Profiler 0.33.2

Xamarin Profiler preview 0.33.2 is now available for download! There have been a number of fixes since our previous preview, which have been noted below.

Please note that the Mac app bundle has been renamed (from XamarinProfiler.Mac.app to “Xamarin Profiler.app”), so the old version needs to be removed before installing this new update, so that Xamarin Studio prompts the user for the new location.


Known Issues

  • No official support for profiling release builds is available at this time.
  • Data sets are correct at the time of collection, but data mining and representation is preliminary. This will improve in future releases.
  • Time instrument not available for Android and tvOS profiling.
  • Support for Xamarin.Mac app profiling is preliminary.
  • Installation on Windows with previous versions (>= 0.24) fails, so old profiler versions will be uninstalled first.

Issues Addressed

  • 39763 – Old Xamarin.Mac used for building the package.
  • 40944 – Crash when selecting time range with no instruments.
  • 40451 – Remove dependency on Xamarin Studio.
  • 40345 – Time range selection enabled when just clicking on the chart.
  • 41248 – Wrong caption when drilling down allocations summary.
  • 41284 – Exception when stopping Android run.
  • 41293 – Call tree nodes getting collapsed.
  • 41210 – Call tree options don’t work when time range selected.
  • 40595 – Missing loading spinner.
  • 41427 – Unhandled exception.
  • 41137 – Can’t profile on iOS devices

Products Released


As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla. You can also jump into the discussions on the forum thread posted below.

Technical Bulletin: Android SDK Build-tools 24

Version “24” of the Android SDK Build-tools package contains an upstream bug in aapt that can cause at least 2 errors:

  • ​””aapt.exe” exited with code -1073741819″ (This error can also appear if the Android SDK Build-tools version is not compatible with the installed version of Xamarin.Android. But in this particular case the error is due to the upstream bug.)
  • “The file “obj\Debug\android\bin\packaged_resources” does not exist.”

This bug has been fixed in Android SDK Build-tools 24.0.1.

Recommended fix: Uninstall Android SDK Build-tools version 24 using the Android SDK Manager.


Another separate issue is that versions 24 and higher of the Android SDK Build-tools package require Java JDK 8 or higher. This can cause at least 1 error:

  • “java.lang.UnsupportedClassVersionError: com/android/dx/command/Main : Unsupported major.minor version 52.0”

Possible ways to fix:

  • Update to Java JDK 8, and then make sure that JDK 8 is selected in the Xamarin preferences:
    • Visual Studio: Tools > Options > Xamarin > Android Settings > Java Development Kit Location.
    • Xamarin Studio (on Mac): Xamarin Studio > Preferences > Projects > SDK Locations > Android > Java SDK (JDK).
  • Or uninstall all Android SDK Build-tools versions 24 and higher via the Android SDK manager.
  • Or set the AndroidSdkBuildToolsVersion MSBuild property to an earlier version. For example, if you also have version 23.0.3 installed, you could add the following line within the top <PropertyGroup> element in the Android project .csproj file:
    <AndroidSdkBuildToolsVersion>23.0.3</AndroidSdkBuildToolsVersion>

(Edited on July 14, 2016: Simplify the recommendations and provide a link to the upstream bug.)
(Edited on July 25, 2016: Mention the new version Android SDK Build-tools 24.0.1.)
(Edited on August 11, 2016: Add a note about checking the JDK version in the Xamarin preferences.)

Preview: Xamarin Inspector 0.9.0

We are releasing an updated preview of the Xamarin Inspector for iOS, Android, Mac, and WPF applications. Xamarin Inspector is an interactive tool that you can use to diagnose and prototype changes in your application. The inspector can attach to a live application on any of the supported platforms.


Products Released

Preview: iOS Simulator (For Windows)

We are releasing our second preview of the iOS Simulator for Xamarin.VS. The remoted iOS Simulator provides you with a way to test and debug iOS apps on the simulator entirely from Visual Studio on Windows.


Known Issues

  • Non-public Bug 41626: “Failed to install … App1.app” when attempting to launch Xamarin.Forms project.
    • Partial workaround Launch the app on the regular (non-remoted) Apple Simulator first.
  • Non-public Bug 41620: “The device … was not found” if Xcode path setting is blank (it is blank by default).
    • Workaround – Set the Xcode path explicitly under Tools > Options > Xamarin > iOS Settings > Xcode path.

Products Released

  • iOS Simulator (for Windows) 0.9.1.2 [Win VS Download]
    • Release Notes
    • New Features:
      • Support for stylus translating to pencil input has been added
      • A dialog is shown when sim starts and include an update status
      • Fixed an issue preventing the simulator from starting using usernames with spaces in them