Ah, so THATS what you ment.

Bother. I was hoping to put a try/catch around it, and then just...
ignore it (but not crash). Which I'm doing with an if statement at the
moment.

thanks :) Maybe i need to turn that off in TF.

On Fri, Mar 16, 2012 at 11:14, Rolf Bjarne Kvinge <[email protected]> wrote:
> Hi,
>
> On Fri, Mar 16, 2012 at 12:11 PM, Nic Wise <[email protected]> wrote:
>>
>> ... and after some debugging...with a drumroll but NO surprise, it
>> looks like the problem is.... ME.
>>
>> NullReferenceException in the ContinueWith section. Causes a segfault.
>> Basically:
>>
>> foo.Property = value;
>>
>> foo is null (it's a derivative from MT.D's Element). bang. (Property
>> does nothing except assignment)
>>
>> try/catch doesn't catch it tho. Which is ODD.
>
>
> That's expected if you're using TestFlight's crash handling. TestFlight
> detect the NullReferenceException as a crash and handles it accordingly,
> mono is never given a chance to process it.
>
> Rolf



-- 
Nic Wise
t.  +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/

Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
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
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

Reply via email to