Category Archives: Alpha

Releases specifically targeted for the Alpha Updater Channel.

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

Evolve Keynote Releases!

UPDATE – We’ve added a new build of the Xamarin Profiler that is compatible with the Cycle 7 builds noted below. 

 

As you may have heard from Miguel during the Evolve 2016 Keynote session, we’re releasing a number of new builds to our Alpha and Beta channels, with many new features available to sample right now.

 

 


WEB PREVIEW – XAMARIN WORKBOOKS / INSPECTOR


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

 

 


WEB PREVIEW – iOS SIMULATOR (FOR WINDOWS)


We are releasing our first 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.

 

 


WEB PREVIEW – XAMARIN PROFILER


Xamarin Profiler preview 0.33 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.


Products Released

 

 


ALPHA RELEASE – CYCLE 8  FIRST PREVIEW


Our first preview of our newest upcoming feature release (called Cycle 8) can be downloaded from the Alpha channel.

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 8, 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 8 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 Alpha channel.


Cycle 8 Alpha 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.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

Cycle 8 Alpha Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 8 Alpha – This Release!

Cycle 8 Beta – Fall 2016

Cycle 8 Stable – Fall 2016

 

 


BETA RELEASE – CYCLE 7 RELEASE CANDIDATE


Our next major feature release, called Cycle 7, has had some Alpha and Beta previews out for awhile, but now we’re putting our first Release Candidate to the Beta Channel. We’re really close to finalizing this release, but need your help to hammer on these RCs and shake out any last issues that are hidden away.

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.


Cycle 7 Release Candidate 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.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

 

Cycle 7 Release Candidate Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 7 Alpha – March 10th, 2016

Cycle 7 Alpha 2 – March 15th, 2016

Cycle 7 Beta – April 11th, 2106

Cycle 7 Release Candidate – This Release!

Cycle 7 – May 2016

 

Beta: Cycle 7

We are releasing a Beta 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.


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 – This Release!

Stable – April/May 2016

Alpha Preview 2: Cycle 7

Update 1 – Bumped Xamarin.iOS from 9.8.0.58 to 9.8.0.156. This adds support for Apple iOS 9.3 / Xcode 7.3. 


We are releasing a new Alpha preview of our next major feature release, called Cycle 7. 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.


