Bug 24507 - UICatalog fails to launch on 32-bit devices with 8.5.0.176
Summary: UICatalog fails to launch on 32-bit devices with 8.5.0.176
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
: 24505 ()
Depends on:
Blocks:
 
Reported: 2014-11-13 17:53 UTC by Christopher Blackman
Modified: 2014-12-02 06:43 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Christopher Blackman 2014-11-13 17:53:19 UTC
UICatalog fails to launch on 32-bit devices using Xamarin.iOS 8.5.0.176. We've tested on an iPhone 6, 5C, 5S, and iPod touch 5th gen. The app launches correctly on the 64-bit iPhone 6 and 5S, but crashes at launch on the 32-bit 5C and iPod touch. It crashes before the Xamarin Studio debugger is able to connect.

All 3 available CPU architectures are selected in the 'iOS Build' project settings section (ARMv7 + ARMv7s + ARM64). The app works on all devices when building with Xamarin.iOS 8.4.0.39.

Crash log for UICatalog from Xcode: https://gist.github.com/ChrisBlackman/8b6afaf91a2dc8d92c60

Environment info:
====================

=== Xamarin Studio ===

Version 5.7 (build 441)
Installation UUID: 560ac8c1-3b61-43c9-9153-d18fe3a51e9a
Runtime:
    Mono 3.10.0 ((detached/c4d7214)
    GTK+ 2.24.23 (Raleigh theme)

    Package version: 310000029

=== Apple Developer Tools ===

Xcode 6.0 (6299)
Build 6A313

=== Xamarin.iOS ===

Version: 8.4.0.39 (Business Edition)
Hash: 6d89cd3
Branch: 
Build date: 2014-11-11 21:25:46-0500

=== Xamarin.Android ===

Version: 4.17.0.10 (Business Edition)
Android SDK: /Users/Chris/Library/Developer/Xamarin/android-sdk-macosx
    Supported Android versions:
        4.0.3  (API level 15)
        4.4.87 (API level 20)
Java SDK: /usr
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

=== Xamarin.Mac ===

Not Installed

=== Build Information ===

Release ID: 507000441
Git revision: 327273fc1c6e3d70defe261ec236dd4665442119
Build date: 2014-11-10 13:04:11-05
Xamarin addins: 1f4e96a5a6e6a76e4e2cdc58b8015b2d0d8cdece
Comment 1 Rolf Bjarne Kvinge [MSFT] 2014-11-14 08:57:23 UTC
This is from another app:

<Warning>: SgenThreadInfo:tlab_next_addr invalid struct offset 344 (expected 348)
<Warning>: SgenThreadInfo:tlab_temp_end invalid struct offset 580 (expected 584)
<Critical>: * Assertion at ../../../../../mono/mono/metadata/../../../mono-extensions/mono/metadata/metadata-cross-helpers.c:125, condition `!is_broken' not met

Assigning to Rodrigo since he's already said he's going to fix it.
Comment 2 Rodrigo Kumpera 2014-11-14 16:43:59 UTC
Fixed.

Rolf, could you add a testing step that check all target runtimes for the string "invalid struct offset"?

If this string is generated, the final binary is wrong and must not ship.
Comment 3 Christopher Blackman 2014-11-17 16:30:11 UTC
As mentioned by Rodrigo, this issue is now fixed. I've tested with 8.5.0.206, and the app builds and launches correctly on the 5C, 5S and iPod touch 5th gen.

I'll go ahead and close the issue.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2014-11-18 03:25:55 UTC
*** Bug 24505 has been marked as a duplicate of this bug. ***
Comment 5 Rolf Bjarne Kvinge [MSFT] 2014-12-02 06:43:22 UTC
Unit test added.

monotouch/master: f5a4ae0ebc7709835d2b711e54e9f2bc93a71907