On Wed, Nov 14, 2012 at 4:11 PM, Brett Spurrier <[email protected]> wrote: > I agree in that I doubt it had to do with the update. The update did > however, completely remove the option of building for ARMv6, so when I set > it to ARMv7+ARMv7s, then that probably fixed whatever setting was failing > before (note I had it set to ARMv7 previously, but it appears that the build > didn't recognize that).
The update does not remove ARMv6 support. If you were seeing ARMv6 that's because you were building with a SDK earlier than 6.0. IOW if you use SDK 6.0 then you'll see ARMv7 and ARMv7s (ARMv6 will be hidden). For older SDK you'll see ARMv6 and ARMv7 (ARMv7s) will be hidden. This behavior is recent (6.x series) but not new to the 6.0.7 update (in fact the UI logic is inside MonoDevelop's addin, not MonoTouch). Sebastien > Thanks for you notes though...much appreciated. > > Cheers, > Brett > > > On Wed, Nov 14, 2012 at 4:05 PM, Sebastien Pouliot <[email protected]> > wrote: >> >> On Wed, Nov 14, 2012 at 3:57 PM, Brett Spurrier >> <[email protected]> wrote: >> > Ugh...Upgraded MonoTouch to 6.0.7 did the trick. >> >> I'm glad if it works now but I seriously doubt it has something to do >> with the 6.0.7 update. >> >> >>>> Invalid Launch Image - Your app contains a launch image with a size >> >>>> modifier that is only supported for apps built with the iOS 6.0 SDK >> >>>> or >> >>>> later. >> >> That message indicate that the 6.0 SDK was not used to build the >> application. Could your MonoDevelop SDK location be pointing at an >> older Xcode release ? >> >> Many people have reported that Apple does not allow using the new >> iPhone5-sized default image if you're not linking with the 6.0 (or >> later) SDK version. >> >> Regards, >> Sebastien > > _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
