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 Wed, 30 May 2012 15:05:23 GMT


Avidan Chen commented on CB-49:

Is there any chance the above implementation (
will be implemented into Apache Cordova iOS? I really need a way to identify a device in a
consistent manner, even if the user uninstalls and re-installs my app (further explanation
on why exactly I need that can be found here:!searchin/phonegap/UUID/phonegap/benUNTXTUYM/La-9PJSNVI0J).

>From what I understand, the above implementation is good enough not to upset Apple as
it does not access the user's private information, nor does it allow tracking a device using
this id (as the mac address + bundle identifier is encoded one way), and it's solid enough
so that the same value will be returned even if the user uninstalls and re-installs my app,
or updates the iOS version, etc.

The current implementation of device.uuid in iOS gives me a different value every time I update
my app or uninstalls and re-installs it, which is a really big issue for me.
> 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