Alpha Preview 4: Cycle 9

We are releasing the fourth Alpha preview of our next major feature release, called Cycle 9.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.


Known Issues

As this is a Alpha build, there are some known issues and the possibility of new issues being found during testing.

Of course additional bug reports are still welcome for these preview versions. If you see any suspicious behavior that you wish to report, please file a quick bug. File a bug using the “Cycle 9 Preview” new bug form.

  • [Xamarin.VS] – At this time, as a result of VS 2017 moving away from .msi packaging toward utilization of the Visual Studio Installer system, Xamarin for Visual Studio 2017 can not be installed at the same time as Xamarin for Visual Studio 2015/2013/2012. Please note that installing Xamarin to Visual Studio 2017 will render any previous installation of Xamarin in an earlier version of Visual Studio inoperable.
  • [Xamarin.Android]48213 – Android 7.1.1 (API 25) is not yet supported in this release and can cause deployment errors such as “Value cannot be null. Parameter name: path2” if it is installed. A workaround is to uninstall API 25 in the Android SDK Manager or to disable Project properties > Application > Compile using Android version > Use Latest Platform (in Visual Studio) or Project Options > Build > General > Use latest installed platform (in Xamarin Studio) if you encounter any deployment failures.
  • [Xamarin.VS]46559 – VS hangs while Running/debugging an Android Wear App

Products Released 


Installing the Alpha and switching back to Stable

You can install this new Alpha version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – Nov 8th, 2016

Alpha 2 – Nov 16th, 2016 (Connect(); Conference)

Alpha 3 – Nov 28th, 2016

Alpha 4 – This Release!

Alpha Preview 3: Cycle 9

We are releasing the third Alpha preview of our next major feature release, called Cycle 9.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.


Known Issues

As this is a Alpha build, there are some known issues and the possibility of new issues being found during testing.

Of course additional bug reports are still welcome for these preview versions. If you see any suspicious behavior that you wish to report, please file a quick bug. File a bug using the “Cycle 9 Preview” new bug form.

  • [Xamarin.VS] – At this time, as a result of VS 2017 moving away from .msi packaging toward utilization of the Visual Studio Installer system, Xamarin for Visual Studio 2017 can not be installed at the same time as Xamarin for Visual Studio 2015/2013/2012. Please note that installing Xamarin to Visual Studio 2017 will render any previous installation of Xamarin in an earlier version of Visual Studio inoperable.
  • [Xamarin.Android]48213 – Android 7.1.1 (API 25) is not yet supported in this release and can cause deployment errors such as “Value cannot be null. Parameter name: path2” if it is installed. A workaround is to uninstall API 25 in the Android SDK Manager or to disable Project properties > Application > Compile using Android version > Use Latest Platform (in Visual Studio) or Project Options > Build > General > Use latest installed platform (in Xamarin Studio) if you encounter any deployment failures.
  • [Xamarin.VS]46559 – VS hangs while Running/debugging an Android Wear App
  • [Xamarin.VS] – 46750 – User is not able to Create Xamarin.Forms application on Windows 7 with VS2012/13

Products Released 


Installing the Alpha and switching back to Stable

You can install this new Alpha version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – Nov 8th, 2016

Alpha 2 – Nov 16th, 2016 (Connect(); Conference)

Alpha 3 – This Release!

Connect(); Keynote Releases

As you may have heard during the Connect(); Keynote session, we’re releasing a number of new products to our Alpha and Stable channels, with many new features available to sample right now.

 

 


WEB PREVIEW – VISUAL STUDIO FOR MAC


We are releasing our first preview of Visual Studio for Mac. Visual Studio for Mac is an evolution of Xamarin Studio, and includes all the functionality of Xamarin Studio 6.2.

Many changes have been made to the look-and-feel, terminology and default settings to to align more closely with Visual Studio, while remaining a Mac-centred development experience


Products Released

 

 


STABLE RELEASE – XAMARIN WORKBOOKS & INSPECTOR


We are releasing our first Stable build of Xamarin Inspector and Xamarin Workbooks 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. Xamarin Workbooks provide a blend of documentation and code that is perfect for experimentation, learning, and creating guides and teaching aides.


Products Released

 


STABLE RELEASE – iOS SIMULATOR (FOR WINDOWS)


We are releasing our first Stable build of the iOS Simulator for Xamarin.VS. The remote iOS Simulator provides you with a way to test and debug iOS apps on the simulator entirely from Visual Studio on Windows.

 

 


