Category Archives: Beta

Releases specifically targeted for the Beta Updater Channel.

Beta Preview 3: Cycle 8

We are releasing the third Beta preview of our next major feature release, called Cycle 8. As this is a Beta build, there are some known issues and the possibility of new issues being found during testing.

The issues addressed below are only the highest severity ones, so please check out the product release notes to see all the fixes and known issues for this preview.

The Xamarin team is looking for as much user feedback as possible on these Cycle 8 Beta versions, especially for the iOS 10 and Xcode 8 features. If you see a behavior that looks suspicious in these versions, and if it isn’t clear whether one of the known issues in the release notes matches the problem, please file a quick bug report.

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.


Known Issues 

  • [Mono Framework] – 33475: Android app crashes when taking snapshots
  • [Mono Framework] – 40963: iOS app crashes when taking snapshots
  • [Xamarin for Visual Studio] – 40767: Collection View and Table View are rendered differently on the iOS designer and the actual simulator

Products Released

  • Xamarin Studio 6.1.0.5383
    • Release Notes
    • Major Issues Addressed:
      • 42554 – Typing into the search box is corrupting memory and crashing XS
      • 43210 – User is not able to launch an activity by explicitly specifying which activity to launch for Android application in XS
      • 43187 – Quick build/run menu selector does not include run configurations
  • Xamarin.VS 4.2.0.628
    • Release Notes
    • Major Issues Addressed:
      • 43300 – Intermittent disconnection of VS from Build Host while working with iOS application.
      • 43037 – Unable to install XVS builds.
      • 43602 – “Device Log” window does not open in Visual Studio.
      • 43565 – Visual Studio often hangs (pauses, freezes) during `TastyConfig.DebugLaunch()` on second deployment attempt
      • 43650 – User is not getting simulator for Watckit OS1 application in VS dropdown
      • 43454 – User is not able to run Watch OS1 application with VS, application gets terminated
  • Xamarin.iOS 9.99.5.54
    • Release Notes
    • Major Issues Addressed:
      • 43373 – Unable to upload application to device due to an error “Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode8-beta6.app/Contents/Frameworks/libswiftos.dylib)” with Xcode8-beta6 update
  • Xamarin.Android 7.0.0.3
    • Release Notes
    • Major Issues Addressed:
      • 43268 – Android application crashes when launched on Android device, when running a project with a service in XS
      • 42646 – Error XA2006: Reference to metadata item ‘Android.Views.DecorCaptionShade’ when attempting to build codegen tests in release
      • 43487 – ‘System.DllNotFoundException: sqlite3’ thrown when trying to use sqlite with Cycle8
      • 42814 – Deploy to Android device fails when setting a breakpoint
  • Mono Framework 4.6.0.182
    • Release Notes
    • Major Issues Addressed:
      • 42864 –  “System.Net.WebException: Error: NameResolutionFailure” on second web request to certain raw IP addresses with HttpClient
      • 43305 – Standard Library dependency error on Xamarin Studio
      • 42408: WebClient.DownloadString returns 401 Unauthorized when using Basic authentication
      • 42938:  Compilation of netstandard PCL library with xbuild fails with… CSC: error CS0518: The predefined type …  is not defined or imported
      • 43636 – “Index was out of range. Must be non-negative and less than the size of the collection” in `System.Collections.Generic.List`1[T].set_Item()` when attempting to compile certain C# code involving tasks, async/await, and try/catch/finally

Installing the Beta and switching back to Stable

You can install this new Beta version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – April 27th, 2016 (Evolve Conference)

Alpha 2 – July 13th, 2016

Alpha 3 – July 27th, 2016

Alpha 4 – Aug 2nd, 2016

Alpha 5– Aug 9th, 2016

Alpha 6 – Aug 12, 2016

Beta 1 – Aug 17th, 2016

Beta 2 – Aug 24th, 2016

Beta 3 – This Release!

Stable – Fall 2016

Beta Preview 2: Cycle 8

We are releasing the second Beta preview of our next major feature release, called Cycle 8. As this is a Beta build, there are some known issues and the possibility of new issues being found during testing.

The issues addressed below are only the highest severity ones, so please check out the product release notes to see all the fixes and known issues for this preview.

The Xamarin team is looking for as much user feedback as possible on these Cycle 8 Beta versions, especially for the iOS 10 and Xcode 8 features. If you see a behavior that looks suspicious in these versions, and if it isn’t clear whether one of the known issues in the release notes matches the problem, please file a quick bug report.

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.


Known Issues 

  • [Mono Framework] – 42408: WebClient.DownloadString returns 401 Unauthorized when using Basic authentication
  • [Mono Framework] – 33475: Android app crashes when taking snapshots
  • [Mono Framework] – 40963: iOS app crashes when taking snapshots
  • [Mono Framework] – 42938:  Compilation of netstandard PCL library with xbuild fails with… CSC: error CS0518: The predefined type …  is not defined or imported
  • [Xamarin.iOS] – 42392:  ‘clang: error: unable to execute command: Segmentation fault: 11’ when compiling iOS project
  • [Xamarin for Visual Studio] – 40767: Collection View and Table View are rendered differently on the iOS designer and the actual simulator

Products Released

  • Xamarin Studio 6.1.0.5365
    • Release Notes
    • Major Issues Addressed:
      • 42554 – Typing into the search box is corrupting memory and crashing XS
      • 43210 – User is not able to launch an activity by explicitly specifying which activity to launch for Android application in XS
      • 43187 – Quick build/run menu selector does not include run configurations
  • Xamarin.VS 4.2.0.584
    • Release Notes
    • Major Issues Addressed:
      • 43300 – Intermittent disconnection of VS from Build Host while working with iOS application.
      • 43037 – Unable to install XVS builds.
      • 43602 – “Device Log” window does not open in Visual Studio.
  • Xamarin.iOS 9.99.4.23
    • Release Notes
    • Major Issues Addressed:
      • 43373 – Unable to upload application to device due to an error “Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode8-beta6.app/Contents/Frameworks/libswiftos.dylib)” with Xcode8-beta6 update
  • Xamarin.Android 6.2.0.47
    • Release Notes
    • Major Issues Addressed:
      • 43268 – Android application crashes when launched on Android device, when running a project with a service in XS
      • 42646 – Error XA2006: Reference to metadata item ‘Android.Views.DecorCaptionShade’ when attempting to build codegen tests in release
  • Mono Framework 4.6.0.165
    • Release Notes
    • Major Issues Addressed:
      • 42864 –  “System.Net.WebException: Error: NameResolutionFailure” on second web request to certain raw IP addresses with HttpClient
      • 43305 – Standard Library dependency error on Xamarin Studio

Installing the Beta and switching back to Stable

You can install this new Beta version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – April 27th, 2016 (Evolve Conference)

Alpha 2 – July 13th, 2016

Alpha 3 – July 27th, 2016

Alpha 4 – Aug 2nd, 2016

Alpha 5– Aug 9th, 2016

Alpha 6 – Aug 12, 2016

Beta 1 – Aug 17th, 2016

Beta 2 – This Release!

Stable – Fall 2016

Beta Preview 1: Cycle 8

We are releasing the first Beta preview of our next major feature release, called Cycle 8. As this is a Beta build, there are some known issues and the possibility of new issues being found during testing.

The issues addressed below are only the highest severity ones, so please check out the product release notes to see all the fixes and known issues for this preview.

The Xamarin team is looking for as much user feedback as possible on these Cycle 8 Beta versions, especially for the iOS 10 and Xcode 8 features. If you see a behavior that looks suspicious in these versions, and if it isn’t clear whether one of the known issues in the release notes matches the problem, please file a quick bug report.

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.


Known Issues 

  • [Mono Framework] – 42408: WebClient.DownloadString returns 401 Unauthorized when using Basic authentication
  • [Mono Framework] – 33475: Android app crashes when taking snapshots
  • [Mono Framework] – 40963: iOS app crashes when taking snapshots
  • [Mono Framework] – 42938:  Compilation of netstandard PCL library with xbuild fails with… CSC: error CS0518: The predefined type …  is not defined or imported
  • [Xamarin.iOS] – 42392:  ‘clang: error: unable to execute command: Segmentation fault: 11’ when compiling iOS project
  • [Xamarin for Visual Studio] – 40767: Collection View and Table View are rendered differently on the iOS designer and the actual simulator

Products Released

  • Xamarin Studio 6.1.0.5345
    • Release Notes
    • Major Issues Addressed:
      • 42554 – Typing into the search box is corrupting memory and crashing XS
      • 43210 – User is not able to launch an activity by explicitly specifying which activity to launch for Android application in XS
      • 43187 – quick build/run menu selector does not include run configurations
  • Xamarin.iOS 9.99.3.8
    • Release Notes
    • Major Issues Addressed:
      • 43373 – Unable to upload application to device due to an error “Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode8-beta6.app/Contents/Frameworks/libswiftos.dylib)” with Xcode8-beta6 update
  • Xamarin.Android 6.2.0.36
    • Release Notes
    • Major Issues Addressed:
      • 43268 – Android application crashes when launched on Android device, when running a project with a service in XS
      • 42646 – Error XA2006: Reference to metadata item ‘Android.Views.DecorCaptionShade’ when attempting to build codegen tests in release
  • Mono Framework 4.6.0.150
    • Release Notes
    • Major Issues Addressed:
      • 42864 –  “System.Net.WebException: Error: NameResolutionFailure” on second web request to certain raw IP addresses with HttpClient
      • 43305 – Standard Library dependency error on Xamarin Studio

Installing the Beta and switching back to Stable

You can install this new Beta version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – April 27th, 2016 (Evolve Conference)

Alpha 2 – July 13th, 2016

Alpha 3 – July 27th, 2016

Alpha 4 – Aug 2nd, 2016

Alpha 5– Aug 9th, 2016

Alpha 6 – August 12, 2016

Beta 1 – This Release!

Stable – Fall 2016

Beta Release: Cycle 7 Service Release 1 (update 3)

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.


Products Released 

  • Xamarin Studio 6.0.2.73
    • Release Notes
    • Forum Thread – Beta Release: Cycle 7 – Service Release 1
    • Issues Fixed:
      • 42051 – Fixed an error when editing control name in storyboard
      • 41862 – Android Designer should now correctly open in XS for certain projects
      • 41499 – Shortened time it takes for NuGet package searches to return results
      • 42743 – HttpClientHandler combo is not shown for Community license
      • 42795 – View >> Focus Document is not functioning
  • Xamarin.Android 6.1.2.21

Upcoming Release Dates

Beta – July 6th, 2016

Beta 2 – July 20th, 2016

Beta 3 – July 26th, 2016

Beta 4 – This Release!

Stable – July 2016

Beta Release: Cycle 7 Service Release 1 (update 2)

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.

Products Released 


Upcoming Release Dates

Beta – July 6th, 2016

Beta 2 – July 20th, 2016

Beta 3 – This Release!

Stable – July 2016

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

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

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

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

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