UIRequiredDeviceCapabilities~ipod, etc. Build.Settings

TheRealTonyK · January 24, 2013, 4:31pm

The docs here:
http://developer.coronalabs.com/content/configuring-projects

state that this should work:

settings =   
{  
 orientation =   
 {  
 default = "landscapeRight",  
 content = "landscapeRight",  
 supported =  
 {  
 "landscapeLeft", "landscapeRight", "portrait"  
 },  
 },  
 iphone =  
 {  
 plist =  
 {  
 UIInterfaceOrientation = "UIInterfaceOrientationLandscapeLeft",  
   
 UISupportedInterfaceOrientations =  
 {  
 "UIInterfaceOrientationLandscapeLeft",  
 "UIInterfaceOrientationLandscapeRight",  
 "UIInterfaceOrientationPortrait"  
 },   
  
 UIApplicationExistsOnSuspend = false,  
 UIStatusBarHidden = true,  
 UIFileSharingEnabled = false,  
 UIPrerenderedIcon = true,  
 CFBundleDisplayName = "Game Name",  
 },  
 },  
}  
  
settings.iphone.plist["UIRequiredDeviceCapabilities~ipod"] = "front-facing-camera"  
settings.iphone.plist["UIRequiredDeviceCapabilities~iphone"] = "front-facing-camera"

Yet I can still install and launch on an iPod 3rd Gen without a front-facing-camera.

Could really use some build.settings help here. Thanks! [import]uid: 21331 topic_id: 35291 reply_id: 335291[/import]

TheRealTonyK · January 25, 2013, 4:52pm

When attempting to upload any device specific UIRequiredDeviceCapabilities, the application loader process will reject stating that device specific identifiers cannot be used with this key.

How could I support iPhone 4+, iPod 4th Gen+, and all iPad models with build.settings? [import]uid: 21331 topic_id: 35291 reply_id: 140413[/import]

TheRealTonyK · January 28, 2013, 7:59pm

Anyone have experience with making these settings in the build.settings? [import]uid: 21331 topic_id: 35291 reply_id: 140711[/import]

TheRealTonyK · January 25, 2013, 4:52pm

When attempting to upload any device specific UIRequiredDeviceCapabilities, the application loader process will reject stating that device specific identifiers cannot be used with this key.

How could I support iPhone 4+, iPod 4th Gen+, and all iPad models with build.settings? [import]uid: 21331 topic_id: 35291 reply_id: 140413[/import]

TheRealTonyK · January 28, 2013, 7:59pm

Anyone have experience with making these settings in the build.settings? [import]uid: 21331 topic_id: 35291 reply_id: 140711[/import]

lano78 · February 14, 2013, 3:51am

I just go an app rejected that I submitted before x-mas, apple said the app looked malformed on iPads. I looked at my code and I clearly ruled out any possibility to install on iPads. I had in my build.settings added a UIRequiredDeviceCapabilities = “camera-flash” and tested to install on my ipad but it couldn’t.

One other thing is that the app was an exact copy codewise of another app I had approved a while before but another look.

The corona docs say… (this is what I had in my code)

UIRequiredDeviceCapabilities = "what ever you want to check for",

But I see devs using a table

UIRequiredDeviceCapabilities = {"what ever you want to check for", "what ever else you want to check for" },

What is right?

Apple works in strange ways… [import]uid: 13560 topic_id: 35291 reply_id: 142736[/import]

ingemar · February 14, 2013, 5:45am

UIRequiredDeviceCapabilities is an array or dictionary, so your second example with curly brackets would be necessary, even if you only specify one key.

You specify an array to *require* a feature that’s necessary:

iphone =   
{  
 plist =   
 {  
 UIRequiredDeviceCapabilities = {"front-facing-camera", "accelerometer"}  
 }  
}

If you have a reason to make sure that a feature *isn’t* available on the device you’ll need to use a dictionary instead with true/false values, like this:
(The example below requires an accelerometer, but *shouldn’t* have a front camera)

iphone = { plist = { UIRequiredDeviceCapabilities = { ["front-facing-camera"] = false, ["accelerometer"] = true} } } [import]uid: 70847 topic_id: 35291 reply_id: 142743[/import]

lano78 · February 14, 2013, 3:51am

I just go an app rejected that I submitted before x-mas, apple said the app looked malformed on iPads. I looked at my code and I clearly ruled out any possibility to install on iPads. I had in my build.settings added a UIRequiredDeviceCapabilities = “camera-flash” and tested to install on my ipad but it couldn’t.

