2.0: Product runs on iOS 2.0 and later.
2.1: Product runs on iOS 2.1 and later.
2.2: Product runs on iOS 2.2 and later.
2.2.1: Product runs on iOS 2.2.1 and later.
3.0: Product runs on iOS 3.0 and later.
3.1: Product runs on iOS 3.1 and later.
3.1.2: Product runs on iOS 3.1.2 and later.
3.1.3: Product runs on iOS 3.1.3 and later.
3.2: Product runs on iOS 3.2 and later.
4.0: Product runs on iOS 4.0 and later.
Bump, has anyone actually got this working? Am I supposed to see ‘Minimum OS Requirements’ in iTunes Connect as ‘4.0’ if its working (so far I can’t get it to change from 3.1)… [import]uid: 9428 topic_id: 7878 reply_id: 28471[/import]
If you check in iTunes you’ll see that it indeed lists the requirement as 3.2.0 and looking at the binary details in iTunes connect also lists it. I built with Corona.268 . While I cannot vouch for “4.0” it definitely works for 3.2.0 [import]uid: 12405 topic_id: 7878 reply_id: 29095[/import]
So maybe it’s MinimumOSVersion, and not MinimumOSRequirement.
Not sure I’m keen to send my app back to the end of the review queue yet again to adjust though… [import]uid: 9428 topic_id: 7878 reply_id: 29129[/import]
Not sure I’m keen to send my app back to the end of the review queue yet again to adjust though…
If your app really does require iOS 4 then you should probably fix this. There’s a reason Carlos titled this thread as he did. [import]uid: 12108 topic_id: 7878 reply_id: 29375[/import]
But how do I know whether I need that or not – outside of testing on all versions of the OS? Is there a list of things in Corona based on OS version?
Would be nice if the Corona Simulator would flag the minimum OS needed when it does a build, that seems like something a program could keep track of better than a people.
Jay
[import]uid: 9440 topic_id: 7878 reply_id: 29378[/import]
I based it on whether or not the older iOS devices can run it smoothly. I tried Rico: MFH on my kids’ iPhone 2G and it was choking all over the place. Since the iPhone 2G stopped at 3.1.3, I set my MinimumOSVersion to 3.2 to accomodate the first iPad and all the devices going forward. We all know that the iPhone 3G sorta got the shaft by being upgradable to 4.1, and most people were complaining about it’s sluggishness anyway, so I’d think they’d probably aim to get rid of that device at the first chance they get. [import]uid: 6084 topic_id: 7878 reply_id: 29379[/import]
Well, I used a recent daily build for GameCenter via OpenFeint, so I’ve re-submitted my game with minimum iOS 4 (which I guess is pretty important so the app doesn’t crash on launch :S ).
Back to the end of the queue I go!! [import]uid: 9428 topic_id: 7878 reply_id: 29386[/import]
Would be nice if the Corona Simulator would flag the minimum OS needed when it does a build, that seems like something a program could keep track of better than a people.
That would be a really handy feature. *hint hint carlos*
In the meantime, the only Corona feature I’ve seen that requires iOS 3.2 is custom fonts. I only upgraded my phone to iOS 4 recently and before then I’d tested Corona apps with every single feature.
Note though that the latest daily build apparently only works on iOS 4, which makes sense I guess since the latest daily build adds GameCenter support and GC is only on iOS 4: http://developer.anscamobile.com/forum/2011/03/24/latest-daily-builds-ios-3x [import]uid: 12108 topic_id: 7878 reply_id: 29381[/import]
I do not believe your game will crash if you use GameCenter on iOS 3.1 and above. GameCenter will simply be disabled. Someone should correct me though if that’s not the case!
Another thing I noticed: I forgot to include the “minimum OS” value in my plist and while Apple was reviewing it, they set it to 3.1 for me. So maybe they are being more careful about that now? [import]uid: 36054 topic_id: 7878 reply_id: 40730[/import]
Thanks sooooooooooo muuuuuch for the headsup!! I just rejected my binary and uploaded the new version, just lost one day in the cue which is not bad compared to what could have happened otherwise.
cheers all!
adrian
[import]uid: 12407 topic_id: 7878 reply_id: 42318[/import]
To be clear, we added the line of code to our build.settings:
plist=
{
MinimumOSVersion="4.3.0",
But within the Binary Details upon upload, the Minimum OS Requirements reflects: 3.1 still…? Is there something else that must be specified within plist? Or within iTunesConnect to ensure the Minimum OS Requirements is consistent with what we specify within the plist (like above)? We’ll have to reject this binary and resubmit, as soon as we know what the fix is. Thanks for any immediate response!!! Appreciate it… [import]uid: 74844 topic_id: 7878 reply_id: 63660[/import]
@Ben: does the “Binary Details” within iTunesConnect then dynamically reflect the settings from plist? Or does that get corrected once our app is reviewed and then Apple updates this information? It seems like this should be correctly reflected dynamically…?
EDIT: Sorry Ben, missed your last sentence… so you’re saying that Binary Details SHOULD then accurately reflect what we specified within our plist. Very strange. So why isn’t it seeing it I wonder?
Correct, it is dynamic. I checked it on the one I posted here as it is a new app and is still waiting for review, so it has not been manipulated by Apple.
Does not make sense. Perhaps a rebuild and try uploading again if you have not already. [import]uid: 28534 topic_id: 7878 reply_id: 63677[/import]