incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avidan Chen (JIRA)" <>
Subject [jira] [Commented] (CB-49) UUID replacement
Date Tue, 19 Jun 2012 04:02:42 GMT


Avidan Chen commented on CB-49:

OK. Understood. I thought this would be good for other platforms because it's simple to implement
and protects the user's privacy, but if you think otherwise...

But if Apple is offering identifierForVendor - why not use it? According to the description,
this has the exact functionality of the previous UUID implementation - uniquely identifying
a device for us, minus the privacy issues.

If Apple is now replacing [UIDevice uniqueIdentifier] with [UIDevice identifierForVendor]
surely they won't ban applications using the [UIDevice uniqueIdentifier] in iOS 5 when there's
no alternative... 
So maybe device.uuid could return [UIDevice uniqueIdentifier] in iOS 5, and [UIDevice identifierForVendor]
in iOS 6? We would need to adjust for users switching between iOS 5 & 6, but it'd be a
one time change to the UUID for us, instead of getting a new UUID for every installation,
which is useless to us.
> UUID replacement
> ----------------
>                 Key: CB-49
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>         Environment: iOS 5
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>            Priority: Blocker
>             Fix For: 1.6.0
> reported at:
> by:
> As you might have read iOS 5 will remove the UDID (
> This is an excellent alternative and it would be nice if you would implement something
along these lines to keep the functionality. The idea of hashing together with the bundle
id is great, because it makes it impossible to track across applications, which is what apple
wanted to fix (although it can be circumvented that would only anger them, and tracking across
apps isn't required for most apps anyway).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message