Known Issues

  • [Xamarin Studio w/ F# Add-in] – Error when creating an F# Android template on Windows. This should still function correctly on Mac.
  • [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.
  • [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.

Products Released


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – This Release!

Beta – March 2016

Stable – Late March / Early April 2016

Alpha Preview 1: Cycle 7

Update 1 – Bumped Xamarin.iOS from 9.7.0.331 to 9.8.0.43, and Xamarin.Mac from 2.7.0.331 to 2.8.0.42. Both bumps add TLS 1.2 cryptography support.

Update 2 – Bumped Xamarin Studio from 6.0.0.4520 to 6.0.0.4761. Various additional fixes. 

Update 3 – Bumped Xamarin.VS from 99.0.0.1562 to 4.1.0.87. Various additional fixes, corrects version numbering to be in line with previous Xamarin.VS releases. 


We are releasing an Alpha preview of our next major feature release, called Cycle 7. There are a number of new features and bugfixes included in this release, most notably the rollout of the Dark Skin theme for Xamarin Studio. 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.

NOTESome customers who are using targeting System Mono under Unified, using Classic Xamarin.Mac (XamMac.dll), or PCls may run into build issues or crash on launch. They may want to move off the Alpha channel at this time.


Known Issues

  • [Xamarin.VS] – A build error may occur when trying to build WatchKit Applications in Notification Mode with VS 2015.
  • [Xamarin.VS] – A build error may occur when trying to build WatchKit Applications in VS 2012/2013
  • [Xamarin.VS / iOS Designer] – Interface.Storyboard for WatchKit Applications will not open in VS 2012/2013.
  • [Xamarin.VS / iOS Designer] – Bottom section of the View Controller is appearing white instead of grey.
  • [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 Studio w/ F# Add-in] – Error when creating an F# Android template on Windows. This should still function correctly on Mac.
  • [Xamarin.Mac] – When running the Xamarin.Mac unified template project with the target Framework set to “Unsupported”, the popup “Could not connect to the debbuger” may appear.
    • Potential Workaround – Downgrade the Mono framework version available in our Stable channel.
  • [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.

Products Released


Upcoming Release Dates

Alpha – This Release!

Beta – March 2016

Stable – Late March / Early April 2016

Alpha Preview 3: Cycle 6 Service Release 1

We are releasing an updated Alpha preview of our next Service Release to Cycle 6. This is a much bigger service release, and should address a vast majority of the issues we’ve seen reported by the community after the release of Cycle 6. The issues noted below as addressed are not the only ones fixed with this release, so make sure to check out the product release notes to see all the fixes provided with this preview.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Products Released

  • Xamarin Studio 5.10.2.53
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 32494 – Fixed an issue where Xamarin Studio would always compile using C# 5, leading to various errors (often syntax errors) if the project included C# 6 features.
      • 35977 – Fixed an issue where Japanese characters could not be typed into the text editor.
      • 34250 – Fixed an issue where all of the menu items would become disabled after certain project operations.
  • Xamarin for Visual Studio 4.0.1.74
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • Fixed the “iOS IPA -> Include Artwork in IPA” checkbox in the project properties so that it correctly saves changes to the value.
      • Added a candidate fix for an issue where breakpoints in class libraries were not being resolved (non-public Bug 35691).
      • 36117 – Fixed an issue where certain distribution identities and provisioning profiles did not appear in the iOS project settings.
      • Fixed an issue with WatchKit applications in Notification mode failing with “System.ArguementOutOfRangeException”.
  • Xamarin.iOS 9.4.1.23
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 35786 – Fixed an issue where the iOS build process could run out of file descriptors when building large projects, leading to errors such as “error : Could not strip assembly”.
      • 30698 – Fixed an issue with certain 32-bit floating point operations causing crashes on 32-bit devices.
      • 36238 – Fixed an issue with True/False status of the “iOS IPA -> Include Artwork in IPA” not showing the correct value unless the text of the .csproj file explicitly included the “IpaIncludeArtwork” property.

Upcoming Release Dates

Alpha – December 8th, 2015

Alpha (w/ iOS 9.2 & Xcode 7.2 support) – December 10th, 2015

Alpha 2 – December 18th, 2015

Alpha 3 – This release! 

Beta – Mid January 2016

Stable – Late January 2016

Alpha Preview: Cycle 6 Service Release 1

We are releasing an updated Alpha preview of our next Service Release to Cycle 6. This is a much bigger service release, and should address a vast majority of the issues we’ve seen reported by the community after the release of Cycle 6. The issues noted below as addressed are not the only ones fixed with this release, so make sure to check out the product release notes to see all the fixes provided with this preview. All fixes included in Service Release 0, and the previous Alpha for Service Release 1 are included in this preview, so you should not experience any regression with previous fixes such as Xamarin.VS hanging.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Known Issues

  • [Xamarin.VS/WatchOS] – Attempting to run WatchKit applications in Notification mode fails with “System.ArgumentOutOfRangeException”.
  • [Xamarin.iOS] – Certain 32-bit floating point operations cause crashes on 32-bit devices. Partial workaround: Enabling “Project Options -> iOS Build -> Perform all 32-bit float operations as 64-bit float” avoids the problem.
  • [Xamarin.VS] – If the text of the .csproj file does not explicitly include the “IpaIncludeArtwork” property, then the “iOS IPA -> Include Artwork in IPA” property panel will incorrectly show the value as True, when in fact it is False.
    • Workaround: un-check the checkbox and save the project properties, then re-check the checkbox and again save the properties.

Products Released

  • Xamarin Studio 5.10.2.49
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 32494 – Fixed an issue where Xamarin Studio would always compile using C# 5, leading to various errors (often syntax errors) if the project included C# 6 features.
      • 35977 – Fixed an issue where Japanese characters could not be typed into the text editor.
      • 34250 – Fixed an issue where all of the menu items would become disabled after certain project operations.
  • Xamarin for Visual Studio 4.0.1.60
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • Fixed the “iOS IPA -> Include Artwork in IPA” checkbox in the project properties so that it correctly saves changes to the value. (Note that one of the remaining known issues is also related to this checkbox. That issue will be fixed in a future build of this service release.)
      • Added a candidate fix for an issue where breakpoints in class libraries were not being resolved (non-public Bug 35691).
      • 36117 – Fixed an issue where certain distribution identities and provisioning profiles did not appear in the iOS project settings.

Upcoming Release Dates

Alpha – December 8th, 2015

Alpha (w/ iOS 9.2 & Xcode 7.2 support) – December 10th, 2015

Alpha 2 – This release!

Beta – Early January 2016

Stable – Mid-Late January 2016

Alpha Preview: Cycle 6 Service Release 1

UPDATE – Support for Apple iOS 9.2 / Xcode 7.2 has now been added to the Alpha channel builds. Please update your Xamarin.iOS (and if necessary Xamarin.VS) to the latest Alpha channel builds get this support. 

We are releasing an Alpha preview of our next Service Release to Cycle 6. This is a much bigger service release, and should address a vast majority of the issues we’ve seen reported by the community after the release of Cycle 6. The issues noted below as addressed are not the only ones fixed with this release, so make sure to check out the product release notes to see all the fixes provided with this preview. All fixes included in Service Release 0 are included in this preview, so you should not experience any regression with previous fixes such as Xamarin.VS hanging.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Known Issues

  • [Xamarin.VS/WatchOS] – WatchKit template sometimes causing failures with Xamarin.VS builds of Watch Apps.
  • [Xamarin.VS] – If the text of the .csproj file does not explicitly include the “IpaIncludeArtwork” property, then the “iOS IPA -> Include Artwork in IPA” property panel will incorrectly show the value as True, when in fact it is False.
    • Workaround: un-check the checkbox and save the project properties, then re-check the checkbox and again save the properties.
  • [Xamarin.VS (36117)] – Certain distribution identities and provisioning profiles do not appear in the iOS project settings. See the bug for possible workarounds.
  • [Xamarin Studio (35977)] – Certain characters (including Japanese and Chinese characters) cannot be typed into the text editor.
  • [Xamarin Studio (34250)] – After certain project operations, all of the menu items in Xamarin Studio will become “disabled” (grey text).
  • [Xamarin.Mac (35851)] – F# projects fail to build due to “The referenced or default base CLI library ‘mscorlib’ is binary-incompatible with the referenced F# core library”.
    • Workaround: Use this build for now. The next full set of Alpha updates should contain this fix.

Products Released

  • Xamarin for Visual Studio 4.0.1.37
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • Fixed the “iOS IPA -> Include Artwork in IPA” checkbox in the project properties so that it correctly saves changes to the value. (Note that one of the remaining known issues is also related to this checkbox. That issue will be fixed in a future build of this service release.)
      • Added a candidate fix for an issue where breakpoints in class libraries were not being resolved (non-public Bug 35691).

Upcoming Release Dates

Alpha – December 8th, 2015

Alpha (w/ iOS 9.2 & Xcode 7.2 support) – This release!

Beta – Early January 2016

Stable – Mid-Late January 2016

Alpha Preview – Cycle 6 Service Release 0

 We are releasing an Alpha preview of our first Service Release to Cycle 6. This is smaller release, meant to quickly address some of the most commonly reported issues we’ve seen from the community after the release of Cycle 6.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Known Issues

**NOTE** – For any hangs observed in Xamarin.VS, please follow the steps here to collect the call stack of the Main Thread. If the call stack does not include “GetAdditionalResourcesFromAssemblies”, please attach it to a new bug report. This will aid us in investigating these fixes, hopefully speeding up the release of patches to address them. 

  • [Xamarin.VS (36185)] – Hang (GUI lockup, freeze) when opening or working on a solution that contains an Android project. Known temporary workaround: delete the hidden .suo file or .vs folder in the solution directory.
  • [Xamarin.VS] – Error ‘Disallowed path(“iTuneMetadata.plist”) found’ on .ipa uploads preventing submission to App Store.
  • [Xamarin Studio/Xamarin.iOS] -Archiving for Publishing generates the wrong value for CloudKit entitlement, thus preventing distribution.

Products Released

  • Xamarin Studio 5.10.1.1
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 0
    • Issues Addressed:
      • Fixed an issue with the iOS Designer where some xib files would not open. (“This File Format is not supported”)
      • Fixed an issue with the iOS Designer where iOS versions 9.0 or higher would throw an exception when translatesAutoresizingMaskIntoConstraints=NO in some widgets. (“One or more errors occurred… at Parse <uknown offset> … at LoadXmlCore <uknown offset>”)
      • Fixed an issue with the iOS Designer where the z-order was not rendering correctly with Storyboards
  • Xamarin for Visual Studio 4.0.0.1694
    • Release Notes
    • Forum Thread – Alpha Release: Xamarin 4, Cycle 6 – Service Release 0
    • Issues Addressed:
      • 35859 – Fixed an error “vs0192Ø is an invalid ClientId. It must contain only numbers and letters” when attempting to connect to the Mac build host if the Windows user directory contains accented (non-ASCII) characters.
      • 36190 – Fixed an error “Could not write lines to file “obj\Debug\MyLib.csproj.FileListAbsolute.txt”” when building moderately large PCL projects as part of an iOS or Android app.
      • Added an explicit error message “Building from a network share path is not supported at the moment” when attempting to build from an unmapped network share folder on Windows (any path beginning with \\). This is a change to help clarify certain causes of “The “UnpackLibraryResources” task failed unexpectedly”. In its current form, this change will block any attempt to build on a network share that has not been mapped to a drive letter or local folder. This strict rule might be loosened again in the future.

Upcoming Release Dates

Alpha – This release!

Beta – Late November / Early December 2015

Stable – December 2015

Alpha Release: Cycle 6 Preview Update – Release Candidate 1

We are releasing a updated preview of Cycle 6 to the Alpha channel. These updated RCs provide a slew of additional fixes on top of the previous builds, in addition to support for Xcode 7.1. There are still some issues remaining, but the quality is much improved since the initial RC, thanks in great part to community input. Thank you!

If you are used to the updater channels in Xamarin Studio and/or Visual Studio, simply switching to the Alpha channel and getting the latest content will give you the RC1 series of builds. To make it as easy as possible for Xamarin developers to participate in this first RC, we’ve also prepared special versions of our installers which will install the new RC1 build on your Mac and Windows machine if nothing has been previously installed. (Note – if you have gotten web previews of newer Xamarin Platform builds, the installer will not update and you should use the updater in the IDE against the Alpha channel).

Mac Installer  |  Windows Installer

Please note, to use RC1 to develop iOS applications in Visual Studio, you’ll need to install the release on both your Mac and Windows workstations.

The biggest change with the Cycle 6 builds is an overhaul of how Xamarin builds iOS projects on your Mac from Visual Studio. If you happen to experience issues with any of the RC1 products, please log a bug report


Known Issues

  • [Xamarin Studio] – gtk may crash during drag and drop actions.
  • [Xamarin Studio] – Xamarin Studio shows pop up error on creating iOS template projects.
  • [Xamarin Studio] – Holding down Command+Z batches undo actions. (Undo is not executed until key combination is released.)
  • [Xamarin Studio] – iOS extension projects do not compile.
  • [Xamarin Studio] – Adding a new Action to a Controller does not update corresponding *.design.cs file
  • [Xamarin.VS] – Certain iOS projects may have increased build times.
  • [Xamarin.VS] – In some scenarios, iOS applications install, but do not launch from Visual Studio, you must tap on the application manually to launch.
  • [Xamarin.VS/Xamarin.iOS] – Debugger does not stop on breakpoints in async RelayCommand in PCL projects
  • [Xamarin.Mac] – NSOutlineViewDelegate is missing one exported method, leading to applications not displaying contents for the cells.

Products Released


Cycle 6 Release Dates

  • Alpha – August 26th, 2015
  • Alpha 2 – September 2nd, 2015
  • Alpha 3 – September 19th, 2015
  • Alpha 4 – September 24th, 2015
  • RC0 / Alpha 5 – October 6th, 2015
  • RC1 / Alpha 6 – This release!
  • Future RC(s) – October/November 2015
  • Stable – Fall 2015