Beta service release: Xamarin.iOS 8.10.1, bug fixes for 8.10.0

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

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/42673/stable-service-release-xamarin-ios-8-10-1-bug-fixes-for-8-10-0/p1

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


Released versions:

Windows

Mac

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

Release notes: http://developer.xamarin.com/releases/ios/xamarin.ios_8/xamarin.ios_8.10/#Xamarin.iOS_8.10.1

Date published:

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.

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:

Windows

Mac

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 common old known issues from previous releases

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

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

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

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

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

New known issues compared to 8.10.0.267

  • Bug 30241 - Now fixed in the latest Beta and Alpha builds. [iOS] "Failed to move 'obj/iPhone/Release/ipa/Payload/UnifiedSingleViewIphone1.app/iTunesMetadata.plist' to 'obj/iPhone/Release/ipa/iTunesMetadata.plist': Win32 IO returned ERROR_ALREADY_EXISTS. Path:" when building app again without cleaning. (Old workaround: clean the iOS application project and build again, or delete just the destination obj/iPhone/Release/ipa/iTunesMetadata.plist file 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.

Posts

This discussion has been closed.