Alpha Release: Xamarin.Mac 2.0.2, Cycle 5 – Service Release 2

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited June 2015 in Xamarin.iOS

This thread has now been closed to direct all further updates about this service release onto the new Beta release thread:

For anyone who has been commenting on this thread, feel free to continue the conversation in that new thread.

Released versions:

  • xamarin.mac- (03fdc45)
  • MonoFramework-MDK- (198235d)

Reason for release: Additional bug fixes for the "Cycle 5" Stable Release on April 29. (See the release blog for a short description of "Cycles" and "Service Releases.")

Date published: See

NOTE: Alpha versions have not yet completed the full suite of tests by the Xamarin QA team. That said, customer reports of any regressions (or bugs that are incorrectly marked fixed) are still much appreciated, even if the problem would have eventually been caught during the full QA testing process.

Previous versions, downgrading

You can downgrade back to the current Stable version by switching updater channels.

Older versions (from before April 29)

If needed, you can downgrade back to older versions (from before April 29) by manually reinstalling each old package. See the "Previous versions, downgrading" section on the previous Stable release thread for the older downgrade links.

Guidelines for this thread

  1. This first post will be updated regularly.

  2. Hopefully this thread will help answer "what might break if I update to this release?"

  3. If you find a new problem that is specific to this version, please file a bug report (if this link redirects to the top-level page the first time you click it, try clicking it once more).

  4. Please discuss older bugs that are unchanged in this release compared to the previous Stable version in Bugzilla instead.

  5. Of course for questions and discussions about topics other than bugs, feel free start new forum threads.


  • DanSmith.1531DanSmith.1531 USMember ✭✭

    What exactly is in 2.0.2 of Xamarin.Mac? The most accurate link that I could find ( only has information about Xamarin.Mac 2.0.1...

    I was under the impression that full system.servicemodel support is coming in this some bug fixes?

  • ChrisHamonsChrisHamons USForum Administrator, Xamarin Team Xamurai

    There should be zero changes between 2.0.1 and 2.0.2 from the XM viewpoint. Since Xamarin.Mac and Xamarin.iOS share infrastructure, and service releases release all products, sometimes minor bumps like that happen.

    I should have updated the documentation to match. Apologies (fixing now).

    The System.ServiceModel / XM 4.5 changes are still in work. Fixing it correctly took an order of magnitude more work than originally expected. Once they land somewhere public, I'll make a post at least explaining a work around if they don't make a service release (and thus are 2.2).

    The bar for bug fixes in a service release is rather high. They have to be critical enough to warrant the risk of breaking other people by introducing regressions when we make changes. Bugs of a less critical nature have to wait for a standard release.

  • RogerMontgomeryRogerMontgomery USMember

    The Garbage Collector is still not working in your Alpha.

    On March 24, I sent Xamarin a simple/trivial program that demonstrates that your Garbage Collector does not work.
    It is now the middle of June, and I have update to Xamarin.Mac 2.02.17 (Business Edition) and have Xamarin Studio version 5.9.3 (build1). I rebuilt the simple test and was sad to see the bug still exists.

    I was hoping that since you had the example, somebody would trace it down, find the cause, and fix it. But what I got instead was a response that says it will be fixed in Cycle 6.

    Basically Xamarin.Mac is not usable unless I manually insert a Dispose() on each object, and still remains unusable because this causes embarrassingly slow performance.

    If this was assumed to be fixed within this Alpha, then something is wrong with your bug resolution procedures.
    A working Garbage Collector is so fundamental, the symptoms of this problem are likely pervasive throughout your products.

  • ChrisHamonsChrisHamons USForum Administrator, Xamarin Team Xamurai

    @RogerMontgomery So, I understand your frustration. Let me try to break down what's going on for you:

    • The issue you reported is a one in our mono base class library, not Xamarin.Mac. While this doesn't change anything from you perspective, it does explain why I didn't see this bug.
    • Just to clarify, a memory leak != the garbage collection does not work. It means we have a bug, which is leaking either native or managed memory references. The garbage collector is collecting normal memory use fine, it is just a bug in our class libraries (in System.Data it appears).
    • Rodrigo, the lead of the runtime team, took a look at this issue and noted that it if/will be fixed in the next major release, which is internally called cycle 6.
    • Since it is fixed by using more of Microsoft's open source BCL code, it would be difficult to back port to Cycle 5 (Stable) safely, due to the possibly of introducing regressions.
    • It is not safe to assume that given bug will be fixed in a certain release unless explicitly told by somebody from Xamarin. Based on what other bugs are reported, how critical they are, how many people they affect, how scary their fixes entail, and other factors a given bug may or may not be fixed in a given release.
    • Since you have a business license, if you are reporting an issue that is blocking you you should be using . This is our channel for business+ customers to report blocking issues, and for us to see if we can get you a work around / timeline on fixes. (There is a yellow link/bar at the top of bugzilla).
  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    This thread has now been closed to direct all further updates about this service release onto the new Beta release thread:

    For anyone who has been commenting on this thread, feel free to continue the conversation in that new thread.

This discussion has been closed.