Beta Release: XamarinVS 3.11.1450, Service Release for Xamarin.iOS 9.0

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited October 2015 in Visual Studio

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


  • Xamarin.VisualStudio_3.11.1450.msi (75e86d0)

Mac Build Host

  • monotouch- (1d27ac2)

Reason for release: Bug fixes for Xamarin.iOS 9.0 and the corresponding IDE packages.

Date published: See

NOTE: This is a bugfix release for the Xamarin.iOS 9.0 feature release (that release contained a large number of changes compared to the previous Stable version). As usual, Beta 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.

Guidelines for this thread

  1. This first post will be updated regularly.

  2. The goal of this thread is to help answer "what might break if I update to this release?"

  3. 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.

Fixes for known issues from recent release threads

  • Bug 33124 - [iOS] Certain libraries that were compiled by the Microsoft C# 5 compiler (VS 2013) cause "error MT2001: Could not link assemblies. Reason: Can't not find the nested type" during the linking phase of the Xamarin.iOS build process. (For example, any library compiled by VS 2013 that uses an async lambda within a constructor will hit this problem.) Unfortunately this problem affects several existing NuGet packages and Components.

  • Non-public Bug 34163 - [XamarinVS] [iOS] Error similar to: "System.IO.FileNotFoundException: Could not find file "/Users/macuser/Library/Caches/Xamarin/mtbs/builds/Unified.ClassLibrary.iOS1/242ab4564ac5785ce41fda606805edad/obj/Debug/ibtool/IPhoneViewController1.nib"" or "System.IO.FileNotFoundException: Could not find file "/Users/macuser/Library/Caches/Xamarin/mtbs/builds/Unified.ClassLibrary.iOS1/242ab4564ac5785ce41fda606805edad/obj/Debug/optimized/button_black_135x40.png"" when class library assembly name includes dot "." characters. Temporary workaround: Change "Project properties -> Application -> Assembly name" so that it includes no "." characters. Change the project name to match the modified assembly name.

  • Non-public bug 34202 - [XamarinVS] [iOS] Error similar to: "The OutputPath property is not set for project 'iOSClassLibrary1.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='iPhone'." after adding an iOS class library to a solution where an iOS app project is set as the startup project. One temporary workaround: Open the iOS class library .csproj in a text editor and delete all occurrences of the following 2 strings: "|$(Platform)", "|AnyCPU".

  • Non-public Bug 34144 - [XamarinVS] [iOS] Redeploying an app that references a library project without first cleaning the library project causes all resources to be replaced with 0-byte files if any of the resource files was modified. Partial workaround: Clean the library project before redeploying the app.

  • Bug 34220 - [iOS] The new iOS 9 ReplayKit APIs currently hit an error: "Cannot cast from source type to destination type".

  • Bug 34186 - [iOS] "MTOUCH: error MT5212: Native linking failed, duplicate symbol" and "Duplicate symbol in: ... libmonotouch-sgen.a" errors appear if using the -all_load linker flag under "Additional mtouch arguments". Partial workaround: remove the -all_load liker flag.

  • Non-public Bug 33706 - [iOS] Storyboards produce many warnings similar to: "/Applications/ 2015-09-04 18:01:03.651 Interface Builder Cocoa Touch Tool[72838:13678534] CoreUI: CUICatalog: couldn't get 'kMGArtworkGraphicsFeatureSetClass' from MGCopyAnswer got '{ (CollectionView)". These warnings can be ignored for now. The problem is that Xamarin is currently surfacing diagnostic messages from ibtool that are not surfaced by the default Xcode build process.

Remaining known issues

  • Non-public Bug 34173 - [iOS] [Designer] Storyboard fails to load in designer with "There was a problem parsing the XML" for storyboards that contain a <constraint> element with an attribute of multiplier="0". Workarounds: Open the storyboard in Xcode Interface Builder and re-save it from there. Or edit the storyboard in a text editor and manually remove the multiplier="0" attribute.

  • Bug 34205 - [iOS] Changes to WatchKit app storyboards do not appear on the simulator after the first deployment. Workaround: Manually delete the app from the iPhone simulator before re-deploying.

  • Non-public Bug 34198 - [XamarinVS] [iOS] Visual Studio sometimes disallows loading Xamarin projects with: "An equivalent project (a project with the same global properties and tools version) is already present in the project collection". Temporary workaround: Attempt to load the project again, or if that still fails quit and reopen Visual Studio and then reload the project.

  • Non-public Bug 33819 - [XamarinVS] [iOS] Attempting to stop a WatchKit app in Glance mode does not stop the app. Workaround: Kill the app manually.

  • Non-public Bug 33695 - [iOS] Attempting to install a new version of an application on device using a different provisioning profile from the original install is not supported by Xcode 7. Unfortunately, the corresponding error message produced by Xamarin does not describe the problem clearly: "error MT1006: Could not install the application ... on the device ... Application Verification Failed Error (error: 0xe800003a)." This error message will be improved in a future release. Workaround: Manually uninstall the app from the device and try installing it again.

  • Non-public Bug 33880 - [Upstream] [iOS] Attempting to stop a WatchKit app in Notification mode does not stop the app. (The same problem occurs with an Objective-C or Swift app deployed from Xcode, so this is an upstream issue.) Workaround: Kill the app manually.

  • Non-public Bug 33888 - [XamarinVS] [iOS] VS 2010 only. Opening a second Xamarin.iOS solution when already connected to the build host causes VS to disconnect from the build host. The user must refresh the connection manually via the "Refresh build server info" button.

Remaining known issues from older release threads

The remaining known issues from older release threads ("Cycle 5 – Service Release 4" and earlier) are unchanged compared to the current Stable channel version.


  • DRRDRR USMember

    Thank you! This fixed the issues I encountered in build 1443 with images in class library projects. Using XamarinVS is especially important now because we have cross-platform code making use of C# 6.0 features and building directly on the Mac results in internal compiler errors due to bug 32054. That bug is fixed in the alpha channel and building iOS directly on the Mac works in alpha, but I wasn't able to get XamarinVS working in alpha yet (or building Android in VS in alpha).

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited October 2015

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

This discussion has been closed.