Alpha Release: Xamarin Studio 5.9.4, Cycle 5 – Service Release 2

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/44148/beta-release-xamarin-studio-5-9-4-cycle-5-service-release-2/p1

For anyone who has been commenting on this thread, feel free to continue the conversation in that new thread.


Windows

  • XamarinStudio-5.9.4.5.msi (8010a90)

Mac

  • XamarinStudio-5.9.4.5.dmg (8010a90)

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/studio/xamarin.studio_5.9/xamarin.studio_5.9/#Xamarin_Studio_5.9.4

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

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

  • Bug 28961 - [iOS] "error MT3001: Could not AOT the assembly", "error: invalid symbol redefinition". (This can also appear as "System.ArgumentOutOfRangeException: startIndex > this.length" in the "Output -> Xamarin Log" in VS.) One common cause of this error is the use of [MethodImplAttribute(MethodImplOptions.Synchronized)]. Workaround for projects that use [MethodImplAttribute(MethodImplOptions.Synchronized)]: remove [MethodImplAttribute(MethodImplOptions.Synchronized)] and manually synchronize the methods using lock statements instead (https://bugzilla.xamarin.com/show_bug.cgi?id=28961#c6).

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

  • Bug 29211 - [iOS] Enabling the linker when the solution includes a PCL that uses System.IO.Compression causes "Could not load file or assembly 'System.IO.Compression' or one of its dependencies" at run time. The same problem can also happen with System.Threading.Tasks (and probably also several other assemblies). Workaround: add -linkskip=System.IO.Compression (or -linkskip=System.Threading.Tasks for System.Threading.Tasks) under "project options -> iOS Build -> Additional mtouch arguments".

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

  • 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 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 30420 - [iOS] DequeueReusableCell(cellIdentifier) returns null if this.TableView is called in the TableView constructor. Workaround: perform all initialization operations for the TableView in the ViewDidLoad() or ViewWillAppear() methods rather than the constructor.

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

New known issues

  • Non-public bug 30914 - [Android] "No resource found that matches the given name ... with value '@color/deep_purple_a200'". This issue will affect any color name that includes a capital letter, not just "deep_purple_A200".

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

  • Non-public bug 30984 - [Android] Profiling on the command line (for example via log:sample) produces 0-byte profile.mlpd files.


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.

Posts

  • GaborFurediGaborFuredi HUMember ✭✭

    @BrendanZagaeski I'm not sure if you are aware of the problem actually, so wanted to make sure it's on the radar. There's a bug mentioned above:

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

    I see exactly the same symptom, but I'm working on Mac and developing for iOS via Forms. PCL breakpoints do not work. Breakpoints inside custom renderers DO work. If I delete the bin directories, the next debug session works fine. After that, I need to remove the bin again.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @GaborFuredi, thanks for the report! (And apologies for the slow reply.)

    I believe there might have also been some fixes related to iOS breakpoints added between this Alpha version and the new Beta version that has just been released.

    I tried a few quick tests using these new Beta versions. I used the exact test case and steps to reproduce from Bug 30318, except that I modified them slightly to use Xamarin Studio on Mac with iOS. I was able to hit the breakpoints in the PCL project after ever clean, build, and deploy.

    If you are still able to reproduce a problem with breakpoints in Xamarin Studio on Mac with iOS after updating to the new Beta versions from today, then the Xamarin developers would definitely be interested in finding a way to reproduce the problem. Specifically, the most direct way forward would be if you would be able to zip up and attach a minimal test case that demonstrates the problem on a new bug report along with a numbered list of steps to reproduce. See also the bug filing KB article for some additional hints and tips about filing a bug report and minimizing the test case.

    Once you have filed a bug report, feel free to post back a link to it on the new forum thread for the Beta release:
    http://forums.xamarin.com/discussion/44148/beta-release-xamarin-studio-5-9-4-cycle-5-service-release-2/p1

    Thanks again!

  • 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/44148/beta-release-xamarin-studio-5-9-4-cycle-5-service-release-2/p1

    For anyone who has been commenting on this thread, feel free to continue the conversation in that new thread.

This discussion has been closed.