Hi Rolf, I have a Bindings project that exports an Objective-C library written by one of my suppliers. I don't use it myself directly, but I presume they do?
It just happened when my QA guy was here testing. Not something I've been able to reproduce though. Dino From: Rolf Bjarne Kvinge [mailto:[email protected]] Sent: Friday, October 19, 2012 17:33 To: Dean Cleaver Cc: [email protected] Subject: Re: [MonoTouch] Can anyone tell me what happened here? Hi, On Sat, Oct 20, 2012 at 12:28 AM, Dean Cleaver <[email protected]<mailto:[email protected]>> wrote: So if I don't actually use the NSNotificationCenter then this is probably a fault in the external accessory library? Do you use external accessory yourself? Or through some sort of third-party library? The ExternalAccessory framework is part of iOS, so I would not look for a bug there first. Is this something you can reproduce or did it just happen for one of your users? Rolf Dino From: Rolf Bjarne Kvinge [mailto:[email protected]<mailto:[email protected]>] Sent: Friday, October 19, 2012 17:21 To: Dean Cleaver Cc: [email protected]<mailto:[email protected]> Subject: Re: [MonoTouch] Can anyone tell me what happened here? It crashed inside ExternalAccessory. That's pretty much all I can say for certain. Speculating a bit my guess would be that the object listening for notifications from NSNotificationCenter was freed (have in mind that NSNotificationCenter does not ref any objects/notifications, you have to make sure those aren't freed yourself). Rolf
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
