Stable service release: Xamarin.Android 5.1.2, bug fixes for 5.1.0

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

Released versions:

Windows

  • Xamarin.VisualStudio_3.11.586.msi (a91e30d)
  • Xamarin.VisualStudio_3.11.590.msi (5160db7) (Hotfix)

Mac

  • mono-android-5.1.2-1.pkg (4ab8d98)
  • mono-android-5.1.3-1.pkg (d419c93) (Hotfix)
  • MonoFramework-MDK-4.0.1.44.macos10.xamarin.x86.pkg (ed1d3ec)

Reason for release: Bug fixes for the 5.1.0.115 Stable Channel release on April 29.

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

Date published:

Previous versions, downgrading

You can downgrade back to the previous Stable versions (from April 29) by manually reinstalling each old package (see also the article about downgrading). The links to the previous Stable versions are:

Windows

Mac

Older versions (from before April 29)

If needed, you can also downgrade back to the 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 (if this link redirects to the top-level https://kb.xamarin.com/ page the first time you click it, try clicking it once more).

  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.

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

(Candidate fixes for many of these remaining issues are now available on the Alpha updater channel.)

  • Non-public Bug 28995 - [Android] On certain devices, certain apps crash frequently due to "System.ExecutionEngineException: SIGILL". Now fixed in the Beta and Alpha channels.

  • Bug 30318 - [Android] Windows only: Breakpoints in PCL projects do not work after cleaning solution, redeploying, and restarting debugging. Now fixed in the Beta and Alpha channels. (Old partial workaround: delete all the bin folders in the solution after cleaning.)

  • 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. Now fixed in the Beta and Alpha channels.

  • 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). Now fixed in the Beta and Alpha channels.

  • 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 it to version 1.9, or remove it entirely.

  • 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. Now fixed in the Beta and Alpha channels.

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

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

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


EDIT June 3: Update version numbers for Android M Preview SDK hotfix. Add Mono Bug 30481.
EDIT June 4: Adjust wording about downgrading to "older versions."
EDIT June 10: Mark bugs that are now fixed in the Alpha channel "Service Release 2" (28961 28995 30371 29211 30072 29538 29849 29725)
EDIT June 11: Correction: the fixes for 30318 and 30057 will be in the next Alpha build, which should be available in less than 1 week.
EDIT June 23: Mark additional bugs that are now fixed in the Beta channel "Service Release 2" (30318 30057 30420). Add XS Android bug 30915.