STABLE RELEASE – XAMARIN PROFILER


Note (11/22): Xamarin Profiler has been updated to build 1.0.2.2 (from 1.0.1.2). The issues fixed in these updates are noted below.

Note (11/17): Xamarin Profiler has been updated to build 1.0.1.2 (from 1.0.0.24). The issues fixed in these updates are noted below.

Xamarin Profiler 1.0 is now available for download! The Xamarin Profiler Preview integrates seamlessly with your existing Xamarin toolchain to collect information about your Xamarin apps. Use it to find memory leaks, resolve performance bottlenecks, and add polish to your apps before getting them out the door.


Products Released

  • Xamarin Profiler 1.0.2.2
    • Release Notes
    • Issues Addressed:
      • 44253 – Application not rebuilt with profiling support when profiling
      • 47263 – Couldn’t retrieve SSH Fingerprint

 

 


ALPHA RELEASE – CYCLE 9 UPDATED PREVIEW


An updated preview of our next upcoming feature release (called Cycle 9) can be downloaded from the Alpha channel.


Cycle 9 Alpha Known Issues

  • [Xamarin.VS] – At this time, as a result of VS 2017 moving away from .msi packaging toward utilization of the Visual Studio Installer system, Xamarin for Visual Studio 2017 can not be installed at the same time as Xamarin for Visual Studio 2015/2013/2012. Please note that installing Xamarin to Visual Studio 2017 will render any previous installation of Xamarin in an earlier version of Visual Studio inoperable.
  • [Xamarin.VS]46557 – Android Designer is unable to render in Visual Studio.
  • [Xamarin.VS]46559 – VS hangs while Running/debugging an Android Wear App
  • [Xamarin.VS] – 46750 – User is not able to Create Xamarin.Forms application on Windows 7 with VS2012/13
  • [Xamarin.Android] 46509 – New linker failure in Xamarin.Android Cycle 9 on Windows error MSB4018: System.ArgumentNullException: Value cannot be null. Parameter name: instruction
  • [Xamarin.Android] 46510 – New linker failure in Xamarin.Android Cycle 9 Error executing task LinkAssemblies: Value cannot be null. Parameter name: variable

Cycle 9 Alpha Products Released 

 

 


STABLE RELEASE – CYCLE 8 SERVICE RELEASE 1 UPDATES


Note (11/22): Xamarin.VS has been updated to 4.2.1.64 (from 4.2.1.62) .Xamarin Profiler has been updated to build 1.0.2.2 (from 1.0.1.2). The issues fixed in these updates are noted below.

Note (11/17): Xamarin.VS has been updated to 4.2.1.62 (from 4.2.1.60), and Xamarin Profiler has been updated to build 1.0.1.2 (from 1.0.0.24). The issues fixed in these updates are noted below.

An updated Xamarin.VS has been released to Stable as part of C8SR1 alongside the newly released Xamarin tools products. 


Cycle 8 Service Release 1 Stable Products Released 

 

Stable Release: Cycle 8 Service Release 1

We are releasing Cycle 8 Service Release 1 to the Stable channel. Please check out the product release notes to see all the fixes and known issues for this release.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.


Known Issues

  • [Xamarin for Visual Studio], [Xamarin Studio] – Upcoming compatibility feature, tracked in 44330 – “This version does not have support for files saved in Xcode 8 format” appears when attempting to edit a file with the Xamarin iOS designer after having edited the file with Xcode 8. Xcode 8 introduced a new, non-backwards-compatible XML format for Interface Builder documents that is not yet supported in Xamarin’s iOS designer. As it turns out, Xcode 8.1 from Apple has in fact backed out of several of those format changes. Candidate fixes are now under test for Xamarin’s iOS designer to cover the remaining format changes as present in Xcode 8.1.
    • Workaround: This item should be fixed by our Xamarin Studio and Xamarin.VS versions available in the Alpha channel.
  • [Xamarin Studio]43188 – Sporadic “Out of memory” error during build leaves solution in an unbuildable state until the project is reloaded.
    • Improved in this release: Cycle 8 Service Release 1 includes some fixes that should hopefully eliminate the need to reload the project in this scenario. Additional fixes for the “Out of memory” error itself are also planned.
  • [Xamarin for Visual Studio], [Xamarin Studio]43566 – In a few remaining scenarios, the iOS Designer initialization process might still cause a running iOS 10 simulator to become non-responsive. The designer initialization happens when opening an iOS project in Xamarin Studio and during the connection to the remote Mac in Visual Studio. This issue does not affect Xcode 7.3, iOS 9.3 (and lower) simulators.
    • Workaround: Quit and restart the simulator after the designer has initialized. You can then proceed to use the simulator again as normal.

