public etc RowsInSection(....){
try
{
//do your existing stuff
} catch (Exception ex)
{
//write it out to a file, to the console (Debug.WriteLine), show
it to the user etc
}
}
Usually works, but not always.
On Sat, Sep 15, 2012 at 1:38 AM, Liam <[email protected]> wrote:
> Hi Rolf
>
> Thank you for your answers.
>
>
> "Maybe you can try to add an exception handler to
> App.MonoTouch.NextToGoRacesViewController.TableDataViewSource:RowsInSection,
> logging the exception?"
>
> What exactly do you mean by "logging the exception"?
>
> I have not been able to reproduce this crash so I am not sure how I could
> log the exception so that I could read it after the app crashes during the
> app store review.
>
>
> Thanks
> Liam
>
>
>
>
> On 15/09/12 12:04, Rolf Bjarne Kvinge wrote:
>
>
>
> On Sat, Sep 15, 2012 at 1:20 AM, Liam <[email protected]> wrote:
>>
>> Hi Everyone
>>
>> My app has been rejected for crashing. I cannot and have not been able to
>> reproduce what the app store review has described crashes my app.
>>
>> I have symbolicated the crash logs but not all of the symbols from my code
>> are symbolicated...
>>
>> Looking around online it seems that other people have this problem and
>> there doesn't seem to be a definitive solution. Or maybe this is just
>> normal?..
>>
>> The steps that I took to symbolicate are:
>>
>> 1. Copy the Application.app, Application.dSYM and crash reports into the
>> same folder.
>> 2. Open XCode organizer.
>> 3. Go to Device logs and click import.
>> 4. Select the crash files and import them.
>>
>> I have also run dwarfdump --uuid to confirm that the .app and .dSYM files
>> are the same build.
>>
>> When I say not all of the symbols are symbolicated what I mean is that
>> only one reference to my code has been symbolicated. Here is a link to the
>> symbolicated file
>> https://docs.google.com/file/d/0B5ghoqfnILgZVGJuUElNOGNVQTA
>>
>> So my questions are:
>>
>> 1. Is this one reference to my code (Thread 0: 17) the problem which is
>> crashing my app?
>
>
> Frame #17 is a transition from native code into managed code, frame #14
> would be what frame #17 looks like (i.e. the actual managed implementation
> of
> App.MonoTouch.NextToGoRacesViewController.TableDataViewSource:RowsInSection),
> and the bad stuff happened in frame #13 (which would be a method
> App.MonoTouch.NextToGoRacesViewController.TableDataViewSource:RowsInSection
> called).
>
> My guess is that an exception is thrown, and the process is killed since
> there is exception handler to handle the exception. Maybe you can try to add
> an exception handler to
> App.MonoTouch.NextToGoRacesViewController.TableDataViewSource:RowsInSection,
> logging the exception?
>
>>
>> 2. When building the app for the app store in order to get proper
>> symbolicating do I have to select "Enable debugging"?
>
>
> It should just work if you're using MonoTouch 5.4.
>
>>
>> 3. Is there anything that I can do with this crash file to resolve the
>> references that have not been symbolicated?
>
>
> Unfortunately no, there is nothing you can do.
>
> Rolf
>
>>
>> Thanks
>> Liam
>> _______________________________________________
>> MonoTouch mailing list
>> [email protected]
>> http://lists.ximian.com/mailman/listinfo/monotouch
>
>
>
> _______________________________________________
> MonoTouch mailing list
> [email protected]
> http://lists.ximian.com/mailman/listinfo/monotouch
>
--
Nic Wise
t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/
mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
Earnest: Self-employed? Track your business expenses and income.
http://earnestapp.com
Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
