Beta Release: XamarinVS 3.11.836, Cycle 5 – Service Release 3

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited August 2015 in Visual Studio

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


  • Xamarin.VisualStudio_3.11.836.msi (ed5c750)

Mac Build Host

  • monotouch- (2c66d2f)

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:

Date published: See

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

  • Bug 30958 - [iOS] "Invalid UIDeviceFamily - The Info.plist of Apple Watch application '' contains an invalid UIDeviceFamily value of '1'" when submitting WatchKit application. This appeared recently due to a change in the ckecks Apple performs during app submission. See for additional details.

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 4.")

  • 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 29731 - [Android] Android.Bluetooth.BluetoothAdapter.Enable is incorrectly marked as [Obsolete("deprecated")] for API level 20 and higher.

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

Remaining known issues from Cycle 5 – Service Release 2

  • Bug 31423 - [XamarinVS] [Android] [iOS] Locked .dll files: "Could not copy "... PortableClassLibrary1.dll" to "bin\Debug\PortableClassLibrary1.dll". Exceeded retry count of 10. Failed." This is a different problem than Bug 26841 because it affects .dll files rather than .dll.mdb files. It appears to be less common than Bug 26841. The results to date suggest that it is a bug in Visual Studio itself rather than in the Xamarin extensions. For example, it appears to be possible to hit the problem using a Windows Phone project, with no Xamarin involvement at all. The recent changes to the Xamarin "Clean project" process to properly remove stale files might have caused this to become easier to hit with Xamarin projects. In any case, it is still under investigation.

Remaining known issues from before the April 29 Stable Channel release

(For issues that might behave differently for some customers after updating to this new release, or that might be difficult to find via Bugzilla.)

  • Bug 28027 - [XamarinVS] [iOS] The debugger sometimes fails to connect properly after the app launches. This means breakpoints will not be hit during that launch of the app and the "Output -> Debug" window will be blank. Repeating the steps of (a) stopping the debugger and (b) relaunching the app will eventually lead to a successful connection. This problem has existed since at least XamarinVS 3.9.483, but some recent reports suggest that it has become more common for certain users recently. The problem might be caused by a race condition. Based on that guess, the recent releases might have changed some timings and increased the probability of hitting the issue on a wider range of system configurations. The bug is under active investigation.

  • Bug 29897 - [XamarinVS] [iOS] Breakpoints sometimes don't work when debugging on iOS device. Based on the observed behavior of this problem, it appears to have the same underlying cause as Bug 28027.

EDIT Aug 10: Mark iOS bug 30958 as fixed in new beta build (


  • opiantsopiants NZMember ✭✭

    I'm guessing no fix for intellisense and VS randomly freezing in this update as I don't see any mention of it?

  • LucaPinascoLucaPinasco ITMember ✭✭

    Are you working on VS randomly freezing?

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited August 2015

    no fix for intellisense

    Absent additional context, I will make a guess this is referring to one of the following bugs. Note that only Bug 32622 is directly tied to the XamarinVS versions. The other 2 bugs will be fixed within the Xamarin.Forms NuGet package, and so will likely only appear in the Xamarin.Forms release notes, and not in the XamarinVS release notes.

    • Bug 32622 - [XamarinVS] Intellisense shows errors in VS 2015 when referencing certain types in app projects from PCL projects (due to the new Roslyn-based Intellisense in VS 2015). (This one is a bug in the XamarinVS extensions themselves. It only affects VS 2015. The tentative plan is to ship the fix in Cycle 5 – Service Release 4 later this month, after Service Release 3 has been promoted to Stable.) Workaround: see Comment 4 on the bug report.

      Example error messages:

      • "The type 'Object' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version="
      • "The type 'Expression<>' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Linq.Expressions, Version="
    • Bug 32341 - [Xamarin.Forms] Intellisense on code behind files for XAML pages is not available for InitializeComponent() or for elements of the XAML page that include the x:Name attribute. (This is a bug in Xamarin.Forms. It affects all versions of Visual Studio.)

      See the Alpha release thread for the original discussion of that issue:

    • [Xamarin.Forms] Intellisense in VS 2015 does not work within XAML pages themselves, as discussed in the first comment on (This is a bug in Xamarin.Forms caused by a change in the "ownership" of Intellisense from the XamarinVS extensions into the Xamarin.Forms NuGet package. It only affects VS 2015.) Workaround: see the following two comments on the forum thread:

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai


    VS randomly freezing in this update


    Are you working on VS randomly freezing?

    There are a number of reported, unresolved XamarinVS bugs on Bugzilla that mention the string fragment "freez": see the corresponding Bugzilla query.

    Possible related bugs

    At a glance the most interesting ones from that list might be:

    • Bug 30056 - Editing multiple XAML files causes hang

    • Bug 32687 [VS 2015 on Windows 10] IDE freezes when clicking the Log In link on the Xamarin Welcome Page.

    Searching for "hang" instead

    Searching for the fragment "hang" turns up some other bugs that might be interesting. For example, here's one that was originally reported in the XamarinVS 3.11.666 release discussion:

    • Bug 31514 - Visual Studio hangs during second attempt to debug on Samsung Galaxy S4, Android 5.0. (This one includes several questions in Comment 1 for anyone seeing this issue. Those questions have not yet been answered.)

    Next steps

    If you can pinpoint whether you are seeing one of these existing bugs, feel free to report back on this thread about which one it is.

    If you have symptoms that do not match any of those existing bugs, you can also report back on this thread with additional details about the symptoms, file a new bug report, or (if you have a Business or higher license) contact Support.

  • opiantsopiants NZMember ✭✭

    @BrendanZagaeski Sorry, should've been more clear. Re intellisense, I was referring to Bug 32341 and this. The problem with VS randomly freezing seems to be related with the workaround you mentioned. Although, I can't be certain yet. Will go back to using resharper and see if it still freezes. I don't like using resharper though because it makes VS sluggish hence my necessity to get xamarin intellisense working again.

    Do you have a rough eta on the intellisense issues I mentioned?

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

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

    For issues about IntelliSense as well as other issues with Visual Studio 2015, I have now created a separate thread that is dedicated to that topic:

This discussion has been closed.