Products Released

  • Xamarin Studio 6.1.2.44
  • Release Notes
    • Issues Addressed:
      • 45535 – User is not seeing iOS Simulator in Xamarin Studio
      • 43675 – New “run configurations” menu means we can’t see which emulator is selected
      • 45358 – User is not seeing iOS Simulator in Xamarin Studio when using Xcode 8.1 beta
      • 42779 – Random crash caused by LogViewProgressMonitor
      • 44537 – XS 6.x branches are not reading XML documentation from 3rd party libraries
      • 44378 – Mac Migration Tool Not Working
      • 44285 – Xcode 8 quits after Xamarin Studio returns to the foreground when using Xcode 8 via Open With > Xcode Interface Builder.
      • 44144 – Cannot open axml files using Layout Editor
      • 40314 – “Reopen Closed Tab” option does not work on Assembly Browser tabs
      • 38791 – Update default product templates to benefit from C#6
      • 15222 – Open With doesn’t work when file is open in another editor
      • 34994 – Dialogs do not highlight default [“Return”] button on Mac
      • 46062 – Cannot create a WatchKit App (watchOS2) project’
      • 45855 – “Failed to launch the simulator: Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode.app/Contents/Frameworks/libswiftos.dylib): not found.” when attempting to launch iOS 10.1 simulator via `mlaunch`
      • 45644 -[iOS Designer] Accessing Designer throws error “Unable to boot device because it cannot be located on disk”
      • 45861 – “May Slow Down Your iPhone … The developer of this app needs to update it to improve its compatibility.” because of default “i386” supported architecture setting in the iPhoneSimulator configuration on new projects
      • 45856 – Missing iOS 10.0 deployment target
      • 45899 – “error HE0035: Could not find a paired iPhone device for the Watch ‘watchOS 3.1 (14S471a) – Apple Watch – 42mm'” on Series 1 Watch simulator
  • Xamarin.VS 4.2.1.58
  • Release Notes
    • Issues Addressed:
      • 44578 – Cannot debug any solution from VS on my iPad anymore
      • 44997 – Android Designer shows progress indicator indefinitely
      • 44468 – Can’t save 120×120 App Icons in Info.plist editor
      • 45122 – Import Existing Keystore fails with java.io.IOException: Keystore was tampered with, or password was incorrect
      • 44567 –  “Launch failed. The app ‘app’ could not be launched on ‘iPhone’: Object reference not set to an instance of an object” when attempting to deploy to certain iOS devices in certain environments.
      • 44958 – No Available Devices are Listed After Changing Start Up Project via the Run button
      • 43316 – Native References in iOS Binding projects do not build in VS
      • 45249 – “Could not install package ‘Xamarin.Forms 2.2.0.45’. You are trying to install this package into a project that targets ‘Unsupported,Version=v0.0′” when adding a new XAML page to a Forms Shared Project
      • 44432 – Entitlements view doesn’t save changes made in designer nor loads data from plist
      • 43948 – Android Designer shows progress indicator indefinitely
      • 44284 – User is not getting option ‘Top Shelf Image Wide’ under Assets catalogs for tvOS template in VS.
      • 38570 – “The project requires user input. Reload the project for more information” error prevents loading a newly created F# Blank App (Android) tempate app
      • 44394 – The error message shown in the Output window when attempting to use a 7.x device with Xcode 8 does not include the compatibility error returned by Xcode.
      • 44273 – “An error occurred trying to load the page.” appears in the “Project Properties > iOS Build” tab when not connected to a Mac
      • 45333 – [Android Archive Manager and Publishing Workflow Enhancements] Differentiator between Alias, Wizard Path, Key Details, Keystore Path]
      • 45676 – “Failed to launch the simulator: Could not load the framework ‘libswiftAppKit.dylib’ … Library not loaded: @rpath/libswiftQuartzCore.dylib” when attempting to launch iOS 10.1 simulator.
      • 44551 – Attempting to deploy app with “iOS Application > Devices” set to “iPhone/iPod” on physical iPad has no effect and produces no error messages or warning in any log files
      • 45862 – “May Slow Down Your iPhone … The developer of this app needs to update it to improve its compatibility.” because of default “i386” supported architecture setting in the iPhoneSimulator configuration on new projects
      • 44570 – building with VS 2015 Update 3 and msbuild property IpaPackageDir is defined and custom solution profile an error is thrown when cleanup starts from mac xamarin throws error
      • 45711 – “Error opening installation log file. Verify that the specified log file location exists and is writable” when attempting to install update if username contains accented characters
      • 44724 – “Failed to read file attributes for “/Users/macuser/Library/Caches/Xamarin/Resources/Images.xcassets”” when rebuilding iOS project that uses asset catalogs
  • Xamarin.iOS 10.2.1.5
  • Release Notes
    • Issues Addressed:
      • 44701 – “Could not link assemblies” due to NullReferenceException in certain scenarios during bindings optimization
      • 45379 – “Assertion: should not be reached at … mono/mono/sgen/sgen-scan-object.h:90” causes crash on simulator and device
  • Xamarin.Android 7.0.2.37
  • Release Notes 
    • Issues Addressed:
      • 44535 – “‘System.ComponentModel.INotifyPropertyChanged’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘System.ObjectModel” for projects that reference PCLs with `INotifyPropertyChanged`
      • 44633 – Enabling <AndroidUseSharedRuntime> in some projects causes `classes.dex` to not deploy to device
      • 34498 – AOT task fails if project path has a space in it
      • 43915 – Getting build error on Android F# app when using ‘Array.take’.
      • 44193 – Warning when building Forms app: MSB3247 Found conflicts between different versions of the same dependent assembly
  • Mono Framework 4.6.2.7
  • Release Notes
    • Issues Addressed:
      • 39832 – SIGSEGV when running roslyn
      • 44349 – Mono.Data.Sqlite fails to store seconds in timestamp value to a table

 


