Alpha Release: Xamarin Studio 5.9.5, Cycle 5 – Service Release 3

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

This thread has now been closed to direct all further updates about this service release onto the new Beta release thread:

http://forums.xamarin.com/discussion/47345/beta-release-xamarin-studio-5-9-5-cycle-5-service-release-3/p1


Windows

  • XamarinStudio-5.9.5.6.msi (c50b102)

Mac

  • XamarinStudio-5.9.5.6.dmg (c50b102)

Reason for release: Additional bug fixes for the "Cycle 5" Stable Release on April 29 and the previous Cycle 5 Service Releases. (See the release blog for a short description of "Cycles" and "Service Releases.")

Release notes: http://developer.xamarin.com/releases/studio/xamarin.studio_5.9/xamarin.studio_5.9/#Xamarin_Studio_5.9.5

Date published: See https://releases.xamarin.com/.

NOTE: Alpha versions have not yet completed the full suite of tests by the Xamarin QA team. That said, customer reports of any regressions (or bugs that are incorrectly marked fixed) are still much appreciated, even if the problem would have eventually been caught during the full QA testing process.

Previous versions, downgrading

You can downgrade back to the current Stable version by switching updater channels.

Older versions (from before April 29)

If needed, you can downgrade back to older versions (from before April 29) by manually reinstalling each old package. See the "Previous versions, downgrading" section on the April 29 Stable release thread for the older downgrade links.

Guidelines for this thread

  1. This first post will be updated regularly.

  2. Hopefully this thread will help answer "what might break if I update to this release?"

  3. If you find a new problem that is specific to this version, please file a bug report.

  4. Please discuss older bugs that are unchanged in this release compared to the previous Stable version in Bugzilla instead.

  5. Of course for questions and discussions about topics other than bugs, feel free start new forum threads.

Fixes for known issues from recent releases

  • Bug 31527 - [Android] "The following assembly referenced from ... could not be loaded: Assembly: System.Runtime ... Version: 4.0.0.0" when using the "Shared Runtime" with the linker enabled. Workaround: set "Project Options -> Android Build -> Linker [tab] -> Linker behavior" to "Don't link" in Xamarin Studio or "Project Properties -> Android Options -> Linker [tab] -> Linking") to "None" in Visual Studio. Enabling linking when the "Shared Runtime" is enabled is an intentionally untested scenario (partly because the on-device "shared runtime" assemblies will necessarily never be linked).

  • Bug 31597 - [Android] For some projects the generated .mdb files are incorrect, causing breakpoints to be skipped or incorrect line numbers to appear in the call stacks. Possible workaround: add Condition="'$(AndroidLinkMode)' != 'None' AND '$(AndroidUseSharedRuntime)' != 'true'" to the StripEmbeddedLibraries task in C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets on Windows or /Library/Frameworks/Xamarin.Android.framework/Versions/Current/lib/xbuild/Xamarin/Android/Xamarin.Android.Common.targets on Mac.

