Alpha Release: Xamarin.iOS 9.2.0, Cycle 6 Preview

BrendanZagaeskiBrendanZagaeski XamuraiUSForum Administrator, Xamarin Team Xamurai
edited October 2015 in Xamarin.iOS

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

Visual Studio Extension

  • Xamarin.VisualStudio_4.0.0.1505.msi (9ac5fb8)


  • monotouch- (f85a845)

Reason for release: Preview of the upcoming Cycle 6 feature release, in particular to gather as many additional customer bug reports as possible. (See the release blog and "Xamarin Release Cycles" for more information about "Cycles" and "Service Releases.")

Release notes:

Date published: See

NOTE: These Alpha versions have some known open bugs, and they have not yet completed the full suite of tests by the Xamarin QA team. The reason for this release is to gather as many additional customer bug reports as possible. (See also guideline #2 below.)

Previous versions, downgrading

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

Guidelines for this thread

  1. This first post will be updated regularly.

  2. If you find a new problem that is specific to this version:

    a. If you can share some specific error messages or can reproduce the problem consistently, please email the information you have so far to [email protected].

    b. If you only have a general description of the problem, you can post it directly on this forum thread so that hopefully a member of the Xamarin team or another user will recognize it and be able to help fill in some details.

Important changes

  • [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] [Visual Studio] [iOS] [Android] Support for OS X 10.9 Mavericks has been deprecated. The Cycle 6 builds now require OS X 10.10 Yosemite.

Important known issues in the Alpha builds

  • Non-public Bug 34065 - [XamarinVS] [iOS] "System.IO.EndOfStreamException: We could not fully deserialize the response" when attempting to open Interface.storyboard in a WatchKit app.

Remaining known issues from Cycle 5, with more common or severe issues near the top

  • Non-public Bug 30481, Bug 29557 - [Mono] [Android] [iOS] SqlConnection.GetSchema() fails with "SourceTable is required to be a non-empty string".

  • Bug 29745 - [iOS] Error due to duplicate symbols during native compilation for device: "duplicate symbol _monoeg_g_array_new" (and many similar messages). Workarounds: disable profiling under "Project Properties -> iOS Build", or if your app uses the -all_load linker flag (via either gcc_flags or LinkerFlags) try removing it.

EDIT Sep 02: Update for new Alpha builds. The Windows installers are now available.
EDIT Sep 10: Adjust the "guidelines" to mention [email protected].
EDIT Sep 18: Add iOS Bug 33124.
EDIT Sep 21: Update for Sep 18's new Alpha builds.
EDIT Sep 23: Adjust title to match new 9.2 Alpha build number.
EDIT Sep 24: Update for new Alpha builds.


  • NikiNiki ✭✭✭ BGMember ✭✭✭

    When trying to debug in simulator, I get the following exception in the Application Output pane and the simulator doesn't launch and the app is not deployed. I am running latest El Capitan beta (15A279b) and XCode 6.4 (6E35b) on MBPr 13".

      at <unknown> <0xffffffff>
      at (wrapper managed-to-native) MonoMac.ObjCRuntime.Class.class_addMethod (intptr,intptr,intptr,string) <0xffffffff>
      at MonoMac.ObjCRuntime.Class.RegisterMethod (System.Reflection.MethodInfo,MonoMac.Foundation.ExportAttribute,System.Type,intptr) <0x00105>
      at MonoMac.ObjCRuntime.Class.RegisterMethod (System.Reflection.MethodInfo,System.Type,intptr) <0x00119>
      at MonoMac.ObjCRuntime.Class.Register (System.Type,string,bool) <0x00667>
      at MonoMac.ObjCRuntime.Class.Register (System.Type) <0x000df>
      at MonoMac.ObjCRuntime.Runtime.RegisterAssembly (System.Reflection.Assembly) <0x003b3>
      at MonoTouch.Simulator.SimController.Initialize () <0x0008f>
      at MonoTouch.Simulator.SimController..ctor (string,System.Version,string,System.Collections.Generic.List`1<string>) <0x00053>
      at MTouch.Main2 (string[]) <0x05c9e>
      at MTouch.Main (string[]) <0x00024>
      at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
    Native stacktrace:
    Got a SIGSEGV while executing native code. This usually indicates
    a fatal error in the mono runtime or one of the native libraries 
    used by your application.
  • JohannesSjokvistJohannesSjokvist ✭✭ NOMember ✭✭

    Using the latest Alpha makes .xnb files added as BundleResource zeroed out in the project folder while building the project.
    Don't know if it is the same for all BundleResource, but it should not change original files while building?

    Before build:

    After build:

    It occurs while building when the build log reports:

    Copying file from '/Users/username/Library/Caches/Xamarin/mtbs/builds/MyCocosSharpApp/80530cb89674cb39b8f6ce9064aa15a6/Content/fonts/arial black-22.xnb' to '/Users/username/Library/Caches/Xamarin/mtbs/builds/MyCocosSharpApp/80530cb89674cb39b8f6ce9064aa15a6/bin/iPhoneSimulator/Debug/ black-22.xnb'
    2> Copying file from '/Users/username/Library/Caches/Xamarin/mtbs/builds/MyCocosSharpApp/80530cb89674cb39b8f6ce9064aa15a6/Content/fonts/arial black-33.xnb' to '/Users/username/Library/Caches/Xamarin/mtbs/builds/MyCocosSharpApp/80530cb89674cb39b8f6ce9064aa15a6/bin/iPhoneSimulator/Debug/ black-33.xnb'

    I am using VS 2015 with Xamarin.VisualStudio_4.0.0.1505.msi and Yosemite as build host with monotouch-

    I have not tried earlier Alpha releases...

  • JohannesSjokvistJohannesSjokvist ✭✭ NOMember ✭✭

    Here are the images before and after build in the project folder:
    Before build:

    After build:

    It builds without problems on the Mac... So this is something VS or build host related I think.

  • CheesebaronCheesebaron mod DKInsider, University mod
    edited October 2015

    For some reason in VS2015 the plugin can't seem to find any Simulators. The start simulator button works fine, but none are found even if I select iPhone or iPhoneSimulator solution configurations. Anyone else seeing this?

    Nevermind, versions have to match on both machines. No warning is shown when they are not in sync.

  • BrendanZagaeskiBrendanZagaeski Xamurai USForum Administrator, Xamarin Team Xamurai

    @JohannesSjokvist, thanks for the report! That issue should now be fixed on the latest Alpha version from today. (The new fix was tested against .php files and .ttf files, both of which had the same "resource-erasing" problem as the .xnb files from your report. If you continue to see any problems on the new Alpha, please do file a quick little bug report. Thanks!)

  • BrendanZagaeskiBrendanZagaeski Xamurai USForum Administrator, Xamarin Team Xamurai

    Cheesebaron, many thanks for the heads-up on the version mismatches. I will add a note to the QA team to test more version-mismatched scenarios. Hopefully that problem will mostly only affect these pre-Stable versions (since they have very close version numbers while also breaking backwards-compatibility from build to build).

  • BrendanZagaeskiBrendanZagaeski Xamurai USForum Administrator, Xamarin Team Xamurai
    edited October 2015

    Niki, many thanks for the report and apologies for dropping out of contact on this thread. The Xamarin.iOS 9.0 Stable release pulled me away from these Alpha threads for the past couple of weeks. Moving forward I will adjust my recommendation on these pre-Stable feature release threads to encourage direct bug reports. That will help distribute the follow-up investigation among the Xamarin QA and engineering teams and allow for more detailed discussion of specific symptoms.

    Possible next step: new Alpha version

    The described symptom with MonoMac.ObjCRuntime.Class.class_addMethod() appears to match non-public Bug 33469. A candidate fix for that issue is present in the latest Alpha release from today.

    If you like, feel free to try the latest Alpha builds to see if they improve the behavior on your system, and if not please do file a quick bug report. Thanks in advance!

  • BrendanZagaeskiBrendanZagaeski Xamurai 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.