Updating and downgrading
You can install this new version by checking for updates on the Stable updater channel.
You can downgrade back to the previous Cycle 8 Service Release 0 (from October 4, updated with Xcode 8.1 compatibility on October 27) versions by manually reinstalling each old package. See the KB article on downgrading. If you would prefer an email with any older installer links you need, feel free to write to contact@xamarin.com to request the older versions.

  • For Mac you’ll need: Xamarin Studio, Xamarin.iOS, Xamarin.Android, and Mono.
  • For Windows you’ll need: Xamarin.VisualStudio (from either the Xamarin.Android or Xamarin.iOS drop-down menu), and optionally Xamarin Studio.

Older Mono package versions are not currently listed on https://store.xamarin.com/account/my/subscription/downloads. The Mono package for the previous Stable version (from October 4) is available here:


Upcoming Release Dates

Beta 1 – Oct 19th, 2016

Beta 2 – Nov 3rd, 2016

Stable – This Release!

Alpha Preview: Cycle 9

We are releasing the first Alpha preview of our next major feature release, called Cycle 9. As this is a Alpha build, there are some known issues and the possibility of new issues being found during testing.

Of course additional bug reports are still welcome for these preview versions. If you see any suspicious behavior that you wish to report, please file a quick bug.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.

The issues addressed below are only the highest severity ones, so please check out the product release notes to see all the fixes and known issues for this release.


Known Issues 

  • [Xamarin.VS]46557 – Android Designer is unable to render in Visual Studio.
  • [Xamarin.VS]46559 – VS hangs while Running/debugging an Android Wear App
  • [Xamarin.VS] – 46750 – User is not able to Create Xamarin.Forms application on Windows 7 with VS2012/13
  • [Xamarin.Android] 46509 – New linker failure in Xamarin.Android Cycle 9 on Windows error MSB4018: System.ArgumentNullException: Value cannot be null. Parameter name: instruction
  • [Xamarin.Android] 46510 – New linker failure in Xamarin.Android Cycle 9 Error executing task LinkAssemblies: Value cannot be null. Parameter name: variable

Products Released

  • Xamarin Studio 6.2.0.1358
    • Release Notes
    • Major Issues Addressed:
      • 44330 – Can’t edit storyboard with iOS Designer after editing with Xcode 8
  • Xamarin.VS 4.3.0.254
    • Release Notes
    • Major Issues Addressed:
      • 44317 – A problem was encountered creating the sub project ‘myprojectname.Droid’. Attempted to access a missing method
  • Xamarin.Android 7.0.99.160
    • Release Notes
    • Major Issues Addressed:
      • 44350 – Seeing multiple error CS00**: Inconsistent accessibility errors building binding projects using class-parse

