views:

9579

answers:

9

For an iPhone app that submits images to a server I need somehow to tie all the images from a particular phone together. With every submit I'd like to send some unique phone id. Looked at

  [[UIDevice mainDevice] uniqueIdentifier]
and [[NSUserDefaults standardDefaults] stringForKey:@"SBFormattedPhoneNumber"]

but getting errors in the simulator.

Is there an Apple sanctioned way of doing this?

+1  A: 

Haven't done iphone work, but how about taking a hash of something unique to the phone ... oh, say the phone number?

Getting iphone number

Niniki
That frequently works but will return incorrect information in a significant number of cases. It gets a phone number, but it's not guaranteed to be the current phone's number, a valid phone number, or even a unique number.
Tom Harrington
how often does an iPod Touch have a phone number?
Graham Lee
+20  A: 

What errors are you getting? [[UIDevice currentDevice] uniqueIdentifier] (edited to fix API, thanks Martin!) is the officially recommended way of doing this.

Ben Gottlieb
*** +[UIDevice mainDevice]: unrecognized:however tried [UIDevice currentDevice] and it works in the sim
Martin Redmond
sorry, you're right.
Ben Gottlieb
+4  A: 

You can also use CFUUID to generate a UUID. Here's some code:

NSString *uuid = nil;
CFUUID theUUID = CFUUIDCreate(kCFAllocatorDefault);
if (theUUID) {
  uuid = NSMakeCollectable(CFUUIDCreateString(kCFAllocatorDefault, theUUID);
  CFRelease(theUUID);
}
smeger
Sounds cool. Will theUUID be the same on every invocation?
Martin Redmond
No, different every time, so usually you'd generate it on first launch and then save it to your preferences using NSUserDefaults.
smeger
The downside to this is that if the app is deleted and reinstalled or if the device is restored from backup, you'll lose the saved UUID and things won't be recognized as from the same device.
Jeff Kelley
I had to type theUUID as CFUUIDRef, not CFUUID.And don't forget to add CoreFoundation to your project, and import <CoreFoundation/CoreFoundation.h>
Glenn Barnett
+9  A: 

By far the easiest and most appropriate way to obtain a unique identifier is to use the mechanisms Apple explicitly provides for obtaining one - [[UIDevice currentDevice] uniqueIdentifier]. You can not guarantee that the phone number will be unique to the device or that the device will even have a phone number. Beyond that, doing so is a horrible idea as it is a definite invasion of the user's privacy. Even the uniqueidentifier should be hashed if you are going to store it in any way.

wisequark
+1 for calling out the privacy concerns. So many just ignore this aspect.
jmanning2k
What is a good way to store a HASHED value of a string?
Donna
+1  A: 

This is an interesting problem that I am also looking into solving. Here is a scenario that I would like to address.

What happens when you sell your phone to another person... that Device ID will then belong to somebody else, so even if the app is removed from the iPhone, it could be re-added and all that data would then be re-associated to a new user... this is bad.

Using the Phone number with the Device ID MD5 would be a great solution. Another we came up with is having a SQL Lite DB with some token Hashed with the Device ID. Then when the app is removed the DB is killed and all the data is disassociated. I think that might be too brittle.

Any other ideas?

Rob Ellis (PhoneGap/Nitobi)

Or the phone develops a problem and is replaced under warranty - same user, new phone. The generated UUID stored in NSUserDefaults solution would win here, since prefs are synced back.
jmanning2k
A: 

snippit:

NSString *phoneNumber = (NSString *) [[NSUserDefaults standardUserDefaults] objectForKey:@"SBFormattedPhoneNumber"]; // Will return null in simulator!
NSLog(@"Formatted phone number [%@]", phoneNumber);

I [recently] ran this code as-is on OS 2.2.1 [and OS 3.0].

It works as expected when run on the device, and returns my phone number with the full international dialing codes [ 1 in my case].

When run on the simulator, the value [returned] is a null string, so it only works on an actual iPhone device.

I did not test it on an iPod Touch.

...

Ran this code on a different device this week, and got a null value instead of the number.

On further research, it appears that the number returned by this code snippit is the number that is set up in iTunes for the device.

If you didn’t enter the iPhone’s number in iTunes at device activation, or perhaps (as in my case) if the default value wasn’t the iPhone’s number and you clicked OK anyway, such that iTunes doesn’t list the phone number when your iPhone is plugged in, this code will return a null string.

[Above is an edited concatenation of comments I recently posted to another article on this topic at http://www.alexcurylo.com/blog/2008/11/15/snippet-phone-number/]

Crisp
A: 

Here is some more information on a way to get it from iTunes which may be useful for testing purposes.

Andrew Burns
A: 

I had success with such code:

- (NSString *)stringUniqueID {
 NSString *  result;
 CFUUIDRef   uuid;
 CFStringRef uuidStr;
 uuid = CFUUIDCreate(NULL);
 assert(uuid != NULL);
 uuidStr = CFUUIDCreateString(NULL, uuid);
 assert(uuidStr != NULL);
 result = [NSString stringWithFormat:@"%@", uuidStr];
 assert(result != nil);
 NSLog(@"UNIQUE ID %@", result);
 CFRelease(uuidStr);
 CFRelease(uuid);
 return result;
}
Holtwick
A: 

This code snippet does not work for iPod touch. It returns null.

sg