Hi Chris, I expect that we'll be releasing a 4.1 "soon". We noticed yesterday that there is a regression and we are working hard to track it down and resolve it before pushing a new release out to the beta channel (4.1.x will be beta releases allowing everyone to test bug fixes as well as test new features we've been working on such as improved debugging, performance improvements, smaller compiled app sizes, etc).
Hopefully we'll release 4.1.0 next week but that depends on how quickly we're able to find this regression and resolve it, so don't hold me to that timeline! ;-) Jeff On Fri, Aug 12, 2011 at 4:09 AM, Chris van Wyk <[email protected]> wrote: > Hi Jeff, > > What time frame are we looking at in terms of release for 4.1 and is there > a tentative feature list for this release? > > Thanks > Chris > > > From: Jeff Stedfast <[email protected]> > Date: Thu, 11 Aug 2011 19:46:02 -0400 > To: Dean Cleaver <[email protected]> > Cc: "Forums, MonoTouch ([email protected])" < > [email protected]> > > Subject: Re: [MonoTouch] Exception assistance... > > Hi Dean, > > Finally got around to looking at this today. It looks like the null-check > for NSString's .ctor (string value) didn't make it into 4.0.4.1 :-( > > It *will* be in MonoTouch 4.1, however. That said, the only thing that will > change is that you'll get a ArgumentNullException thrown when passing null > to NSUserDefaults.SetString(). From looking at the trace you provided in the > original email, it looks like it would have to be the first argument to > SetString() that is null if that is of any help to you. > > Hope that helps, > > Jeff > > On Wed, Aug 10, 2011 at 6:39 PM, Jeff Stedfast <[email protected]> wrote: > >> Thanks Dean, I'll look into this tomorrow. >> >> Jeff >> On Aug 10, 2011 5:59 PM, "Dean Cleaver" < >> [email protected]> wrote: >> > Ummm - was released last Friday, and was the latest at that time. >> > >> > From: Jeff Stedfast [mailto:[email protected]] >> > Sent: Wednesday, August 10, 2011 4:55 PM >> > To: Dean Cleaver >> > Cc: Forums, MonoTouch ([email protected]) >> > Subject: Re: [MonoTouch] Exception assistance... >> > >> > >> > Yep, that's what it looks like. We should null-protect that method. >> Which version of MT is this? >> > >> > Jeff >> > On Aug 10, 2011 5:51 PM, "Dean Cleaver" < >> [email protected]<mailto: >> [email protected]>> wrote: >> >> Guys, >> >> >> >> Would I be right if I guess that this is an exception where null was >> passed into the SetString function? >> >> >> >> MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown. >> Name: NSInvalidArgumentException Reason: *** -[NSPlaceholderString >> initWithUTF8String:]: NULL cString >> >> at MonoTouch.Foundation.NSString..ctor (System.String str) [0x00000] in >> :0 >> >> at MonoTouch.Foundation.NSUserDefaults.SetString (System.String value, >> System.String defaultName) [0x00000] in :0 >> >> at KleverLogic.FlashValet.iPhone.Valet.AppDelegate.SaveSettings () >> [0x0004b] in >> /xsl-home/kleverlogic/FlashValet/Mobile/iPhone/Valet/Main.cs:1086 >> >> >> >> Cheers, >> >> Dino >> > > _______________________________________________ MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > -- Rate my reply: http://www.nicereply.com/xamarin/jstedfast
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
