Category Archives: Stable

Stable Release: Updated Cycle 8 Service Release 1 w/ Xcode 8.2 Support

We are releasing an updated version of Cycle 8 Service Release 1 to the Stable channel which provides Xcode 8.2 support on top of our existing Stable builds. 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 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.

Products Released


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 1 (from November 16) 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.iOS.
  • For Windows you’ll need: Xamarin.VisualStudio (from either the Xamarin.Android or Xamarin.iOS drop-down menu).

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!

Stable Release: Cycle 8 Service Release 0 w/ Xcode8.1 Support

We are releasing updated builds of Cycle 8 Service Release 0 to the Stable channel. These build support the final release of Xcode 8.1 from Apple (released today).

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.


Remaining higher visibility known issues related to Xcode 8.1

  • [Xamarin Studio] – 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
    • Fix: Change Project options > iOS Build > Supported architectures to x86_64 (instead of the default i386) for the iPhoneSimulator configuration.
  • [Xamarin.iOS] – 45899 – “error HE0035: Could not find a paired iPhone device for the Watch ‘watchOS 3.1 (14S471a) – Apple Watch – 42mm’ (C64439C5-9D9C-4B5C-B3B5-F77BBAA5B669)” when attempting to launch watch app on series1 sim

Other higher visibility known issues

  • [Xamarin.Android]46279 – “C:\Program Files (x86)\MSBuild\Xamarin\Android\mono-symbolicate” store-symbols … “obj\Release\android/assets” …  exited with code -1073740791″ and “Assertion at ..\mono\metadata\class.c:5078, condition `class’ not met” when attempting to create Android packages in the Release configuration.
    • Beta channel: The current Beta versions are not affected by this issue, so updating to Beta is one possible workaround.
    • Alternate partial workaround: Disable the symbolication step by opening the Android app project .csproj file in a text editor and changing the following line anywhere that it appears to say “false” instead of “true”: <AndroidManagedSymbols>true</AndroidManagedSymbols>

Intentional changes in Xcode 8.1 itself
As usual, be sure to also check the upstream release notes.

  • “May Slow Down Your iPhone … The developer of this app needs to update it to improve its compatibility.” alert dialog will be displayed when 32-bit applications are launched on 64-bit devices and simulators.
    • Fix: Be sure to configure your project to provide a 64-bit build for 64-bit devices.

Products Released


Release Dates

Stable – This Release!

(UPDATED) Stable Release: Cycle 8 Service Release 0

Update We are releasing updated builds for some of our products on top of Cycle 8 Service Release 0 to address issues 4430042443, and 44708:

  • Xamarin.VS updated to 4.2.0.703
  • Xamarin.iOS updated to 10.0.1.10
  • Xamarin.Android updated to 7.0.1.3
  • Xamarin.Mac updated to 2.10.0.105
  • Mono Framework updated to 4.6.1.5

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 Studio]44285 – Xcode 8 quits after Xamarin Studio returns to the foreground when using Xcode 8 via Open With > Xcode Interface Builder.
  • [Xamarin.Android]44633 – “Deployment failed because of an internal error: Failure [INSTALL_FAILED_DEXOPT]” when <AndroidUseSharedRuntime> is enabled in certain projects because classes.dex is not deployed to device as expected.
  • [Xamarin for Visual Studio]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
  • [Xamarin for Visual Studio], [Xamarin Studio]43566 – The iOS Designer initialization process will cause any 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.
    • Improved in this release: Cycle 8 Service Release 0 includes some fixes to reduce the chances of hitting this problem, but additional fixes are also planned.
    • 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.1.15
    • Release Notes
    • Major Issues Addressed:
      • 42376 – Crash while loading certain solutions due to incorrect absolute path calculation
      • 43566 (via 44373) – The iOS Designer initialization process will cause any running iOS 10 simulator to become non-responsive.
      • 43655 – Cannot open ‘API Documentation’ in XS on Mac.
      • 43675 – New “run configurations” menu causes most of the emulator name to be cut off
      • 44021 – No way to set sticker icons source in iMessage extension
      • 44128 – Crash when closing designer window and changing API level
      • 44190 – iOS and tvOS Broadcast UI/Upload extension fails to build
      • 44282 – iOS and tvOS Broken Broadcast UI template
      • 44283 – Missing iPhone 7 and Apple Watch Series 2 simulators
      • 44293 – Incorrect target framework profile for new PCL in XS compared to VS
  • Xamarin.VS 4.2.0.703
    • Release Notes
    • Major Issues Addressed:
      • 44146 – “GetFullVsVersionString must be called on the UI thread” error appears when attempting to open Manage NuGet Packages for Solution, sometimes blocking the use of the NuGet package manager in projects that use Xamarin Components.
      • 43566 (via 44373) – The iOS Designer initialization process will cause any running iOS 10 simulator to become non-responsive.
      • 44482 – Unable to connect VS to mac build host
      • 44508 – Selecting a file via the file browser for “Custom entitlements” deletes the selected file from the file system rather than selecting it
      • 44269 – Android Designer with Custom Controls spins loading bar when x86 Java JDK is set as the active JDK under Tools > Options > Xamarin > Android Settings > Java Development Kit Location.
      • 44357 – Getting ‘codesign’ error when ‘Enable incremental builds’ option is checked in VS and no code signing certificate installed on build host.
      • 44262 – Google Play Publishing wizard fails after client id/secret are entered.
      • 44591 – “Run in Test Cloud” context menu item is missing in VS 2015
      • 44460 – ResolveLibraryProjectImports often fails not being able to delete.
      • (Updated) 44300 – Xamarin.Android projects appear as “incompatible” after closing and reopening a solution in a single VS session.
        • A remaining issue related to the Test Recorder preview feature is still under investigation, so it is recommended to uninstall Test Recorder if you continue to see this issue after updating.
  • Xamarin.iOS 10.0.1.10
    • Release Notes
    • Major Issues Addressed:
      • 44225 – “Error: TrustFailure (CertificateUnknown)” when using Apple TLS handler to access HTTPS servers that use virtual domains (via Server Name Indication).
      • 44073 – VTCompressionSession does not handle null sample buffer
      • 42395 – Build runs indefinitely and never finishes with LLVM enabled
      • 44122 – MTOUCH: error MT2001: Could not link assemblies. Reason: Value cannot be null.
      • (Updated) 42443 – ServicePointTest (System) test crash on tvOS device
  • Xamarin.Android 7.0.1.3
    • Release Notes
    • Major Issues Addressed:
      • 43883 – Android Support v7 AppCompat Binding Generator error with Android N preview (API Level 24)
      • 39859 – Xamarin.Android apps on the Samsung Galaxy S7 fails to start with the error System.ExecutionEngineException SIGILL
      • 43411 – HTTP Bad Request (400) when encoding space (%20) in URL with AndroidClientHandler
      • 44268 – “Unexpected libzip error: Inval” when building projects that reference any of the Android Support Libraries on Windows if the user name contains any accented characters.
      • 44448 – Urban Airship component causes native crash in Mono
      • 44184 – “The “BuildApk” task failed unexpectedly. Xamarin.Tools.Zip.ZipException: Entry has been changed” when attempting to archive or deploy apps in certain environments.
  • Mono Framework 4.6.1.5
    • Release Notes
    • Major Issues Addressed:
      • 44402 – “Cannot implicitly convert type `int[]’ to `System.Collections.IEnumerable'” and “Type `System.Array’ does not contain a member `OfType’ and the best extension method overload … requires an instance of type `System.Collections.IEnumerable'”.
      • 43655 – User is not able to open ‘API Documentation’ in XS on Mac.
      • (Updated) 44708 – “TrustFailure (The authentication or decryption has failed.) … Invalid certificate received from server.” with “Error code: 0x5” or “Error code: 0xffffffff800b010f” when attempting to access HTTPS servers on ports other than 443

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 (September 13, 2016) 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 September 13) is available here:


Upcoming Release Dates

Beta – Sept. 23rd, 2016

Stable – Sept. 26th, 2016

Updated Stable – This Release!

 

Stable Release: Cycle 8 w/ iOS 10 and Xcode8 Support

We are releasing our next major feature release, called Cycle 8 to the Stable channel. These build also support the final Apple releases of iOS 10 and Xcode 8.

If you are wondering how to embed new iOS 10 functionality in your apps, you can check out the samples available here to get a head start:

  • AVCamBarcode – using AVFoundation to Detect Barcodes and Faces.
  • Flags – a demonstration of automatic RTL support in Asset Catalogs and UIStackViews.
  • IceCreamBuilder – app extension that interacts with the Messages app.
  • RawExpose – shows a RAW image asset management system.
  • SpeakToMe – using Speech Recognition with AVAudioEngine.
  • SpeedSketch(sitting in PR now) – leveraging touch input for a drawing application.
  • WatchPuzzle – how to work with low-level graphics in watchOS.

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.

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 alert the team.

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]Upstream non-standard behavior of NuGet Package Manager extension (Xamarin tracking bug 44146) triggered by XamarinVS 4.2 – “GetFullVsVersionString must be called on the UI thread” error appears when attempting to open Manage NuGet Packages for Solution, blocking the use of the NuGet package manager on certain systems
    • Temporary workaround: Install this small extension from the Xamarin VS team that will force the NuGet Package Manager to load before the Xamarin extensions.
    • Alternate temporary workaround: Before opening any projects, open Tools > NuGet Package Manager > Package Manager Settings to force the NuGet Package Manager extension to load before the Xamarin extensions.
  • [Xamarin.iOS]44225 – “Error: TrustFailure (CertificateUnknown)” when using Apple TLS handler to access HTTPS servers that use virtual domains (via Server Name Indication).
    • Partial temporary workaround: Under Project Options > iOS Build, change the SSL/TLS implementation setting back to the old default Mono (TLS v1.0).
  • [Xamarin for Visual Studio], [Xamarin Studio]43566 – The iOS Designer initialization process will cause any 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.
  • [Xamarin.Android]44268 – “Unexpected libzip error: Inval” when building projects that reference any of the Android Support Libraries on Windows if the user name contains any accented characters.
    • Temporary workaround: Create and log in with a Windows user account that has only ASCII letters in the user name.
    • Alternate workaround: Add a XAMARIN_CACHEPATH environment variable under Control Panel > System > Advanced system settings > Environment Variables, and set it to a path that uses only ASCII letters in the directory names.
  • [Xamarin.Android]44184 – “The “BuildApk” task failed unexpectedly. Xamarin.Tools.Zip.ZipException: Entry has been changed” when attempting to archive or deploy apps that use certain NuGet packages.
  • [Xamarin.UITest] – Xcode 8 removes the UI Automation API, causing “SetUp : System.InvalidOperationException : Sequence contains no matching element … at System.Linq.Enumerable.First[TSource] … at Xamarin.UITest.iOS.Instruments.GetAutomationTemplatePath ()” when attempting to use UITest locally.
    • Candidate fix: Update to the Xamarin.UITest 2.0.0 Beta prerelease, which is based on Calabash 0.20 and includes a new API that uses XCUITest rather than UI Automation.
    • Alternate temporary workaround: Keep using Xcode 7, or just keep Xcode 7 installed in the default location and unpack Xcode 8 side-by-side to a custom location.
  • [Xamarin Studio]43655 – Cannot open ‘API Documentation’ in XS on Mac.
  • [Xamarin Studio]43675 – New “run configurations” menu prevents seeing which emulator is selected.
  • [Xamarin for Visual Studio] – 40767: Collection View and Table View are rendered differently on the iOS designer and the actual simulator
  • [Xamarin.iOS] – 42443 –  ServicePointTest (System) tests crash on tvOS device
  • [Mono Framework] 44429 – Upstream issue in OS X Sierra Beta, P/Invoke to NSLog or os_log currently crashes.
    • Workaround – Use System.Console.WriteLine() instead of using NSLog directly
    • Alternate workaround: Create a small C static library which invokes NSLog for you, link it into your application, and invoke it instead.