Posts

  • JeremyKolbJeremyKolb USMember ✭✭✭

    People area complaining about GC issues with this release: http://forums.xamarin.com/discussion/42460/is-gc-broken-xamarin-visualstudio-3-11-445

  • MihaMarkicMihaMarkic SI ✭✭✭✭
    edited June 2015

    How is bug 30548 even possible? I mean a library that slows down Thread creation?

  • JeremyKolbJeremyKolb USMember ✭✭✭

    @MihaMarkic I think it's actually a Xamarin.Insights bug. One of the reports shows that they scrape a log and that probably takes a long time so they exhaust the thread pool or something... not sure but it's a big problem for one of our customers.

  • MMountainMMountain USMember ✭✭
    edited June 2015

    ** Delete **

  • MihaMarkicMihaMarkic SI ✭✭✭✭
    edited June 2015

    @JeremyKolb If that's true then it is really a bad design (Insights' design that is).

  • ChristineBlandaChristineBlanda USMember ✭✭✭

    With this build the code is not breaking on breakpoints in the portable code using VS against the Android Simulator or an iOS device, and using XS (on Windows) against the Android Simulator.
    Breakpoints in the Android project's MainActivity do hit and breakpoints in the iOS project's Main sometimes hit.
    in XS on the Mac against an iOS device the breakpoint in the portable code did hit .. but the page didn't come forward so I noticed the app wasn't responding and had to go find it.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited June 2015

    breakpoints in the portable code using VS against the Android Simulator ... and using XS (on Windows) against the Android Simulator.

    That is most likely the "remaining known issue" Bug 30318 noted in the first post in the thread. See:

    http://forums.xamarin.com/discussion/comment/126361/#Comment_126361

    and

    http://forums.xamarin.com/discussion/comment/127653/#Comment_127653

    ... from the Beta release threads for some additional context as well as some project settings to double-check.

    As a quick first check to see if project settings might be causing a problem, you can try creating a "new from template" Android App + PCL solution, and see if the breakpoints work any better there.

    • The default "good" configuration for debugging contains the following lines if you open the Android app's .csproj in a text editor:

        <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
          <DebugSymbols>true</DebugSymbols>
          <DebugType>full</DebugType>
          <Optimize>false</Optimize>
          <OutputPath>bin\Debug</OutputPath>
          <DefineConstants>DEBUG;</DefineConstants>
          <ErrorReport>prompt</ErrorReport>
          <WarningLevel>4</WarningLevel>
          <AndroidLinkMode>None</AndroidLinkMode>
          <ConsolePause>false</ConsolePause>
        </PropertyGroup>
      
    • The following "bad" properties should be removed if present:

      • <BundleAssemblies>true</BundleAssemblies>
      • <AndroidUseSharedRuntime>false</AndroidUseSharedRuntime>
    • The following "good" properties should be added or corrected if they are missing or incorrect:

      • <DebugSymbols>true</DebugSymbols>
      • <AndroidLinkMode>None</AndroidLinkMode>

    With this build the code is not breaking on breakpoints in the portable code using VS against ... an iOS device

    iOS project's Main sometimes hit

    That sounds like Bug 28027, which is not mentioned on this (Xamarin.Android) release thread, but it is mentioned on the XamarinVS and Xamarin.iOS release threads.

  • ChristineBlandaChristineBlanda USMember ✭✭✭

    Thanks, I tried those suggestions but still have the issue. Hopefully it will be fixed soon.

  • SimonWainwrightSimonWainwright GBMember ✭✭

    Have you had any luck with the debug symbols Christine? I have the same issue and have tried the suggestions above

  • ClintonLandryClintonLandry USUniversity
    edited June 2015

    In relation to the System.Deployment when I rolled back to the suggested version at the top of the thread I do not see it on emulators only on actual devices and only when linking either SDK assemblies or all.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    So far the one report against Xamarin.Android 5.1 about a "System.Deployment" error message was explained by the fact that the project referenced Microsoft.VisualBasic.dll. Microsoft.VisualBasic.dll does not exist in the Xamarin.Android profile. See Bug 30633, Comment 4 for some additional discussion.

    Exception while loading assemblies: System.IO.FileNotFoundException: Could not load assembly 'System.Deployment, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Perhaps it doesn't exist in the Mono for Android profile?

  • rogiheerogihee NLMember ✭✭✭
    edited July 2015

    -meant for other thread-

  • ClintonLandryClintonLandry USUniversity

    Confirmed on the below spec with no references to VisualBasic I do not see the System.Deployment issue.

    === Xamarin Studio ===

    Version 5.9.4 (build 5)

    Runtime:
    Microsoft .NET 4.0.30319.34209
    GTK+ 2.24.22 (MS-Windows theme)
    GTK# 2.12.26

    === Xamarin.Android ===

    Version: 5.1.4 (Business Edition)
    Android SDK: E:\Users\Clinton-Dev\AppData\Local\Android\android-sdk
    Supported Android versions:
    2.3 (API level 10)
    4.0.3 (API level 15)
    4.1 (API level 16)
    4.2 (API level 17)
    4.3 (API level 18)
    4.4 (API level 19)
    4.4.87 (API level 20)
    5.0 (API level 21)
    Java SDK: E:\Program Files (x86)\Java\jdk1.6.0_45
    java version "1.6.0_45"
    Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
    Java HotSpot(TM) Client VM (build 20.45-b01, mixed mode, sharing)

    === Xamarin Android Player ===

    Not Installed

    === Build Information ===

    Release ID: 509040005
    Git revision: 8010a90f6e246b32364e3fb46ef2c9d1be9c9a2b
    Build date: 2015-06-08 17:16:25-04
    Xamarin addins: 7e93e9c3503f28770f23ce1b7eafd829919f18e8

    === Operating System ===

    Windows 6.2.9200.0 (64-bit)

  • ColinPhillipsColinPhillips USMember

    I was previously able to compile referencing some DLLs (the app is in production referencing these DLLs) that are written in Visual Basic. They are business objects / manager code.

    After updating Xamarin, I am unable to compile with the following error:
    Exception while loading assemblies: System.IO.FileNotFoundException: Could not load assembly 'Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Perhaps it doesn't exist in the Mono for Android profile?
    File name: 'Microsoft.VisualBasic.dll'
    at Xamarin.Android.Tuner.DirectoryAssemblyResolver.Resolve(AssemblyNameReference reference, ReaderParameters parameters)
    at Xamarin.Android.Tasks.ResolveAssemblies.AddAssemblyReferences(ICollection`1 assemblies, AssemblyDefinition assembly, Boolean topLevel)
    at Xamarin.Android.Tasks.ResolveAssemblies.Execute()

    I uninstalled Xamarin as well as Visual Studio, reinstalled using the April 29th version without success.

    Please advise as I am unable to compile whatsoever and have exhausted all known options.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited July 2015

    ColinPhillips, as hinted at a few comments ago, that error message is accurate: Xamarin.Android does not include a "Microsoft.VisualBasic" assembly.

    I am not too familiar with how Visual Basic .dll files interoperate with C# .dll files, but one guess is that the error you are seeing might indicate that the Visual Basic library is not a Portable library (PCL). Xamarin will only work with Visual Basic libraries if they are PCLs (and if the selected PCL profile includes "Xamarin.Android" under "Project Properties -> Library -> Targeting"). This requirement corresponds to the following statement from the documentation:

    Xamarin.Android is not ABI compatible with existing assemblies compiled for a different profile...

    (From http://developer.xamarin.com/guides/android/under_the_hood/assemblies/)

    If non-PCL VB libraries worked in the past, it would have only been "by luck," and not something that was intentionally supported by Xamarin.Android.

    Hope this helps clear things up!

This discussion has been closed.