No you should not but meanwhile I always do. I claim that MT has a bug deep down hidden somewhere that causes the problems you experience. I can see the same in my code and I have never found a reasonable explanation for them. I get them on the device only. For each and every controller - totally random. Sometimes not a single one for days then multiple errors. I have never seen the issue on the Simulator and that makes me think it is a well hidden bug because on the Sim GC gets called more often and hence the probability should be higher to encounter the crashes there, but the opposite is the case. Implementing the ctor has not caused any side effects for me. I added logging if the ctor is hit and if the app crashes I can see if a method was called in the uninitialized controller. Has not happened so far. It seems the object is just created by some ObjC code but nothing is done with it. Note that if you are using storyboards, you must add the ctor.
Grüße, René Am 29.06.2012 um 19:57 schrieb Dean Cleaver <[email protected]>: > I thought we weren’t supposed to create them in our code, but if I don’t I > get this: > > System.Exception: Selector invoked from objective-c on a managed object > (0x9795310) that has been GC'ed ---> System.MissingMethodException: No > constructor found for > KleverLogic.FlashValet.iPhone.Valet.Common.NumberViewController::.ctor(System.IntPtr) > > Are we supposed to include them or not? > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
