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 Mon, 25 Jun 2012 06:53:42 GMT


Avidan Chen commented on CB-49:

Thanks. I appreciate you taking the time to address my questions in this matter.

In the user registration screen in my app, I'm sending the device.uuid to the server as part
of the new user credentials. Later, when a user is authorized by their manager to use the
app and tries to log in, I'm sending the uuid as part of the credentials. If the uuid matches
what is stored in the DB, the user is allowed to log in. Otherwise, their manager needs to
approve the new device (which is a requirement that came from the product manager, as my application
allows access to sensitive information, and it's vital for the manager to know from where
the employee accesses this information).

Apple has approved my app in April which was running Phonegap 1.2, even though I'm using device.uuid.

I understand your concern that Apple might reject apps using device.uuid, but unfortunately
I cannot wait for the release of 2.0.
As Apple have already approved my app once, I think I'll try my luck again, but this time

if (!ios6) 
  [UIDevice uniqueIdentifier] 
  [UIDevice identifierForVendor] 

as a plugin. Hopefully they won't reject my app.

Do you know of any tutorial on how to write plugins for Cordova 1.8 for iOS and Android? I
can't seem to find any.

> 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