Category Archives: Xamarin.Mac

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!

Beta Release: Cycle 7 Service Release 0

We are publishing a preview of our first bugfix release on top of Cycle 7, called Service Release 0. As this is a Beta build, there may be 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 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 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.


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 – This Release!

Stable – June 2016

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. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.

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. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.


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!

Beta Release: Cycle 7 Release Candidate 3

Update (6/6) – Slightly newer builds have been pushed to the Beta channel in anticipation of our upcoming Stable release. Please see the newer version numbers noted below. 

We are publishing a new release candidate of our next major feature release, called Cycle 7. As this is a Beta build, there may be 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 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. The functionality to support 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 – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – This Release!

Stable – April/May 2016

Beta Release: Cycle 7 Release Candidate 2

We are publishing a new release candidate of our next major feature release, called Cycle 7. As this is an 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 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. The functionality to support this is not in this release, however it will be included in a future release of Cycle 7, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

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 – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – This Release!

Stable – April/May 2016

Stable Release: Cycle 6 Service Release 4

We are releasing the Stable builds of Service Release 4 on top 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.


Products Released

  • Xamarin for Visual Studio 4.0.4.4
    • Release Notes
    • Forum Thread – Stable Release: Xamarin 4, Cycle 6 – Service Release 4
    • Issues Addressed:
      • 39433 – Fixed an erroneous null reference exception being thrown by the Android Debugger in VS.
      • 38753 – Clicking “Xamarin for Visual Studio Update Available” notification in the toolbar will now properly trigger the appropriate Update UI.
      • 40022 – Selecting “Tools => Xamarin Account” should now properly recognize existing VS Professional license levels for Xamarin.
      • 36078 – XUnit Test Runner should no longer hang when a breakpoint is set in a test.

Upcoming Release Dates

Stable – This Release!

Evolve Keynote Releases!

UPDATE – We’ve added a new build of the Xamarin Profiler that is compatible with the Cycle 7 builds noted below. 

 

As you may have heard from Miguel during the Evolve 2016 Keynote session, we’re releasing a number of new builds to our Alpha and Beta channels, with many new features available to sample right now.

 

 


WEB PREVIEW – XAMARIN WORKBOOKS / INSPECTOR


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.


Products Released

 

 


WEB PREVIEW – iOS SIMULATOR (FOR WINDOWS)


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

 

 


WEB PREVIEW – XAMARIN PROFILER


Xamarin Profiler preview 0.33 is now available for download! There have been a number of fixes since our previous preview, which have been noted below.

Please note that the Mac app bundle has been renamed (from XamarinProfiler.Mac.app to “Xamarin Profiler.app”), so the old version needs to be removed before installing this new update, so that Xamarin Studio prompts the user for the new location.


Products Released

 

 


ALPHA RELEASE – CYCLE 8  FIRST PREVIEW


Our first preview of our newest upcoming feature release (called Cycle 8) can be downloaded from the Alpha channel.

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 to support this is not in this release, however it will be included in a future release of Cycle 8, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

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

NOTE – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Alpha channel.


Cycle 8 Alpha Known Issues

  • [Xamarin Studio / Xamarin.VS] – Updating your Xamarin.iOS, Xamarin.Android, or Xamarin.Mac to the builds noted below without also updating your IDE will prevent the IDE from properly running license checks, which can cause adverse functionality.
  • [Xamarin Studio – Windows Only] – You must have both MS Build Tools 2013 and MS Build Tools 2015 installed on your machine for Xamarin Studio to work properly on Windows.
  • [Xamarin.iOS] – Breakpoints may not hit for WatchKit applications when the Link All option is selected.
    • Workaround – Perform a “Clean” (or Rebuild) after switching the Link all option on.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

Cycle 8 Alpha Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 8 Alpha – This Release!

Cycle 8 Beta – Fall 2016

Cycle 8 Stable – Fall 2016

 

 


BETA RELEASE – CYCLE 7 RELEASE CANDIDATE


Our next major feature release, called Cycle 7, has had some Alpha and Beta previews out for awhile, but now we’re putting our first Release Candidate to the Beta Channel. We’re really close to finalizing this release, but need your help to hammer on these RCs and shake out any last issues that are hidden away.

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 to support this is not in this release, however it will be included in a future release of Cycle 7, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

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 – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Cycle 7 Release Candidate Known Issues

  • [Xamarin Studio / Xamarin.VS] – Updating your Xamarin.iOS, Xamarin.Android, or Xamarin.Mac to the builds noted below without also updating your IDE will prevent the IDE from properly running license checks, which can cause adverse functionality.
  • [Xamarin Studio – Windows Only] – You must have both MS Build Tools 2013 and MS Build Tools 2015 installed on your machine for Xamarin Studio to work properly on Windows.
  • [Xamarin.iOS] – Breakpoints may not hit for WatchKit applications when the Link All option is selected.
    • Workaround – Perform a “Clean” (or Rebuild) after switching the Link all option on.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

 

Cycle 7 Release Candidate Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 7 Alpha – March 10th, 2016

Cycle 7 Alpha 2 – March 15th, 2016

Cycle 7 Beta – April 11th, 2106

Cycle 7 Release Candidate – This Release!

Cycle 7 – May 2016

 

Beta: Cycle 7

We are releasing a Beta of our next major feature release, called Cycle 7. As this is an 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 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.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta – This Release!

Stable – April/May 2016

Stable Release: Cycle 6 Service Release 3

We are releasing the Stable builds of Service Release 3 on top of Cycle 6 (these have also been published in the Beta channel). Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.

For more information on the changes contained within these builds announced at Microsoft //Build, please check out the official Xamarin blog, and also the Xamarin FAQ.

Note that Alpha channel contains previews for our next feature release, which does not yet contain these changes. New Alpha builds will be available next week.


Products Released


Upcoming Release Dates

Stable – This Release!

Alpha Preview 2: Cycle 7

Update 1 – Bumped Xamarin.iOS from 9.8.0.58 to 9.8.0.156. This adds support for Apple iOS 9.3 / Xcode 7.3. 


We are releasing a new Alpha preview of our next major feature release, called Cycle 7. As this is an Alpha 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 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.


Known Issues

  • [Xamarin Studio w/ F# Add-in] – Error when creating an F# Android template on Windows. This should still function correctly on Mac.
  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [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.

Products Released


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – This Release!

Beta – March 2016

Stable – Late March / Early April 2016