One other thing is that the app was an exact copy codewise of another app I had approved a while before but another look.

The corona docs say… (this is what I had in my code)

UIRequiredDeviceCapabilities = "what ever you want to check for",

But I see devs using a table

UIRequiredDeviceCapabilities = {"what ever you want to check for", "what ever else you want to check for" },

What is right?

Apple works in strange ways… [import]uid: 13560 topic_id: 35291 reply_id: 142736[/import]

ingemar · February 14, 2013, 5:45am

UIRequiredDeviceCapabilities is an array or dictionary, so your second example with curly brackets would be necessary, even if you only specify one key.

You specify an array to *require* a feature that’s necessary:

iphone =   
{  
 plist =   
 {  
 UIRequiredDeviceCapabilities = {"front-facing-camera", "accelerometer"}  
 }  
}

If you have a reason to make sure that a feature *isn’t* available on the device you’ll need to use a dictionary instead with true/false values, like this:
(The example below requires an accelerometer, but *shouldn’t* have a front camera)

iphone = { plist = { UIRequiredDeviceCapabilities = { ["front-facing-camera"] = false, ["accelerometer"] = true} } } [import]uid: 70847 topic_id: 35291 reply_id: 142743[/import]

lano78 · February 14, 2013, 11:51am

I just go an app rejected that I submitted before x-mas, apple said the app looked malformed on iPads. I looked at my code and I clearly ruled out any possibility to install on iPads. I had in my build.settings added a UIRequiredDeviceCapabilities = “camera-flash” and tested to install on my ipad but it couldn’t.

One other thing is that the app was an exact copy codewise of another app I had approved a while before but another look.

The corona docs say… (this is what I had in my code)

UIRequiredDeviceCapabilities = "what ever you want to check for",

But I see devs using a table

UIRequiredDeviceCapabilities = {"what ever you want to check for", "what ever else you want to check for" },

What is right?

Apple works in strange ways… [import]uid: 13560 topic_id: 35291 reply_id: 142736[/import]

ingemar · February 14, 2013, 1:45pm

UIRequiredDeviceCapabilities is an array or dictionary, so your second example with curly brackets would be necessary, even if you only specify one key.

You specify an array to *require* a feature that’s necessary:

iphone =   
{  
 plist =   
 {  
 UIRequiredDeviceCapabilities = {"front-facing-camera", "accelerometer"}  
 }  
}

If you have a reason to make sure that a feature *isn’t* available on the device you’ll need to use a dictionary instead with true/false values, like this:
(The example below requires an accelerometer, but *shouldn’t* have a front camera)

iphone = { plist = { UIRequiredDeviceCapabilities = { ["front-facing-camera"] = false, ["accelerometer"] = true} } } [import]uid: 70847 topic_id: 35291 reply_id: 142743[/import]

lano78 · February 14, 2013, 11:51am

I just go an app rejected that I submitted before x-mas, apple said the app looked malformed on iPads. I looked at my code and I clearly ruled out any possibility to install on iPads. I had in my build.settings added a UIRequiredDeviceCapabilities = “camera-flash” and tested to install on my ipad but it couldn’t.

One other thing is that the app was an exact copy codewise of another app I had approved a while before but another look.

The corona docs say… (this is what I had in my code)

UIRequiredDeviceCapabilities = "what ever you want to check for",

But I see devs using a table

UIRequiredDeviceCapabilities = {"what ever you want to check for", "what ever else you want to check for" },

What is right?

Apple works in strange ways… [import]uid: 13560 topic_id: 35291 reply_id: 142736[/import]

ingemar · February 14, 2013, 1:45pm

UIRequiredDeviceCapabilities is an array or dictionary, so your second example with curly brackets would be necessary, even if you only specify one key.

You specify an array to *require* a feature that’s necessary:

iphone =   
{  
 plist =   
 {  
 UIRequiredDeviceCapabilities = {"front-facing-camera", "accelerometer"}  
 }  
}

If you have a reason to make sure that a feature *isn’t* available on the device you’ll need to use a dictionary instead with true/false values, like this:
(The example below requires an accelerometer, but *shouldn’t* have a front camera)

iphone = { plist = { UIRequiredDeviceCapabilities = { ["front-facing-camera"] = false, ["accelerometer"] = true} } } [import]uid: 70847 topic_id: 35291 reply_id: 142743[/import]