Remaining known issues from the April 29 Stable Channel release, with more common or severe issues near the top

  • Bug 30513 - [Android] The logged stack traces from exceptions thrown within async methods do not include the actual location where the exception was thrown. Partial workaround: switch back to the old Xamarin.Android 4.x exception propagation style by setting the XA_BROKEN_EXCEPTION_TRANSITIONS environment variable to true (see also Bug 30513, Comment 11).

  • Bug 29326 - [Android] String resources defined in NuGet packages overwrite string resources defined in app project, causing the displayed app name to be incorrect for example. Workaround: avoid using the same string key that is used in the NuGet packages.

  • Non-public Bug 30481, Bug 29557 - [Mono] [Android] [iOS] SqlConnection.GetSchema() fails with "SourceTable is required to be a non-empty string". (A fix for this issue is planned for the upcoming "Service Release 3.")

  • Bug 30548 - [Android] Under certain conditions new threads take several seconds to start. This problem seems to be triggered by Xamarin.Insights 1.10. Partial workarounds: upgrade Xamarin.Insights to version 1.10.3, downgrade to version 1.9, or remove it entirely.

  • Bug 29745 - [iOS] Error due to duplicate symbols during native compilation for device: "duplicate symbol _monoeg_g_array_new" (and many similar messages). Workarounds: disable profiling under "Project Properties -> iOS Build", or if your app uses the -all_load linker flag (via either gcc_flags or LinkerFlags) try removing it.

  • Bug 28808 - [Xamarin Studio] Uncommon "Too many open files" error, possibly related to keeping a solution open in Xamarin Studio across several sleep/wake cycles, leads to an inability to save the solution, and consequently a loss of the solution file contents.

  • Bug 29001 - [Xamarin Studio] Under certain conditions, clicking in the universal search bar can trap the cursor focus, preventing text entry into the text editor window.

  • Bug 30915 - [Xamarin Studio] [Android] Xamarin Studio repeatedly asks for the password for the selected certificate when attempting to sign using SHA1withDSA certificates from keystore files. Xamarin Studio should instead display the error message from jarsigner: "private key algorithm is not compatible with signature algorithm" as it did in Xamarin Studio 5.8. (SHA1withRSA or MD5withRSA certificates do work without error.)

  • Bug 29731 - [Android] Android.Bluetooth.BluetoothAdapter.Enable is incorrectly marked as [Obsolete("deprecated")] for API level 20 and higher.

  • [Xamarin Studio] Xamarin Studio 5.9 for Mac requires OS X 10.9 or higher. The updater does not currently block this update on OS X 10.8. The behavior of the updater for this kind of version incompatibility will be improved in the future.

  • Bug 31379, Bug 31560 - [iOS] Enabling the linker when the app references PCL projects that include "duplicate" System.Threading.Tasks references (for example when using the "Microsoft.Net.Http" NuGet in a .NET 4.0 PCL) causes "Could not load file or assembly 'System.Threading.Tasks'" on the simulator. This bug has in fact existed since the original April 29 release of Cycle 5, but until Service Release 2 it had been obscured by the closely related Bug 29211. The bug only affects simulator builds and has fairly easy workarounds, so it is minor in severity. Workarounds: disable the linker in the iPhoneSimulator configurations or add -linkskip=System.Threading.Tasks under "project options -> iOS Build -> Additional mtouch arguments".

New known issues

  • Non-public Bug 32298 - [Xamarin Studio] [iOS] Applications with . dot/period characters in the assembly name crash when launching in the Release configuration on iPhoneSimulator. The simulator log shows "Could not find the assembly MyApplication.exe", when the name of the assembly is in fact "My.Application.exe".

EDIT July 21: Add Android bug 30513.
EDIT July 24: Update version numbers for new Alpha builds. Remove now fixed iOS bug 31893. Add Mac-only iOS Bug 32298.

Posts

  • CinderRoxleyCinderRoxley USMember
    edited July 2015

    Is there any way I can get the installer files for this so I can manually install? I don't have Xamarin Studio currently installed and can't install the release version on OS X 10.11 DP3.

  • Is the problem that XS does not start on El Capitan beta 3 also resolved. If so, please make a download available since i can't update using the existing installation. Thanks!

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @CinderRoxley, if you're looking for just the Xamarin Studio installer file, you can find it on:

    https://store.xamarin.com/account/my/subscription/downloads

    Under the "View all versions" link. (See also the screenshot at the bottom of the KB article on downgrading). If you have an Indie license or higher, this page will also show versions of the other Xamarin installer packages. If you have a Starter or Trial account and you're looking for the other installer links, feel free to send an email to contact@xamarin.com to request whichever installer packages you'd like.

    All that said, as pointed out be Leendert, the OS X 10.11 El Capitan Beta still has some known issues with Xamarin. The developer team is working to resolve the issues before the El Capitan stable release. As mentioned in Apple's El Capitan Beta release notes,

    Do not use this prerelease software in a commercial operating environment or with important data.

    The latest Xamarin update about OS X 10.11 El Capitan support can be found on the Xamarin Release Blog here: https://releases.xamarin.com/ios9-elcapitan-preview-technical-bulletin/. Feel free to subscribe to that blog to receive updates about new releases, including news about OS X 10.11 El Capitan support.

  • CinderRoxleyCinderRoxley USMember

    Thanks, Brendan. Someone on the twitter account sent me a link the download. I've run into a few issues and certainly can't expect perfection running development previews, but it's great to be able to get back to work!

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    This thread has now been closed to direct all further updates about this service release onto the new Beta release thread:

    http://forums.xamarin.com/discussion/47345/beta-release-xamarin-studio-5-9-5-cycle-5-service-release-3/p1

This discussion has been closed.