Beta Release: Xamarin 4, Cycle 6 – Service Release 2

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited March 2016 in General

This thread has now been closed to direct all further updates about this release onto the latest announcement:

Release Blog post:

This is a small bugfix release. It addresses several of the known issues from the Xamarin 4, Cycle 6 Feature Release. See the Release Blog post for more details.

Fixed bugs

You can view the list of bugs addressed by this Beta version of the service release using the following Bugzilla query:

Remaining known issues

You can view all of the remaining bugs that have been reported against the Xamarin 4 ("Cycle 6") but that are not yet fixed in "Cycle 6 – Service Release 2" using the following Bugzilla query:

Bug filing

If you find any new issues in this release compared to the current Stable versions or the previous "Xamarin 3" versions that you would like the Xamarin team to investigate, please do file a quick bug report, and then feel free to add a note on this thread with the bug number. Thanks!

Note that Beta versions have not yet completed the full suite of tests by the Xamarin QA team. That said, customer bug reports are still much appreciated, even if the problem would eventually be caught by the remaining QA tests.

Previous versions, downgrading

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

Release info


  • Xamarin.VisualStudio_4.0.1.145.msi (f869dba) Release notes forthcoming
  • XamarinStudio- (ac9b7fc) Release notes forthcoming


  • XamarinStudio- (ac9b7fc) Relese notes forthcoming
  • monotouch- (58ba2bc) Relese notes forthcoming
  • mono-android-6.0.2-1.pkg (46c3f7e) Release Notes
  • xamarin.mac- (0fd7a23) Release notes forthcoming
  • MonoFramework-MDK- (832de4b) Release notes forthcoming

Release Blog post:

See the first entry in the release blog and "Xamarin Release Cycles" for more information about "cycles," "service releases," and "feature based releases."

Compatibility notes

(These are the same as for the initial Cycle 6 Feature Release.)

  • [XamarinVS] The Cycle 6 builds of XamarinVS now require Visual Studio 2012 or higher. Following along with the end of Mainstream Support for Visual Studio 2010 by Microsoft, Cycle 6 is not compatible with VS 2010.

  • [iOS] The Cycle 6 builds now require Xcode 7 or higher. For example, attempting to build an iOS app for device using Xcode 6.4 will now fail with "Native linking failed, undefined symbol: ___divdc3".

  • [Xamarin Studio] [XamarinVS] [iOS] [Android] [Xamarin.Mac] Support for OS X 10.9 Mavericks has been deprecated. The Cycle 6 builds now require OS X 10.10 Yosemite.

EDIT Mar 04: Add Xamarin.Mac and update Xamarin.iOS, XamarinVS, and Mono versions.


  • BradChase.2654BradChase.2654 USMember ✭✭✭
    edited March 2016

    @BrendanZagaeski Brendan, where are we on defect 36080? We really need to upgrade but are still stuck on version 3 because we CANNOT use WCF. WCF is COMPLETELY broken in 4. This is unacceptable and needs to be addressed.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited March 2016

    BradChase.2654, "Cycle 6 – Service Release 2" ended up being a bit of an unusual release because it was added primarily as a way to get some fixes that were already "ready to go" onto the Stable channel while the larger Cycle 7 release is still in testing.

    In fact, I included Bug 36080 as one of a handful of bugs I passed to engineering as a "Support team wish list for Cycle 6 – Service Release 2," mentioning that it is one of the remaining regressions from Xamarin 4 ("Cycle 6") that has the highest number of customer reports. But unfortunately, in part due to the "special" expedited style of this service release, that bug fix won't make it into this service release.

    That said, that bug is now at the top of my "wish list" for Cycle 7.

    (Also apologies for the lack of reply on your similar comment on the Cycle 7 thread. Your comment there helped remind me to add the bug to my "wish list.")

  • BradChase.2654BradChase.2654 USMember ✭✭✭

    @BrendanZagaeski Thank you for the reply. It is becoming a thorn in our side as we have a release coming up VERY shortly and yet we still cannot compile on iOS because of the differences from 3 to 4. Without this functionality in and tested we are sitting ducks. The pressure is on! Thanks for the info though, hopefully this is in there soon!

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    This thread has now been closed to direct all further updates about this release onto the latest announcement:

This discussion has been closed.