Log in or register to post comments

Info.plist / Apple review process

September 18, 2011 - 5:53am #1

Hi,

Let's say once QCAR iOS is out of beta I will publish my application on Apple Appstore.

Could you tell me what extra values I should put into Info.plist file in order to meet requirements of Apple's review process? So far I figured that I'll need these (under UIRequiredDeviceCapabilities):
* video-camera (obviously we need camera)
* opengles-2 (this limits to devices iPhone 3GS and up)

Anything else? wifi?

I think it would make sense to include this in QCAR iOS distribution (if it's possible), so no one forgets it before submission :)

Thanks,
Paulius
http://pixel-punch.com

Re: Info.plist / Apple review process

September 22, 2011 - 10:26am #7

What is the best way to incorporate other licenses present in the "Licenses" directory while distributing binary?

Re: Info.plist / Apple review process

September 20, 2011 - 1:20pm #6

The release is out as of today :) See the announcement: http://ar.qualcomm.at/node/2000898

- Kim

Re: Info.plist / Apple review process

September 20, 2011 - 7:12am #5

Any idea when that would be?

Eagerly waiting to launch an app :(

Re: Info.plist / Apple review process

September 20, 2011 - 4:09am #4
stridefrodo wrote:

Sorry if I missed something but do we need to wait till iOS SDK comes out of beta to submit the app?

Correct.

Do watch this space for news about release dates. :)

Re: Info.plist / Apple review process

September 19, 2011 - 1:23pm #3

Sorry if I missed something but do we need to wait till iOS SDK comes out of beta to submit the app?

Re: Info.plist / Apple review process

September 19, 2011 - 3:48am #2
Paulius wrote:

Let's say once QCAR iOS is out of beta I will publish my application on Apple Appstore.

Could you tell me what extra values I should put into Info.plist file in order to meet requirements of Apple's review process?

Hi Paulius, thanks for your idea.

Given that we're providing a library and have no control over the use and implementation around QCAR we'd never have the correct answer for everybody.

It's good practise for the developer to think through this themselves and decide what they need (for example we have some developers who don't require a camera as their app uses QCAR only as part of its purpose).

Maybe it would be a good item for 'things to consider' in our future documentation or in a forum sticky.

Log in or register to post comments