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

Alpha Preview 2: Cycle 8

We are releasing a new Alpha preview of our next major feature release, called Cycle 8. As this is an Alpha build, there are 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: This is a release only for Xamarin Studio and Xamarin iOS. Updates to Xamarin.VS, Xamarin.Android, and Xamarin.Mac will be included in a future preview.


Known Issues

  • [Xamarin Studio / Xamarin.VS] – Updating your Xamarin.iOS, Xamarin.Android, or Xamarin.Mac to the builds noted below without also updating your IDE will prevent the IDE from properly running license checks, which can cause adverse functionality.
  • [Xamarin Studio – Windows Only] – You must have both MS Build Tools 2013 and MS Build Tools 2015 installed on your machine for Xamarin Studio to work properly on Windows.
  • [Xamarin.iOS] – Breakpoints may not hit for WatchKit applications when the Link All option is selected.
    • Workaround – Perform a “Clean” (or Rebuild) after switching the Link all option on.

Products Released


Upcoming Release Dates

Alpha – April 27th, 2016 (Evolve Conference)

Alpha 2 – This Release!

Stable – Fall 2016

Stable Release: Cycle 7

We are publishing the final builds for our next major feature release, called Cycle 7, to the Stable channel.

Please check out the product release notes to see all the fixes and known issues for this release, 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. The functionality for this is supported in this release.

NOTE: Visual 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: The Cycle 7 version of Xamarin.VS requires Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.

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. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.


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 Studio] –  41565 – “Could not load solution:” and “Load operation failed.” when attempting to open certain projects in Xamarin Studio 6.0.
    • Recommended fix – Open the problematic .csproj file in a text editor and remove the conflicting item from the <ProjectTypeGuids> element. For iOS extension projects, the most common fix is to remove the {FEACFBD2-3405-455C-9665-78FE426C6842}; item from the list.
  • [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 

  • GTK# 2.12.38

Previous Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – May 24th, 2016

Stable – This Release!

Beta Release: Cycle 7 Release Candidate 3

Update (6/6) – Slightly newer builds have been pushed to the Beta channel in anticipation of our upcoming Stable release. Please see the newer version numbers noted below. 

We are publishing a new release candidate of our next major feature release, called Cycle 7. 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. The functionality to support this is supported in this release.

NOTE: Visual 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 MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – This Release!

Stable – April/May 2016

Preview: Android N Support Preview 2

We are releasing our second preview with support and bindings for Google’s Android N SDK. Be sure to visit the Android N page and read about all the new features N support provides. If you are looking to get started right away, make sure to check out the new Android N samples and join in on the forum discussions.

Please note that depending on which platform you are targeting, you will need to download certain products for this preview to work:

  • If you are using Visual Studio, you will only need to download the Xamarin.VS linked below.
  • If you are using Xamarin Studio on a Mac machine, you will need to download the Xamarin Studio, Xamarin Android, and Mono Framework linked below.
  • If you are using Xamarin Studio on a Windows machine, you will to download the Xamarin Studio, Xamarin.VS, and GTK Installer linked below.

There is no target stable date for N support at this time, as we have to wait until Google finalizes and publishes their support before we can release ours. That being said, we will do additional N preview releases between now and the final Google 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.Studio / Xamarin.VS] – The Xamarin.Android Designer does not support rendering of the new API level (N).
  • 31002 – [Xamarin.Studio / Xamarin.VS] – Users will have to manually make sure their minimum SDK version is set to v6.0 (23) or lower, instead of v6.0.99 (24), in order to deploy to N devices and emulators.
  • 40156 – [Xamarin Android] Projects which utilize Support.v7.AppCompat may no longer compile on Windows when using the preview build tools (24 rc2). This can be worked around by using the latest stable version of build tools instead (23.0.3).

Products Released

  • Xamarin for Visual Studio 4.1.0.509 [Download]

Beta Release: Cycle 7 Release Candidate 2

We are publishing a new release candidate of our next major feature release, called Cycle 7. As this is an Beta build, there are 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. The functionality to support this is not in this release, however it will be included in a future release of Cycle 7, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

NOTE: Visual 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 MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – This Release!

Stable – April/May 2016