Does the “build active architecture only” box need to be unchecked while making a distribution build? I made a distribution build and submitted it with that box checked and am wondering if I need to reject it and uncheck it…
depends on the active architecture.
if you make it armv7 only, you can only distribute to os4 / os 3.2, previous OS require that you build for armv6 too.
and even with os4 it requires that you specify the armv7 requirement in the plist I think
but you will generally see it right away if it is incorrect. after upload the status will change to invalid an alike if its not fine
Well it’s been about 2 days now and they haven’t rejected it yet. When I make a build with it unchecked my build size increases by about 5 megabytes. Sounds like I should have had it unchecked. Has anyone successfully had an app approved with it checked?
if something on this level is wrong it will be autorected by the system.
if it wasn’t, don’t worry 
So if it looks like my distribution build was built for armv6 arch only. Will that be okay?
you will likely find that out on day 7 to 10 when they review it.
that you cut the ipad is no problem, but you killed out 3GS and iphone4 too which is in your anti-interest 
you can just recompile and reupload it, or at least that worked before the uploader enforcement was there, just try it
Well the armv6 version runs fast on both the iPhone 4 and the 3g (i tested on both), so I’m just going to keep it the armv6-only build up. So it looks like if someone wants a smaller iPhone-only build, build for armv6 only (if the optimizations of armv7 aren’t needed). Although for iPad armv7 is needed I see.
Edit: What’s interesting is that there’s no armv6 option in the info screen. There’s only Standard(armv6 and armv7) and Optimized (armv7) when using sdk 4.0. BUT if “build for active arch” box is checked and active arch is armv6 then it builds it only for armv6. It’s almost like checking that box is building armv6(only) in a behind doors way or something, because why wouldn’t armv6 be an option at the info screen in the first place.
I dont understand why building for Arm6 only will nuke the iPad support.
Games which were compiled long before iPad was around all seem to work fine on an iPad so why all of a sudden would they just stop working if we compile them for Arm6 only using the new SDK? If you dont build for active architecture only then the build size will BLOOOAT enourmously (almost doubling in size) and many games will no longer be under the 20 meg OTA download limit when they were before (and they worked fine on iPad as well before)
they will run fine, if you set the project to be iphone only.
but if you set it to ipad, it MUST contain ARM7 as the ipad natively is ARMV7.
by not making that available its clear to the automatisms that your project can not be an ipad targeted one and thus not run in native ipad mode
Can someone with an iPad clarify this: armv6 wont work if you do an iPad only (3.2) app. But I thought it would “run” if you targeted 4.0?!?
3GS and 4G are fine with armv6 only. But to clarify the only reason to do this is to reduce binary size… if you wont make 20MB limit then there’s no need.
“they will run fine, if you set the project to be iphone only”
Ahh excellent. Thats all I was wondering. We are not trying to make this an iPad + iPhone universal app. We are just trying to update an existing iPhone app that has a fairly large / happy iPad playing community (its a 2d game with fairly low-fi graphics so I guess they don’t care about the lack of resolution when the game is playing in up-scale iPhone compatibility mode on their iPad).
If we were to make an iPad specific version we would have to do some work on the menu’s etc where we have used GUITexture’s etc so we would likely just release an iPad specific version so as not to bloat the iPhone version by chasing the all-in-one universal outcome.