Intentional Changes

  • [Xamarin.iOS] – “Error MT0091: This version of Xamarin.iOS requires the iOS 10.0 SDK (shipped with Xcode 8.0) when the managed linker is disabled. Either upgrade Xcode, or enable the managed linker.” This message will appear when building using Xcode 7.3 or older with Xamarin.iOS 10. The issue arises because Xamarin.iOS 10 is built to include the Xcode 8 symbols. When enabled, the Xamarin managed linker can remove these unused symbols to allow building successfully against older versions of Xcode.
    • Fix: Update to Xcode 8, or enable the Xamarin linker by choosing a setting other than Don’t link under Project properties > iOS Build > Linker behavior.
  • [Xamarin for Visual Studio]Build > Export Android Package (.apk) and Tools > Android > Publish Android App have been replace by the Build > Archive command that is part of the new Android Archive Manager and Publishing workflow.

Products Released

  • Xamarin Studio 6.1.0.5441
    • Release Notes
    • Major Issues Addressed:
      • 42554 – Typing into the search box is corrupting memory and crashing XS
      • 43210 – User is not able to launch an activity by explicitly specifying which activity to launch for Android application in XS
      • 43187 – Quick build/run menu selector does not include run configurations
      • 43949 – Unable to set SDK and NDK path in XS
      • 43888 – Unable to open iOS designer in XS
      • 43678 – Unable to open ‘Create Layout Variation’ window on clicking ‘New Version’ button
      • 44036 – Cannot create new multiplatform projects
      • 42389 – Constant spinwheels / hangs when editing, scrolling, or searching in the document editor with a large solution using XS 6.1
      • 42325 – Xamarin.Forms projects using montouch.dll do not work in the previewer
      • 42206 – Incorrectly detecting xamarin forms xaml
      • 42103 – User is not able to run Library project in windows XS, if they have a custom execution command
      • 42041 – Unable to open .fsx file in F# Interactive pad of Windows XS
      • 42035 – Getting “Session termination detected” in F# Interactive pad and it stop working
      • 42012 – Reset button of F# Interactive pad does not reset its saved session
      • 41889 – Not getting “Broadcast Receiver 1 invoked !” message in application output, when running Xamarin.Android project with a broadcast receiver, explicitly
      • 41838 – iOS application throws exception, while running in Background Fetch Mode
      • 41785 – ‘Arguments’ and ‘Environment variable’ are not getting saved for iOS application in XS
      • 41757 – User is not getting get option to choose to run watchkit application in Glance mode or notification via Run dropdown in XS
      • 41756 – User is not able to run project in XS, when Multi Startup option is selected
      • 41688 – User is not able to execute library project with custom execution command in XS
      • 41679 – User is not able to Archive for iOS Publishing on MAC
      • 41646 – User is not able to Add a Custom Configuration in XS
      • 40497 – XA is not recognized, looking for mandroid.exe
      • 40422 – The roslyn workspace can’t be queried while it’s loading
      • 43168 – Getting error in Android Previewer even after building or rebuilding the project
      • 42969 – Apps won’t launch on simulators or devices using Xcode8 beta 4
      • 41784 – error ‘object reference not set to instance of object’ in Forms Previewer when opening any XAML file.
      • 42470 – Remove Other/Miscellaneous/MonoMac templates
      • 41905 – copy classes containing regions delete the keys
      • 41687 – Xamarin Studio Community Version 6.0 (build 5174) freezes when users click on “Navigate” -> “Find Reference”
      • 41685 –  Xamarin Studio Community Version 6.0 (build 5174) does not correctly save .cs files
  • Xamarin.VS 4.2.0.680
    • Release Notes
    • Major Issues Addressed:
      • 43300 – Intermittent disconnection of VS from Build Host while working with iOS application.
      • 43037 – Unable to install XVS builds.
      • 43602 – “Device Log” window does not open in Visual Studio.
      • 43565 – Visual Studio often hangs (pauses, freezes) during `TastyConfig.DebugLaunch()` on second deployment attempt
      • 43650 – User is not getting simulator for Watckit OS1 application in VS dropdown
      • 43454 – User is not able to run Watch OS1 application with VS, application gets terminated
      • 44046 – Getting build error for iOS/tvOS template
      • 43976 – Can’t open WatchOS interface.storyboard in designer
      • 43884 – Unable to open iOS designer in VS
      • 43232 – Unable to build Blank Mac App(Cocoa App), getting ‘Illegal characters in path’ error.
      • 42958 – Getting “DetectSdkLocations — FAILED” error on building Blank Mac application on Visual Studio
      • 42757 – Getting build error in Android Designer when building the project after dragging the custom control to the designer in VS
      • 42688 – Getting “Required service ‘EnvDTE80.DTE2’ not found” error on opening Android Designer
      • 42435 – Getting “‘ResolveUinversalTypeIdentifiers’ task failed unexpectedly” error on building ‘Spritekit Game’ or ‘Scenekit Game’ Mac app solution in VS
      • 42397 – The forms previewer is disabled in cycle8
      • 42113 – xaml files in shared asset projects don’t work in the forms previewer
      • 41815 – Xamarin.Forms.Templates.VisualStudio.dll gets loaded on VS startup even after second time+
      • 40546 – No Xamarin/VS License is activated and keeps showing VS community
      • 43018 – unable to select an event handler which has been already defined
      • 42422 – Game Controller checkbox Settings remembered on reopeining the Info.plist of tvOS application
      • 41915 – Xamarin breaks VSTU debugger integration with Unity 3D and Visual Studio
      • 41507 – Connecting from Visual Studio Community 2015 to Mac host
  • Xamarin.iOS 10.0.0.6
    • Release Notes
    • Major Issues Addressed:
      • 43373 – Unable to upload application to device due to an error “Could not load the framework ‘libswiftos.dylib’ (path: /Applications/Xcode8-beta6.app/Contents/Frameworks/libswiftos.dylib)” with Xcode8-beta6 update
      • 43837 – Unexpected Error MT0000 when building in Release configuration and targeting a device (not sim)
      • 40936 – iOS app crash when taking snapshots
      • 42099 – User is not able to run watchOS2 app in XS
      • 42750 – Deploying an iOS app to iPhone 6S crashes when a breakpoint is set
      • 42549 – Getting build error ‘Could not AOT the assembly’ in release mode on iOS device
      • 42493 – WatchOS2 app is not launching on Watch Simulator
      • 40788 – Invalid assembly name System.ServiceModel.Web
      • 42452 – Unsupported type encoding : _GLKVector4={?=ffff}{?=ffff}{?=ffff}[4f])16 / GLKMatrix4 = {?=ffffffffffffffff}[16f])16
  • Xamarin.Android 7.0.0.18
    • Release Notes
    • Major Issues Addressed:
      • 43268 – Android application crashes when launched on Android device, when running a project with a service in XS
      • 42646 – Error XA2006: Reference to metadata item ‘Android.Views.DecorCaptionShade’ when attempting to build codegen tests in release
      • 43487 – ‘System.DllNotFoundException: sqlite3’ thrown when trying to use sqlite with Cycle8
      • 42814 – Deploy to Android device fails when setting a breakpoint
      • 42835 – Android projects which use Support packages are failing to build on Windows due to issue extracting resources
      • 42521 – Applications crashing on startup due to java.io.IOException: No original dex files found
      • 42469 – Assertion “fixed_type_allocator_indexes [type] == slot’ not met” causing apps to crash on startup
      • 42912 – Release deployments are crashing immediately on startup “No assemblies found in ‘(null)’ or ‘<unavailable>’.”
      • 41706 – TypeLoadException thrown when trying to compile a binding project.
      • 40437 – All builds are now failing on windows due to error finding mandriod
  • Mono Framework 4.6.0.245
    • Release Notes
    • Major Issues Addressed:
      • 42864 –  “System.Net.WebException: Error: NameResolutionFailure” on second web request to certain raw IP addresses with HttpClient
      • 43305 – Standard Library dependency error on Xamarin Studio
      • 42408: WebClient.DownloadString returns 401 Unauthorized when using Basic authentication
      • 42938:  Compilation of netstandard PCL library with xbuild fails with… CSC: error CS0518: The predefined type …  is not defined or imported
      • 43636 – “Index was out of range. Must be non-negative and less than the size of the collection” in `System.Collections.Generic.List`1[T].set_Item()` when attempting to compile certain C# code involving tasks, async/await, and try/catch/finally
      • 33475 – Android app crash when taking snapshots
      • 41644 – Shutdown deadlock for Mono 4.5.1/master with Xamarin Studio/

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 7 Stable versions (from August 1, 2016) by manually reinstalling each old package. See the “Get the latest stable version of Cycle 7” section on your account page: https://store.xamarin.com/account/my/subscription/downloads#cycle7. (If you do not yet have a Xamarin login, you can create one.) If you have any trouble downloading the previous versions from that link, would like to install an even earlier set of versions, or simply would prefer an email with all the installer links you need, feel free to email contact@xamarin.com.

For Mac, you’ll also need to downgrade Xcode to 7.3.


Release Dates

Alpha – April 27th, 2016 (Evolve Conference)

Alpha 2 – July 13th, 2016

Alpha 3 – July 27th, 2016

Alpha 4 – Aug 2nd, 2016

Alpha 5– Aug 9th, 2016

Alpha 6 – Aug 12, 2016

Beta 1 – Aug 17th, 2016

Beta 2 – Aug 24th, 2016

Beta 3 – Aug 31st, 2016

Beta 4 – Sep 8th, 2016

Stable – This Release!

Stable Release: Cycle 7 Service Release 1

We are publishing a Stable release of our second bugfix release on top of Cycle 7, called Service Release 1.

NOTE Regarding .NET Standard and NuGet Client – These builds introduce compatibility with the new .NET Standard 1.6.  This in particular allows developers to consume NuGet packages that have been built against the .NET Standard 1.6.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the beta channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Products Released 

  • Xamarin Studio 6.0.2.73
    • Release Notes
    • Forum Thread – Stable Release: Cycle 7 – Service Release 1
    • Issues Fixed:
      • 42051 – Fixed an error when editing control name in storyboard
      • 41862 – Android Designer should now correctly open in XS for certain projects
      • 41499 – Shortened time it takes for NuGet package searches to return results
      • 42743 – HttpClientHandler combo is not shown for Community license
      • 42795 – View >> Focus Document is not functioning
  • Xamarin.Android 6.1.2.21

Upcoming Release Dates

Beta – July 6th, 2016

Beta 2 – July 20th, 2016

Beta 3 – July 26th, 2016

Beta 4 – July 29th, 2016

Stable – This Release!

Xamarin Studio Stable Hotfix for Incompatible XS Addins

We are releasing an updated Xamarin Studio build to the Stable channel in order to address an issue causing addins for Xamarin Studio 6.0 to show as incompatible with Xamarin Studio 6.0.1 for some users.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.


Issues Addressed 

  • 42089 – Fixed an issue where addins for Xamarin Studio 6.0 were showing as incompatible with Xamarin Studio 6.0.1.

Products Released 

Stable Release: Cycle 7 Service Release 0

We are publishing the stable builds of our first bugfix release on top of Cycle 7, called Service Release 0.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. You will need to rebuild your apps with Xamarin C6SR4, or later, to ensure that this crash does not occur once the final system image for Android N is released.

NOTEVisual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: You will need to have Microsoft Build Tools 2015 installed in order to use the iOS Designer in the Stable channel, with the current Xamarin.VS build.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.VS]41836 – For iOS apps, breakpoints within async methods in PCL projects are not hit if the linker is enabled.
  • [Xamarin.VS/Xamarin.iOS] – Under certain conditions, downgrading from our Xamarin products in the Alpha channel to the Beta or Stable channel versions may result in the Xamarin.iOS plugin failing to load correctly.
    • Workaround – Delete the component cache  (steps here).
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”
  • [Xamarin.Android] – AOT+LLVM compiling is disabled in this release due to a crash discovered while trying to fix a compiler issue. It will be re-enabled in a future release.

Products Released 


Upcoming Release Dates

Beta – June 20th, 2016

Stable – This Release!

Stable Release: Cycle 7

We are publishing the final builds for our next major feature release, called Cycle 7, to the Stable channel.

Please check out the product release notes to see all the fixes and known issues for this release, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. The functionality for this is supported in this release.

NOTE: Visual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: The Cycle 7 version of Xamarin.VS requires Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed.


Known Issues

  • [Xamarin.VS]41836 – For iOS apps, breakpoints within async methods in PCL projects are not hit if the linker is enabled.
  • [Xamarin.VS/Xamarin.iOS] – Under certain conditions, downgrading from our Xamarin products in the Alpha channel to the Beta or Stable channel versions may result in the Xamarin.iOS plugin failing to load correctly.
    • Workaround – Delete the component cache  (steps here).
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”
  • [Xamarin Studio] –  41565 – “Could not load solution:” and “Load operation failed.” when attempting to open certain projects in Xamarin Studio 6.0.
    • Recommended fix – Open the problematic .csproj file in a text editor and remove the conflicting item from the <ProjectTypeGuids> element. For iOS extension projects, the most common fix is to remove the {FEACFBD2-3405-455C-9665-78FE426C6842}; item from the list.
  • [Xamarin.Android] – AOT+LLVM compiling is disabled in this release due to a crash discovered while trying to fix a compiler issue. It will be re-enabled in a future release.

Products Released 

  • GTK# 2.12.38

Previous Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – May 24th, 2016

Stable – This Release!