Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Even with the latest iOS6’s identifierForVendor, what I found is when user deleted the app and the value will get reset.
Unlike the traditional OpenUDID pasteboards’ approach, it keep in the pasteboards and can re-use them.
I can’t see if Apple is going to ban the pasteboards, so should we keep using OpenUDID in the pasteboards mode?
(Also pasteboards is being widely supported)
Two parts to my answers:
identifierForVendor is really not a good equivalent for UDID or OpenUDID. You should look into the new Framework called AdSupport (formerly known as identifierForAdvertising). There is a unique identifier there that basically fulfills the unique identifier + preserved + cross apps, with two caveats: A/ the user may “opt-out” from the preferences by toggling a flag (it’s actually a soft flag) B/ the user may reset the identifier in the settings…
OpenUDID will be updated this week or next with iOS 6 compliant code.
All in all, OpenUDID is great for the transition between iOS 5 and iOS 6. Overtime, iOS 6 native APIs will be enough to cover your needs.