Technical Bulletin: Stable Update for Windows Signing Certficate

We are releasing new Stable builds to update the certificate for our build signing step, as the old one is about to expire. These builds contain no functional changes from the previously released Stable builds, and thus should have no effect on projects made against the previous Stable builds.


Products Released

  • Xamarin Windows Installer

 

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

Stable Release: iOS 9.2 / Xcode 7.2 Support

We are releasing new Stable builds with support for the final iOS 9.2 API that Apple released yesterday as part of Xcode 7.2. Please note this release only supports the iOS 9.2 API, and does not include watchOS2 or tvOS support. Those will come to Stable at a later date (but are available as previews now)


Products Released


 

Stable Release: iPad Pro Device Support & VS Hang Hotfix

We are releasing new versions of our IDEs to the Stable channel today to provide device support for the iPad Pro. In addition, the Xamarin.VS build also includes a fix to address a hang that customers have been reporting after the Cycle 6 feature release.

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


Known Issues

  • [Xcode 7.1] Xcode 7.1 does not support iPad Pro icon sizes. Xcode 7.2 (beta) is required for iPad Pro icons to work as expected. This is an unusual situation. Because Xcode 7.2 is still in beta, this Xamarin Stable hotfix is is not fully tested against Xcode 7.2 or iOS 9.2.
  • [Xcode 7.1 and 7.2] Neither Xcode 7.1 nor Xcode 7.2 supports deploying iPad Pro launch image sizes (“… no longer support launch images and will not be adding the iPad pro launch image size to asset catalogs”,https://openradar.appspot.com/22915712). Launch graphics for the iPad Pro must be provided as storyboards or XIBs.
  • [Xamarin Studio] The asset editor for the iPad Pro launch images has no effect on the launch graphics displayed during app startup on simulator or device. This is an upstream issue due to a decision by Apple (see the preceding note about launch images in Xcode). The asset editor for these launch images is currently present in Xamarin Studio, but it will be removed in a future release unless Apple adds this functionality.
  • [Xamarin Studio] When using Xcode 7.2 beta you might see “Error MT0074: The maximum deployment target for iOS is 9.1 (current deployment target is 9.2). Please select an older deployment target in your project’s Info.plist.”
    • Workaround: adjustInfo.plist to set the deployment target to iOS 9.1 or lower. This error is a side effect of the fact that Xcode 7.2 itself is in beta (so the Xamarin Stable channel is not yet intended to have full compatibility).
  • [Xamarin.VS] iPad Pro devices are not displayed in the devices drop-down menu when the current StartUp Project is an “iPhone/iPod” project. This will be corrected in a future release.
  • [Xamarin.VS] In some environments the asset catalog editor might not display the “167.0×167.0” “iPad Pro App” entry as expected. This issue is under investigation. Temporary workaround: add the image to the .appiconset folder by hand (this directory is located in the Resources directory of the project, visible in Explorer), then replace “iPadProIcon.png” in the following snippet with the name of the file you added to the .appiconset folder, and then paste the snippet into theimages array in the text of the Contents.json file.
{
  "filename": "iPadProIcon.png",
  "size": "83.5x83.5",
  "scale": "2x",
  "idiom": "ipad"
}

Products Released


Upcoming Release Dates

Stable – This release!

Preview: WatchOS 2.0& tvOS Third Preview

We are releasing an updated preview with support for watchOS 2 (simulator only) and tvOS (simulator and device), now available for Visual Studio. These new builds also have Bitcode support for tvOS applications, and support for tvOS binding projects. Be sure to check out the associated documentation tvOS.

As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla. You can also jump into the discussions on the forum thread posted below.


Known Issues

  • [Xamarin.iOS] – watchOS 2 WatchKit Extension shouldn’t be an execution target.
  • [Xamarin.iOS] – watchOS 2 applications currently only work on watch simulators.
  • [Xamarin.iOS] – Bitcode support is not available for watchOS 2.0 device builds.
  • [Xamarin.iOS] – watchOS debugging is supported only for default mode in watch simulator.
  • [Xamarin.iOS] – watchOS 2 and tvOS APIs are not final, some types might be missing or unavailable.
  • [Xamarin.iOS] – tvOS asset catalog editor is not fully implemented.
  • [Xamarin.VS] – tvOS icon set in asset catalog won’t show up in simulator.
  • [Xamarin.VS] – No binding project support for tvOS.
  • [Xamarin.VS] – This preview does not currently include support for the Xamarin.iOS designer for tvOS or watchOS 2.
  • [Xamarin.VS] – BundleIdentifiers of Watch App Extension, Watch App and companion id have to be set manually.
  • [Xamarin.VS] – Watch App reference in iOS Project -> References has a yellow triangle.
  • [Xamarin.VS] – Incremental builds are always turned off for tvOS apps.
  • [Xamarin.VS] – WatchOS2.0 template is missing asset catalog for icons and launch images.
  • [Xamarin.VS] – No Glance and Notification mode debugging support in WatchOS 2 applications.

Products Released

Stable Release: Cycle 6 Service Release 0

We are releasing the earlier preview of our first Service Release to Cycle 6 to the Stable channel. 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.

Products Released

  • Xamarin Studio 5.10.1.3
    • Release Notes
    • Forum Thread – Stable 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
      • 36189 – Fixed an issue with archiving for publishing generating the wrong value for CloudKit entitlement.
  • Xamarin for Visual Studio 4.0.0.1697
    • Release Notes
    • Forum Thread –Stable 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 – November 24th, 2015

Stable – This release!

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

Preview: Xamarin Inspector 0.3.2.3

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.

The Xamarin Inspector is available on both Windows with Visual Studio and on Mac OS X with Xamarin Studio. Inspector is now supported on the recently announced Xamarin 4. Updating to the latest stable Xamarin releases across the board is the only requirement to begin using the Inspector preview product! Once you have the RC installed, you can download the Inspector from the links below, or from the supporting documentation page.


Products Released

Stable Release: Cycle 6 Final

We are releasing our final Cycle 6 to the Stable channel. These final builds contain all fixes from the previous releases, along with new feature and tons of improvements. Be sure to check out our blog post, and the product release notes below.

If you are used to the updater channels in Xamarin Studio and/or Visual Studio, simply switching to the Stable channel and getting the latest content will give you the final builds. We’ve also updated the standard installers, which will install the builds 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 Stable channel).

Mac Installer  |  Windows Installer

Please note, to use final builds to develop iOS applications in Visual Studio, you’ll need to install them 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 products, please log a bug report.


Known Issues

  • Please see product release notes for known issues. 

Products Released


Cycle 6 Release Dates

Beta Preview: Cycle 6 Preview Update – Release Candidate 3

We are releasing a slightly updated preview of Cycle 6 to the Beta channel. These updated RCs fix a known issue with Xamarin Inspector compatibility from RC2. The Xamarin.Android, Xamarin.Mac, and Mono Framework remain unchanged from the previous release.

If you are used to the updater channels in Xamarin Studio and/or Visual Studio, simply switching to the Beta channel and getting the latest content will give you the RC3 series of builds. To make it as easy as possible for Xamarin developers to participate in this RC, we’ve also prepared special versions of our installers which will install the new RC3 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 Beta channel).

Mac Installer  |  Windows Installer

Please note, to use RC3 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 RC3 products, please log a bug report.


Known Issues

  • [Xamarin Studio] – Holding down Command+Z batches undo actions. (Undo is not executed until key combination is released.)

Products Released


Cycle 6 Release Dates