"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

UDID uniqueIdentifier

By dmost on Wed, 06/20/2012 - 17:10
Many iOS bloggers are all a twitter about Apple rejecting applications that access the user's UDID (aka call [UIDevice uniqueIdentifier]). [URL=http://techcrunch.com/2012/03/24/apple-udids/]UDID Apple Rejections[/URL] Setting a symbolic breakpoint; we see the QCAR library is grabbing the UDID within QCAR::init() and worry this puts our app at a high risk for rejection. We have language in our license agreement and privacy policy that covers the collection of data; as as per Qualcomm's publishing notes: "You must inform end-users of your application that certain types of anonymous usage data is collected by the Vuforia SDK and sent back to Qualcomm servers". However, few users read that (based on our tracking stats!) so we are still fearful of Apple's ban hammer. I'm hoping an SDK update is on the way to address this issue. Any re-assuring words? We have an update heading into review imminently. Thanks! --Dave

At this time, we are not aware of any Vuforia apps being rejected. Please be sure to adhere to sections 7 & 8 of the Vuforia license agreement. - Kim

Our Vuforia app has ben rejected for using the call to uniqueIdentifier. UDID has been deprecated for ages, why waiting the last minute to remove it? Is there an update to fix this?

Is there an update to fix this?

Yes there is.  

 

The sticky here :

https://developer.vuforia.com/forum/ios/udid-information-and-clarification

clearly stated we were working on an update which was launched recently.

 

Thank you. I wish I had received this email one week ago to avoid this rejection, but I've checked again in the inbox, in the trash, in the spam box, and nothing has been received from Vuforia. Anyway, that's a good thing the library is available with the fix.

We were also rejected just this weekend.  The libQCAR.a file is the culprit.  When will this be fixed?

It already is.

If you read the thread below you'll realise 1) the latest build is already out  2) the sticky was updated to reflect this and 3) an email blast went out, possibly later than anticipated.

So download the latest SDK, build and submit.

N