Bug 7641 - App built using 6.0.2 (and 6.0.3) doesn't run on iOS5 (on device)
Summary: App built using 6.0.2 (and 6.0.3) doesn't run on iOS5 (on device)
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-10-04 08:47 UTC by Andrew.Tait
Modified: 2012-10-04 14:25 UTC (History)
2 users (show)

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

Symbolicated crash log (20.18 KB, application/octet-stream)
2012-10-04 08:47 UTC, Andrew.Tait

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 Andrew.Tait 2012-10-04 08:47:26 UTC
Created attachment 2685 [details]
Symbolicated crash log

We've got a couple of apps that we've rebuilt using MT 6.0.2/3. Both of them run fine under iOS6, but are crashing immediately on iOS5. They previously ran OK under iOS5, when built with MT 5.x.

I attach a symbolicated crash log from one of the applications. The only app code being run seems to be main. Can you offer any guidance as this is preventing us from submitting iPhone 5 updates?
Comment 1 Sebastien Pouliot 2012-10-04 09:00:53 UTC
The original exception comes from ObjC (with some C++) too. MonoTouch catch that (unhandled) exception before throwing it back (that's normal) so we need to dig the original root cause.

1. Did you try this on the iOS 5.x simulator(s) ?

2. Can you look at the Console (from Xcode) to see what message were logged just before the crash. There's likely some message(s) that will hint us about the condition.

3. Can you attach (you can mark is as private) the full build log of the application ? (as found in "Built Output", inside MonoDevelop's "Error List" pad). 

Also before re-building your application please add "-v -v -v" to your project's options ("mtouch additional arguments") so we have more details about it.
Comment 2 Andrew.Tait 2012-10-04 14:25:56 UTC
Drat. Sorry. It was a result of replacing a deprecated property that turned out to be iOS 6 only. Once I worked out how to install the old simulators, it became clear. Thanks for the pointer.