incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-49) UUID replacement
Date Fri, 08 Jun 2012 23:32:23 GMT


Shazron Abdullah commented on CB-49:

That is a suitable alternative - but requires more work on the user's part, to combine these
values for the hash. Right now, I don't think this is the right solution for the Cordova API
device.uuid variable (there is a dependency on an external variable, this secret key - and
it is iOS specific), but it is suitable for a plugin.

All core Cordova functionality is implemented as plugins (these are core plugins). If after
discussion with all the devs it is suitable for all platforms and aligns with our project
goals, we can pull it in as core (if copyrights are assigned to Apache). For example, our
plan is to pull in the ChildBrowser plugin into the core for 2.0.

I am however, changing the UUID implementation again since iOS 5.x introduced new behaviour,
while still not unique (not based off MAC address), it has the same lifetime as described
in the iOS quirk for device.uuid: CB-748
> 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