Bug 13203 - [ios sample] "Font List" gets crashes as soon as launch on Simulator 5.1
Summary: [ios sample] "Font List" gets crashes as soon as launch on Simulator 5.1
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: 6.3.x
Hardware: PC Mac OS
: High critical
Target Milestone: 6.4 (async)
Assignee: GouriKumari
Depends on:
Reported: 2013-07-12 08:32 UTC by Atin
Modified: 2013-08-01 07:56 UTC (History)
5 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 Atin 2013-07-12 08:32:40 UTC
Steps to reproduce:
1. Open 'Fontlist' sample in VS.
2. Debug or run the application.

Actual result:
Application crashes as soon as launches on simulator 5.1. However its working fine with ios device, This issue also exists with XS on mac.

Error logs on mac host:https://gist.github.com/saurabh360/14517a656095f25a776f
Expected result:
Application run successfully on Simulator

Environment details:
All mac
Windows 7
VS 2010/2012
Xcode 4.4.1
XS 4.0.10 (build 3)- d550634949488e5db108e5b48fc2e357c5f6b32f
Mono 3.1.1 ((no/c07cb68)
App info: monotouch-samples-master4638ae8895e6af6ba62ae30d0c7e28e92c6214b4

Regression status: REGRESSION, This is working fine with MT
Comment 1 Atin 2013-07-12 08:35:46 UTC
MTVS for above issue: 1.3.223
Comment 2 PJ 2013-07-12 12:24:14 UTC
> This issue also exists with XS on mac.

Thanks for giving this info, it makes it clear that the issue is in iOS and not in iOS for VS.

> However its working fine with ios device

Thanks - does it happen with both iOS 5 and 6(.1) simulators, and on both iPad and iPhone?
Comment 3 Mohit Kheterpal 2013-07-12 13:41:16 UTC
An update of the above issue:

This issue exists only on ios simulator 5.1, While its working fine on ios simulator 6.1.
Its also working fine with ios device 6.1.3 and ios device 5.1.1
Comment 4 Atin 2013-07-12 13:44:20 UTC
This issue also exists with other ios sample:

Sound sample,Simple Text Input, Notification,Core location, Custom propertyAnimation
Comment 5 Sebastien Pouliot 2013-07-12 16:28:49 UTC
Works fine for me.

Do you have some other apps working on the 5.1 simulator ?

Did you try to reset your simulator ?
Comment 6 PJ 2013-07-12 21:00:44 UTC
I was also unable to reproduce this issue. I did see some application output spew running this sample and the Simple Text sample when switching from 5.0 to 5.1 simulator this afternoon, but it went away when I reset the simulator, didn't affect the behavior of the application, and it didn't survive on my clipboard before something else took my attention away from this bug, unfortunately.

I figured I would report my inability to reproduce as well, though! Please try resetting the simulator as suggested in comment 5.
Comment 7 narayanp 2013-07-15 05:32:13 UTC
Today we have checked this issue after reset the iOS Simulator on following builds:

VS 2012/2010
Xamarin.iOS 6.3.8-5
iOS for VS 1.3.227
Xcode 4.3.3

We are still seeing that when application launching on iOS Simulator, it get crashed. We checked it after reset the iOS Simulator
Comment 8 Atin 2013-07-15 11:29:22 UTC
An update to the above issue:

Application run successfully with machine having Xcode 4.6.
Comment 9 PJ 2013-07-15 14:10:53 UTC
The iOS team on the call today said that if this issue is not reproducible with the latest Xcode, they won't be able to do anything about it. RESOLVING as WONTFIX.
Comment 10 Atin 2013-08-01 07:56:35 UTC
As per comment 9 marking this as Verified Wontfix.