This thread has now been closed to direct all further updates about this service release onto the new Stable release thread:
For anyone who has been commenting on this thread, feel free to continue the conversation in that new thread.
Reason for release: Bug fixes for the 3.11.445 Stable Channel release on April 29.
May 19, 2015: 3.11.576 published to Beta and Alpha updater channels
See the corresponding Alpha release thread (now closed) for the earlier history of this service release: http://forums.xamarin.com/discussion/40277/alpha-service-release-xamarinvs-3-11-570-bug-fixes-for-3-11-445/p1
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.
You can downgrade back to the current Stable version by switching updater channels.
You can downgrade back to the previous Stable versions (from before April 29) by manually reinstalling each old package (see also the article about downgrading). The links to the previous Stable versions are:
This first post will be updated regularly.
Hopefully this thread will help answer "what might break if I update to this release?"
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).
Please discuss older bugs that are unchanged in this release compared to the previous Stable version in Bugzilla instead.
Of course for questions and discussions about topics other than bugs, feel free start new forum threads.
(The fixes for most of these remaining issues are scheduled to be released in the next service release. The first Alpha versions of that release will be published shortly after this current Beta is promoted to Stable.)
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 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.
Bug 30371 - [Visual Studio] [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).
Non-public Bug 30059 - [XamarinVS] [iOS] "Mono.Debugger.Soft.CommandException: Debuggee returned error code 200." when hitting breakpoints in PCLs in certain projects when running XamarinVS on certain computers.
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.
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.Threading.Tasks for System.Threading.Tasks) under "project options -> iOS Build -> Additional mtouch arguments".
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: downgrade Xamarin.Insights to version 1.9, or remove it entirely.
Bug 30420 - [iOS]
this.TableView is called in the TableView constructor. Workaround: perform all initialization operations for the TableView in the
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
LinkerFlags) try removing it.
Non-public Bug 29538 - [Android] Profiling via the graphical Xamarin Profiler ("Run -> Start Profiling") causes the app to crash at startup.
Bug 29849 - [XamarinVS] [iOS] The "Visual C# -> Mobile Apps -> Blank App (Xamarin.Forms Portable)" template includes an iOS project that has a non-empty value for the
<CodesignEntitlements> property for the iPhoneSimulator configurations, meaning that the iPhoneSimulator configuration will attempt to perform code signing. This is inconsistent with the other templates and also with the corresponding Xamarin Studio template on Mac. Workaround: open the
.csproj file in a text editor and delete the
<CodesignEntitlements> property from all of the iPhoneSimulator configurations.
Bug 29731 - [Android]
Android.Bluetooth.BluetoothAdapter.Enable is incorrectly marked as
[Obsolete("deprecated")] for API level 20 and higher.
(For issues that might behave differently for some customers after updating to this new Beta 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 in this latest release. To make a reasonable guess, the problem might be caused by a race condition. Based on that guess, this new version 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.
obj/iPhone/Release/ipa/iTunesMetadata.plistfile and build again.)
EDIT May 19: Initial post for Beta releases.
EDIT May 19: Small improvement in XamarinVS Bug 28027: the stop debugging button will no longer pause VS for 2 minutes.
EDIT May 19: Increase severity ranking of Android Bug 28995 based on additional customer reports.
EDIT May 21: Add Mono Bug 30171, Android Bug 30057, iOS Bug 30059.
EDIT May 21: Add Android Bug 30318, Xamarin Studio Bug 30072.
EDIT May 27: Add XVS.Android Bug 30371.
EDIT May 27: Update bugs fixed by latest Beta versions. (30171, 30241)
EDIT May 28: Add Android Bug 30548, iOS Bug 30420.