Beta Release: Xamarin.Android 5.1.4, Cycle 5 – Service Release 2

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited June 2015 in Xamarin.Android

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

http://forums.xamarin.com/discussion/44632/stable-release-xamarin-android-5-1-4-cycle-5-service-release-2/p1


Windows

  • Xamarin.VisualStudio_3.11.666.msi (ebae43a)

Mac

  • mono-android-5.1.4-16.pkg (5f55a9e)

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

Release notes: http://developer.xamarin.com/releases/android/xamarin.android_5/xamarin.android_5.1/#Xamarin.Android_5.1.4

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

NOTE: Beta 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 previous 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 widely reported known issues from older releases

  • Bug 26841 - [XamarinVS] [Android] [iOS] "The process cannot access the file ... MyApplication.dll.mdb because it is being used by another process" after debugging an app, stopping debugging, and starting debugging again.

Fixes for remaining known issues from the April 29 Stable Channel release

  • Non-public Bug 28995 - [Android] On certain devices, certain apps crash frequently due to "System.ExecutionEngineException: SIGILL".

  • Bug 30318 - [Android] Windows only: Breakpoints in PCL projects do not work after cleaning solution, redeploying, and restarting debugging. Partial workaround: delete all the bin folders in the solution after cleaning. (The next Alpha build should include this fix.)

  • Bug 30371 - [XamarinVS] [Android] Project Properties display incorrect default values for "BundleAssemblies" and "EmbedAssembliesIntoApk" if they are not explicitly specified. This means that these properties can "automatically" change to incorrect values when you update other properties under "Project Properties -> Android Options". The incorrect values can cause secondary symptoms like Bug 30334 where breakpoints are not hit in the Debug configuration.

  • Non-public Bug 30057 - [Android] Windows only: the debugger will not be able resolve breakpoints unless "Shared Runtime" is ON and the Linker is OFF (under "Project Properties -> Android Options" in Visual Studio or "Project Options -> Android Build" in Xamarin Studio). (The next Alpha build should include this fix.)

  • Bug 30072 - [Xamarin Studio] [Android] Xamarin Studio sometimes crashes with SIGABRT in gtk_text_view_validate_onscreen() after password is entered during "Import an Existing Key" in "Build -> Archive for Publishing -> Sign and Distribute" workflow.

  • Non-public Bug 29538 - [Android] Profiling via the graphical Xamarin Profiler ("Run -> Start Profiling") causes the app to crash at startup.

  • Non-public Bug 29725 - [Xamarin Studio] [iOS] [Android] Expressions in the Watch window are cleared each time you stop debugging.

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

  • 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".

  • 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 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.

New known issues

  • Non-public bug 30990 - [Android] Assertion failure at run time "condition `cur_slot == class->vtable_size' not met" for AOT'd apps on some x86 devices.
This discussion has been closed.