Xcode: MinimumOSVersion functionality - menu?

Solar2D Daily Builds and Public Releases
#1

We have run into an issue whereby our specified “MinimumOSVersion” that is placed in our build.settings file is NOT being reflected in our Binary Details once our release app candidate is uploaded to Apple’s Store.

Chatter out on the outside forums state that Apple discourages people from directly indicating within the plist what the MinimumOSVersion is, yet our Corona forums indicate that’s how we’re to deal with this issue. Xcode provides a menu’ing system for this process and then they handle it behind the scenes (I’m assuming).

If we develop an App that we don’t want to run on anything slower than 3GS, we are to indicate a Minimum OS Requirements: 4.3.0
However, right now we’re not being successful in trying to get our Binary Details to reflect that. Which means we’re losing valuable time within the queue; and worse - if the app is approved we run the risk of low star ratings impacting our products marketability when people with 3G devices start meeting with crashes.

Xcode offers the ability for programmers to indicate this value and it seems that Corona needs to make this a priority in my eyes. I am surprised there isn’t more chatter within our forums regarding this very issue. I have heard people having success indicating a MinimumOSVersion=“3.2” but I have seen NO feedback about anyone being successful around MinimumOSVersion=“4.3.0”
http://developer.anscamobile.com/forum/2011/07/06/prevent-old-iphone-and-ipod-users-downloading-app
Beebe talks about this here, but I don’t see much confirmation of it working.

Ansca, any recommendations or future solutions to this issue? Anxiously awaiting feedback - thank you very much. [import]uid: 74844 topic_id: 16984 reply_id: 316984[/import]

#2

Did you try :

MinimumOSVersion=“4.3”

?? [import]uid: 84637 topic_id: 16984 reply_id: 64356[/import]

#3

@Danny: Funny you should say that; the three responses I got on the Apple forums actually were similar. Originally, the Ansca tech support staff thought it was a misplaced bracket ‘}’ but when we attempted their recommended change, the output “appeared” identical with the info.plist…so we have been skeptical and thus have not rejected our submission and jumped to the end of the queue. But now I’m sort of wondering about this “4.3” vs. “4.3.0” a little bit more. I could make both the bracket change AND the “x.y” change and see what the info.plist does.

Here’s the rub: our submitted zip with the info.plist file has in there 4.3 so we think it’s fine… well, except that we cannot explain why the BINARY DETAILS reflects 3.1 right now. It’s horrible not knowing what the problem is for sure.

EDIT: as a sidenote, it was Beebe that recommended the “4.3.0” [import]uid: 74844 topic_id: 16984 reply_id: 64361[/import]

#4

4.3 seems more likely to work as I think it only accepts two numbers not 3 decimal places anyway.

As for the info in itunes connect, perhaps it hasn’t refreshed as yet, I’m not sure on that however [import]uid: 84637 topic_id: 16984 reply_id: 64364[/import]

#5

@Danny: I just retried the build with the 4.3 and info.plist appears to be NO DIFFERENT now. iTunesConnect has had the submission since Tuesday so that’s almost 4 full days and I would think that number is parsed immediately upon submission…and is not a manual update or anything. But this being our first submission, I have no experience in this regard. [import]uid: 74844 topic_id: 16984 reply_id: 64366[/import]

#6

I will pass this onto the team. Maybe minimum os version is hardcoded at 3.2, im not sure.

Leave it with me [import]uid: 84637 topic_id: 16984 reply_id: 64367[/import]

#7

@Danny: to be clear, our build.settings now looks like this with the corrected bracket placement per Tom in Support:

iphone =  
 {  
 plist=  
 {  
 MinimumOSVersion="4.3.0",  
 UIStatusBarHidden=true,  
 UIApplicationExitsOnSuspend = false,  
 CFBundleIconFile = "Icon.png",  
 CFBundleIconFiles = {  
 "iTunesArtwork.png",  
 "Icon-72.png",  
 "Icon@2x.png",   
 "Icon.png",   
 },  
 CFBundleIdentifier = "com.nonomonkey.www",  
 CFBundleDisplayName = "NoNo Monkey",  
  
 },  
 }

(and thank you for the effort!) [import]uid: 74844 topic_id: 16984 reply_id: 64369[/import]

#8

Assuming your Info.plist has correctly replaced the MinimumOSVersion with your specified version, I don’t think anything is wrong. “BINARY DETAILS” implies that is reading the executable binary, not the Info.plist. Corona executable binaries (currently) are built to support 3.1 no matter what. The Info.plist is an opportunity to further constrain the OS version.

This mechanism is partly how we supported iPad only in the 3.2 era. Since iPad-only does not work on a 3.1 device, we change the MinimumOSVersion to 3.2 for these builds.

Assuming Apple didn’t break the iTunes/App Store, they should be respecting the Info.plist setting when users browse the store.
[import]uid: 7563 topic_id: 16984 reply_id: 64373[/import]

#9

Thank you ewing, that’s a big relief and I’m glad we didn’t yank the submission and re-enter the queue.

EDIT: I wanted to update this thread and state that when we submitted the LITE version of our game which had the fixed bracket configuration in our build.settings, the BINARY DETAILS for our LITE version did in fact reflect correctly the desired Minimum OS Requirements: 4.3.0
[import]uid: 74844 topic_id: 16984 reply_id: 64399[/import]