Prevent Old iPhone and iPod users from Downloading App

Solar2D General Questions/Discussion
#1

Hello,

I would like to know how I can deny first and second generation of iOS mobile iphones and ipods from downloading my app. Is it an option in itunes connect or is it explicit in the binary. If it is infact explicit, then where in the binary does it need to be set (ie build.settigns…). Note that verision ‘1’ appears as Version 3 on my iphone, if that makes any sense.

Thanks for reading my post! [import]uid: 58749 topic_id: 12066 reply_id: 312066[/import]

#2

We use these settings in build.settings:

settings = { iphone = { plist = { UIRequiredDeviceCapabilities = { "armv7", "opengles-2", }, }, }, } [import]uid: 9058 topic_id: 12066 reply_id: 44003[/import]

#3

Please excuse my lack of knowledge but what is “opengles-2”, thanks [import]uid: 58749 topic_id: 12066 reply_id: 44058[/import]

#4

OpenGL for Embedded Systems (OpenGL ES) is a subset of the OpenGL 3D graphics application programming interface (API) designed for embedded systems such as mobile phones, PDAs, and video game consoles. OpenGL ES is managed by the not-for-profit technology consortium, the Khronos Group, Inc.

by Wikipedia

http://en.wikipedia.org/wiki/OpenGL_ES#OpenGL_ES_2.0_2 [import]uid: 13454 topic_id: 12066 reply_id: 59923[/import]

#5

In the plist section, you could specify “MinimumOSVersion”, which won’t specifically exlude on a device-by-device basis, but you could instead exclude based on whether or not a device could run a certain version of iOS.

The logic behind this is that, if it’s powerful enough to run iOS #.# then it should be powerful enough to run my game.

Here’s the exact line:

settings = { iphone = { plist = { MinimumOSVersion="4.3.0", }, },}[/code]Here's a page that shows you which devices can run specific versions of iOS:http://en.wikipedia.org/wiki/List_of_iOS_devices#ModelsSo if you want to make sure 3GS is the oldest device you support, you need to set the MinimumOSVersion to at least "4.3.0".Hope that helps! [import]uid: 52430 topic_id: 12066 reply_id: 59940[/import]

#6

Thanks jonathan i was searching for that information, this help me. [import]uid: 13454 topic_id: 12066 reply_id: 59951[/import]

#7

Hi, I currently have a similar issue. I need to restrict downloads to my app if the idevice doesn’t have a camera. Currently my plist entry looks like this

UIRequiredDeviceCapabilities = “video-camera”,

However when I upload, the application loader gives an error, saying its an invalid entry? Did I do anything wrong? [import]uid: 34103 topic_id: 12066 reply_id: 59990[/import]

#8

nevermind, I got it fixed! [import]uid: 34103 topic_id: 12066 reply_id: 59992[/import]

#9

Would you mind telling how got that fixed?

Thanks, [import]uid: 89165 topic_id: 12066 reply_id: 59995[/import]

#10

@Jonathan: we did what you specified with the 4.3.0 setting in build.settings, but the Binary Details did NOT update to reflect this. We cannot figure out why to save our life… any thoughts?

EDIT: on another forum, this was posted: Thanks Martin, what you wrote is correct in general and I already verify it BUT it doesn’t solve the specific issue because Apple about the MinimumOSVersion states clearly: Do not specify this key yourself in the Info.plist file; it is a system-written key.

EDIT #2: Ansca support indicates the following in our case, so I share in case someone else makes this mistake:

This is wrong:

CFBundleIconFiles = {  
"iTunesArtwork.png",  
"Icon-72.png",  
"Icon@2x.png",  
"Icon.png",  
CFBundleIdentifier = "com.game.www", CFBundleDisplayName = "GameTitle", },

And should be this:

CFBundleIconFiles = {  
"iTunesArtwork.png",  
"Icon-72.png",  
"Icon@2x.png",  
"Icon.png",  
},  
  
CFBundleIdentifier = "com.game.www", CFBundleDisplayName = "GameTitle",

If you look closely we accidentaly included CFBundleIdentifier and CFBundleDisplayName within the bracket for CFBundleIconFiles. We were told by Ansca that this made the parser burp and thus resulted in our MinimumOSVersion not being written out. As of this writing, we’re still awaiting confirmation that this fixes our problem. We unfortunately were not given an “error” by the parser so it behaved like it was all fine.
[import]uid: 74844 topic_id: 12066 reply_id: 63684[/import]