Installing the Alpha and switching back to Stable

You can install this new Alpha version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Alpha – This Release!

(UDPATED) Beta Release: Cycle 8 Service Release 1 RC Builds

UDPATE – Xamarin.VS, Xamarin.iOS, Xamarin.Android, and Xamarin.Mac have all been updated to slightly newer versions.

  • Xamarin.VS version is now 4.2.1.57 (was 4.2.1.52)
  • Xamarin.iOS version is now 10.2.1.5 (was 10.2.1.4)
  • Xamarin.Android is now 7.0.2.38 (was 7.0.2.37)
  • Xamarin.Mac is now 2.10.0.113 (was 2.10.0.111)

 

We are releasing a Beta preview of our next release, called Service Release 1. This release contains the Release Candidates of C8SR1, which should be shipping to the Stable Channel soon.

 As this is a Beta build, there are some known issues and the possibility of new issues being found during testing.

Please check out the product release notes to see all the fixes and known issues for this release.

If you see a behavior that looks suspicious in these versions, and if it isn’t clear whether one of the known issues in the release notes matches the problem, please file a quick bug report to let the team know.

If you notice an error in this blog post or have trouble downloading one of the installer packages, please let us know in the corresponding forum thread.


Known Issues

  • [Xamarin for Visual Studio], [Xamarin Studio] – Upcoming compatibility feature, tracked in 44330 – “This version does not have support for files saved in Xcode 8 format” appears when attempting to edit a file with the Xamarin iOS designer after having edited the file with Xcode 8. Xcode 8 introduced a new, non-backwards-compatible XML format for Interface Builder documents that is not yet supported in Xamarin’s iOS designer. As it turns out, the beta version of Xcode 8.1 from Apple has in fact backed out of several of those format changes. Candidate fixes are now under test for Xamarin’s iOS designer to cover the remaining format changes as present in Xcode 8.1.
  • [Xamarin Studio]43188 – Sporadic “Out of memory” error during build leaves solution in an unbuildable state until the project is reloaded.
    • Improved in this release: Cycle 8 Service Release 1 includes some fixes that should hopefully eliminate the need to reload the project in this scenario. Additional fixes for the “Out of memory” error itself are also planned.
  • [Xamarin for Visual Studio], [Xamarin Studio]43566 – In a few remaining scenarios, the iOS Designer initialization process might still cause a running iOS 10 simulator to become non-responsive. The designer initialization happens when opening an iOS project in Xamarin Studio and during the connection to the remote Mac in Visual Studio. This issue does not affect Xcode 7.3, iOS 9.3 (and lower) simulators.
    • Workaround: Quit and restart the simulator after the designer has initialized. You can then proceed to use the simulator again as normal.

