If you don’t know, your app will not be able to get a UUID anymore in iOS 5.
I am fixing this bug, but I see one thing: if I compile my app for iOS 4, and install the app in iOS 5, the unique identifier still work. My old programs have no problem in iOS 5.
So, can I say this to my boss with 100% certainty?
If I compile for iOS 4, my program will have the unique identifier for
all iOS 5 devices! It will only fail when I compile my program for iOS
5 or Apple stops supporting iOS 4 (and this will take a long time)!
I think the answer you want has nothing to do with iOS 5. I would tell your boss:
“As of iOS 4, UDIDs have not been deprecated. Apple has a long, strong history of deprecating functionality for at least a version before yanking the functionality completely. If Apple sticks to this established track record, there’s no reason to believe that UDID support will be anything but deprecated in iOS 5 and would not be in danger of removal until iOS 6.”
Also, for what it’s worth, if UDID support were to vanish, most of the same functionality could be simulated by generating a UUID the first time your app is launched and stashing it to
NSUserDefaultsor disk for later lookup.[Update: Though this turned out to be bad advice. Here we are at iOS 5.1 and apps that make use of UDID are already being rejected. Guess Apple’s extra eager to crack down on this.]