Category Archives: Stable

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!

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!

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

Stable Release: Xamarin.iOS Hotfix for watchOS 1 App Submission

We are releasing new Stable builds to address the issue noted in yesterday’s technical bulletin regarding submissions of watchOS 1 apps built using WatchKit not succeeding. In addition a newer Xamarin.iOS build, we are also providing a new Xamarin.VS build compatible with this updated Xamarin.iOS. The current stable version of Xamarin Studio will work with this updated Xamarin.iOS.

Both of these builds are available through the IDE updater from the Stable channel. For Visual Studio users, please note you will need to update both your Mac Host and your VS environment with the Xamarin.iOS and Xamarin.VS builds respectively.


Products Released

 

Stable Release: iOS 9.1 / Xcode 7.1 Support & El Capitan Fixes

We are releasing new Stable builds to address some issues with OSX El Capitan compatibility with the previous Stable builds, and also support the final iOS 9.1 API that Apple released last week as part of Xcode 7.1. Please note this release only supports the iOS 9.1 API, and does not include watchOS2 or tvOS support (though you can check out our previews for those here).


Products Released


Upcoming Release Dates

Alpha – N/A

Beta – October 22nd, 2015

Stable – Today!

Xamarin.Android Hotfix for Stable Channel to address “Could not load machine data” error

We are releasing an updated Xamarin.Android build to the Stable channel in order to address an issue with activation failures spotted in our recent Android M Stable Release from last week. This build is also being pushed to the Beta channel, as that channel shared the same Xamarin.Android version as the Stable channel at the time this issue was discovered.


Products Released

Stable Release: Android M Support

Today we are putting our final support builds for Google’s Android M SDK to the Stable channels. Please see the forum threads below for any news on issues that people may be finding post launch.


Products Released

 

Stable Release: iOS 9 Support – Service Release 1

We are releasing new Beta builds to further address some issues with our previously released iOS 9 support

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


Products Released


Upcoming Release Dates

Alpha – N/A

Beta – September 29th, 2015

Stable – Today!

Stable Release: Mono Framework for El Capitan

We are releasing an updated Mono Framework to the Stable channel. A bug has been identified as a critical issue affecting some internal tests, and we felt that releasing the fix was a priority.

The issue is caused by a new feature in El Capitan called System Integrity Protection (SIP). One of the changes resulting from SIP is that any environment variables prefixed with DYLD_* are blanked out when launching protected processes.   This caused problems for some applications, and in particular some features of Xamarin Studio.


Products Released