To be blunt, we can't help without having code to look through. MonoTouch doesn't just add method calls, and throw exceptions on its own.
My guess is that your problem is probably an incorrect use of an API or object somewhere. iOS application development is a lot more accessible now, thanks to MT, but if you don't do the basics, just as with ObjC or PhoneGap (et. al.) your foundations will be shaky. Share the code, or at least somewhere we can reproduce the problem, and we can help you diagnose the problem. Regards, James On 13/10/2012, at 11:23 AM, Dean Cleaver <[email protected]> wrote: > Anyone able to help before I ditch MonoTouch and try something that works? We > are seriously in a position where we cannot release code because of this > problem, and the CEO is discussing ditching MonoTouch completely because we > can’t rely on it to work. > > Dino > > From: Dean Cleaver > Sent: Friday, October 12, 2012 17:16 > To: Dean Cleaver; [email protected] > Subject: RE: Any idea what this could be? > > It’s now seemingly not Linea – just random: > > MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown. Name: > NSInvalidArgumentException Reason: -[OS_dispatch_semaphore > UIApplicationWillEnterForeground:]: unrecognized selector sent to instance > 0x81b27e0 > at (wrapper managed-to-native) > MonoTouch.UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr) > at MonoTouch.UIKit.UIApplication.Main (System.String[] args, System.String > principalClassName, System.String delegateClassName) [0x0004c] in > /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:38 > at KleverLogic.FlashValet.iPhone.Valet.Application.Main (System.String[] > args) [0x00048] in > /xsl-home/kleverlogic/FlashValet/Mobile/iPhone/Valet/Main.cs:40 > > And here’s my WillEnterForeground: > > public override void WillEnterForeground(UIApplication application) > { > try > { > > //ThreadPool.QueueUserWorkItem(this.EnterForeground); > } > catch (Exception ex) > { > Application.SendError(ex); > } > } > > Yeah – basically empty, yet it still crashes in the > UIApplicationWillEnterForeground – any ideas? > > Dino > > From: [email protected] > [mailto:[email protected]] On Behalf Of Dean Cleaver > Sent: Thursday, October 11, 2012 15:00 > To: [email protected] > Subject: [MonoTouch] Any idea what this could be? > > I got this error report recently: > > MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown. Name: > NSInvalidArgumentException Reason: -[Linea UIApplicationDidEnterBackground:]: > unrecognized selector sent to instance 0x21a2a80 > at MonoTouch.UIKit.UIApplication.Main (System.String[] args, System.String > principalClassName, System.String delegateClassName) [0x0004c] in > /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:38 > at KleverLogic.FlashValet.iPhone.Valet.Application.Main (System.String[] > args) [0x00027] in > /xsl-home/kleverlogic/FlashValet/Mobile/iPhone/Valet/Main.cs:40 > > I’m intrigued by the “Reason: -[Linea UIApplicationDidEnterBackground:]” > because I make no calls to the linea in this, so wondered if there was even > anything I could do? > > Dino
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