Products Released

  • Xamarin Studio 6.1.2.44
  • Release Notes
    • Issues Addressed:
      • 45535 – User is not seeing iOS Simulator in Xamarin Studio
      • 43675 – New “run configurations” menu means we can’t see which emulator is selected
      • 45358 – User is not seeing iOS Simulator in Xamarin Studio when using Xcode 8.1 beta
      • 42779 – Random crash caused by LogViewProgressMonitor
      • 44537 – XS 6.x branches are not reading XML documentation from 3rd party libraries
      • 44378 – Mac Migration Tool Not Working
      • 44285 – Xcode 8 quits after Xamarin Studio returns to the foreground when using Xcode 8 via Open With > Xcode Interface Builder.
      • 44144 – Cannot open axml files using Layout Editor
      • 40314 – “Reopen Closed Tab” option does not work on Assembly Browser tabs
      • 38791 – Update default product templates to benefit from C#6
      • 15222 – Open With doesn’t work when file is open in another editor
      • 34994 – Dialogs do not highlight default [“Return”] button on Mac
      • 46062 – Cannot create a WatchKit App (watchOS2) project’
      • 45855 – “Failed to launch the simulator: Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode.app/Contents/Frameworks/libswiftos.dylib): not found.” when attempting to launch iOS 10.1 simulator via `mlaunch`
      • 45644 -[iOS Designer] Accessing Designer throws error “Unable to boot device because it cannot be located on disk”
      • 45861 – “May Slow Down Your iPhone … The developer of this app needs to update it to improve its compatibility.” because of default “i386” supported architecture setting in the iPhoneSimulator configuration on new projects
      • 45856 – Missing iOS 10.0 deployment target
      • 45899 – “error HE0035: Could not find a paired iPhone device for the Watch ‘watchOS 3.1 (14S471a) – Apple Watch – 42mm'” on Series 1 Watch simulator
  • Xamarin.VS 4.2.1.52
  • Release Notes
    • Issues Addressed:
      • 44578 – Cannot debug any solution from VS on my iPad anymore
      • 44997 – Android Designer shows progress indicator indefinitely
      • 44468 – Can’t save 120×120 App Icons in Info.plist editor
      • 45122 – Import Existing Keystore fails with java.io.IOException: Keystore was tampered with, or password was incorrect
      • 44567 –  “Launch failed. The app ‘app’ could not be launched on ‘iPhone’: Object reference not set to an instance of an object” when attempting to deploy to certain iOS devices in certain environments.
      • 44958 – No Available Devices are Listed After Changing Start Up Project via the Run button
      • 43316 – Native References in iOS Binding projects do not build in VS
      • 45249 – “Could not install package ‘Xamarin.Forms 2.2.0.45’. You are trying to install this package into a project that targets ‘Unsupported,Version=v0.0′” when adding a new XAML page to a Forms Shared Project
      • 44432 – Entitlements view doesn’t save changes made in designer nor loads data from plist
      • 43948 – Android Designer shows progress indicator indefinitely
      • 44284 – User is not getting option ‘Top Shelf Image Wide’ under Assets catalogs for tvOS template in VS.
      • 38570 – “The project requires user input. Reload the project for more information” error prevents loading a newly created F# Blank App (Android) tempate app
      • 44394 – The error message shown in the Output window when attempting to use a 7.x device with Xcode 8 does not include the compatibility error returned by Xcode.
      • 44273 – “An error occurred trying to load the page.” appears in the “Project Properties > iOS Build” tab when not connected to a Mac
      • 45333 – [Android Archive Manager and Publishing Workflow Enhancements] Differentiator between Alias, Wizard Path, Key Details, Keystore Path]
      • 45676 – “Failed to launch the simulator: Could not load the framework ‘libswiftAppKit.dylib’ … Library not loaded: @rpath/libswiftQuartzCore.dylib” when attempting to launch iOS 10.1 simulator.
      • 44551 – Attempting to deploy app with “iOS Application > Devices” set to “iPhone/iPod” on physical iPad has no effect and produces no error messages or warning in any log files
      • 45862 – “May Slow Down Your iPhone … The developer of this app needs to update it to improve its compatibility.” because of default “i386” supported architecture setting in the iPhoneSimulator configuration on new projects
      • 44570 – building with VS 2015 Update 3 and msbuild property IpaPackageDir is defined and custom solution profile an error is thrown when cleanup starts from mac xamarin throws error
      • 45711 – “Error opening installation log file. Verify that the specified log file location exists and is writable” when attempting to install update if username contains accented characters
      • 44724 – “Failed to read file attributes for “/Users/macuser/Library/Caches/Xamarin/Resources/Images.xcassets”” when rebuilding iOS project that uses asset catalogs
  • Xamarin.iOS 10.2.1.4
  • Release Notes
    • Issues Addressed:
      • 44701 – “Could not link assemblies” due to NullReferenceException in certain scenarios during bindings optimization
      • 45379 – “Assertion: should not be reached at … mono/mono/sgen/sgen-scan-object.h:90” causes crash on simulator and device
  • Xamarin.Android 7.0.2.37
  • Release Notes 
    • Issues Addressed:
      • 44535 – “‘System.ComponentModel.INotifyPropertyChanged’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘System.ObjectModel” for projects that reference PCLs with `INotifyPropertyChanged`
      • 44633 – Enabling <AndroidUseSharedRuntime> in some projects causes `classes.dex` to not deploy to device
      • 34498 – AOT task fails if project path has a space in it
      • 43915 – Getting build error on Android F# app when using ‘Array.take’.
      • 44193 – Warning when building Forms app: MSB3247 Found conflicts between different versions of the same dependent assembly
  • Mono Framework 4.6.2.6
  • Release Notes
    • Issues Addressed:
      • 39832 – SIGSEGV when running roslyn
      • 44349 – Mono.Data.Sqlite fails to store seconds in timestamp value to a table

Installing the Beta and switching back to Stable

You can install this new Beta version or switch back to the current Stable version by changing updater channels.


Upcoming Release Dates

Beta 1 – Oct 19th, 2016

Beta 2 – This Release!

Stable – October 2016