If only it were that simple… connecting it to the debugger got it to crash at exactly the same “place” as where the exception report came from – it did not crash anywhere in my code even with Debug\Exceptions set to stop on every single exception. It just starts at the catch block in the Main function.
Dino From: Richard Heesbeen [mailto:[email protected]] Sent: Tuesday, October 16, 2012 10:58 To: Dean Cleaver Cc: [email protected] Subject: Re: [MonoTouch] Any idea what this could be? If it can be reproduced, then finding the problem shouldn’t be that hard get your CEOs devices and connect them to your mac and run the app in debug mode and make it crash. Then look at the stacktrace and you are likely to see where it is originating from. If not put a lot of debug messages in the code to try and find the problem that way. If your CEO can make it crash but you can’t he is probably doing something you aren’t or in a different order. In short you need to get your CEOs devices and start to debug for real. Richard. From: Dean Cleaver<mailto:[email protected]> Sent: Saturday, October 13, 2012 6:42 AM To: Craig Dunn<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> ; James Darbyshire<mailto:[email protected]> Subject: Re: [MonoTouch] Any idea what this could be? It seems to be easily reproducible on given devices and iOSs – but not always. iOS6 seems fine on all 3 devices (4S, 4 and iPod Touch) I have here, but it crashes on my CEOs iPad 2 with iOS6 and his 4S with iOS5. I need to grab them off him to see if I can find a pattern, but he seems to get consistent crashes regardless. I could do a diff, but there’s been so many check-ins in the past week, and the project is about 200 files, so to check each one, see what’s changed etc could be a mammoth task. Nothing had changed in the area I’m seeing problems in though – that I already checked. Dino
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
