Bug 31304 - [iOS9] linksdk-dual test failure when built for release on 32-bit iOS9 device
Summary: [iOS9] linksdk-dual test failure when built for release on 32-bit iOS9 device
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: master
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: GouriKumari
Depends on:
Reported: 2015-06-22 17:21 UTC by Dylan Kelly
Modified: 2015-06-26 13:40 UTC (History)
3 users (show)

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:

Description Dylan Kelly 2015-06-22 17:21:11 UTC
On the current head of macios-mac-macios-cycle5-c5sr2 (248c95e), I was occasionally hitting one test failure on an 32bit iOS9 iPad2 with regards to BundledResources.dll with the release build of linksdk-dual. It did not fail consistently, however.

Steps to reproduce:
1) Build linksdk-dual for release
2) Deploy on an iOS9 32-bit device
3) Run tests

The BundledResources.dll ResourcesTest fails the following assert:
> file-basn3p08.png
> Expected: True
> But was: False

Supplemental info: The application crashes on a 32bit iOS9 iPad2 with the current alpha (https://gist.github.com/GouriKumari/36599b406a0d346721df)

Screencast of failure: http://www.screencast.com/t/cW2NxE8m

=== Xamarin Studio ===

Version 5.9.1 (build 3)
Installation UUID: a340c79e-e4b7-4348-8915-3696ea8e125e
	Mono 4.0.1 ((detached/ed1d3ec)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400010044

=== Apple Developer Tools ===

Xcode 6.3.2 (7718)
Build 6D2105

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/xamarinqa/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Not Installed

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 248c95e
Branch: master
Build date: 2015-06-20 10:58:19-0400

=== Build Information ===

Release ID: 509010003
Git revision: aad75a6e7e48f18120ce41f47d0ff2c6216f49c3
Build date: 2015-05-08 12:46:18-04
Xamarin addins: 1246b3044cbb7f56a217334f8fc5489ef8eefe3f

=== Operating System ===

Mac OS X 10.10.2
Darwin XQA-Yosemite-15.local 14.1.0 Darwin Kernel Version 14.1.0
    Mon Dec 22 23:10:38 PST 2014
    root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64
Comment 1 Sebastien Pouliot 2015-06-25 08:57:20 UTC
@Dylan please include 

1. the full build log (there's many options in release and that could happen only in very specific circumstances);

2. the full "Application Output" for both the failure and the crash.

Without them we do not know when they happens (and what happened just previously).
Comment 2 Dylan Kelly 2015-06-25 11:26:27 UTC
I am unable to reproduce this issue currently, so I am closing it until it possibly resurfaces. If it does, I will reopen and add the build log and application output.
Comment 3 GouriKumari 2015-06-26 13:40:29 UTC
Since, we couldn't reproduce this issue, I am reassigning the bug and taking it off the milestone. Will reopen, if the issue happens again as mentioned in comment #2.