okay, i respect all your suggestion, let's leave it unchanged. On Thu, Aug 25, 2016 at 5:32 AM Shazron <shaz...@gmail.com> wrote:
> +1 leave unchanged. This is what Apple has intended, and going against the > spirit of what they intend and rocking the boat (so to speak) is fraught > with risk to the project. > > That being said, you could put this feature into your own plugin -- fork > the device plugin and call it something else. In the (unlikely) case in the > future if this rule has changed, the code can be integrated into core. > > On Wed, Aug 24, 2016 at 10:24 AM, Simon MacDonald < > simon.macdon...@gmail.com > > wrote: > > > I agree the current behaviour of device.uuid for iOS should remain > > unchanged. > > > > > > Simon Mac Donald > > http://hi.im/simonmacdonald > > > > On Wed, Aug 24, 2016 at 12:53 PM, Kerri Shotts <kerrisho...@gmail.com> > > wrote: > > > > > I’ve got multiple cents worth of opinions on this one, so bullet points > > > (each worth 2¢): > > > > > > Persistent UUID is (IMNSHO) anti-user and bad for privacy. I’ve yet to > > see > > > a good reason why this would be a good thing to support, and I’m glad > > Apple > > > doesn’t let apps get it anymore. As such, I’m OK with the device plugin > > not > > > guaranteeing an immutable identifier. > > > I don’t like lots of inconsistency between platforms, though. So for > the > > > same reason I’d vote -1 for device.uuidForVendor as iOS only is the > same > > > reason I don’t like the fact that UUID currently behaves differently > > across > > > platforms. > > > But I don’t like adding lots of code and using keychain to fix that. > Not > > > everyone who uses device is going to need the keychain, and so (for the > > > vast majority of dev), this seems like wasted code and bytes. > > > So my hope would be this: device.uuid gets deprecated and goes away > > > eventually. This results in less inconsistency between platforms, and > > > removes an anti-user tracking mechanism in the process. Should someone > > need > > > it, well… they can create a plugin for it. > > > Somewhat related: what’s device.serial used for? Since it supports only > > > Android & OS X, perhaps it should also go away? > > > > > > ~ Kerri > > > > > > > On Aug 24, 2016, at 03:00, Zam Light <love8879...@gmail.com> wrote: > > > > > > > > i knew apple restricted the real uuid usage, > > > > but let's minimize the thing, other platform seems to return reliable > > > > unique uuid per device with same user, > > > > and iOS return a different behavior in uninstall and reinstall > > situation. > > > > it looks little weird when use plugin because of different behavior. > > > > > > > > how about device.uuid return unique key and device.uuidForVendor for > > iOS > > > > platform only? > > > > > > > > On Wed, Aug 24, 2016 at 8:07 AM Jesse <purplecabb...@gmail.com> > wrote: > > > > > > > >> Please do not add this to the cordova-plugin-device, if you want to > > > create > > > >> a new plugin to handle this, then go for it. > > > >> Apple restricted the real uuid's use for a reason, and cordova > should > > > >> respect it. > > > >> > > > >> > > > >> @purplecabbage > > > >> risingj.com > > > >> > > > >> On Tue, Aug 23, 2016 at 12:05 PM, julio cesar sanchez < > > > >> jcesarmob...@gmail.com> wrote: > > > >> > > > >>> As the issue is an improvement and not a bug, I think we should > > discuss > > > >> if > > > >>> this should be added. I commented this on the issue long time ago > > > >>> > > > >>> > > > >>> So I think that storing the identifierForVendor on the keychain > might > > > be > > > >> a > > > >>> good idea, but not sure if we should add it to the device plugin or > > if > > > >> the > > > >>> developer should use a keychain plugin to store the device.uuid > value > > > if > > > >> we > > > >>> wants to get always the same value, maybe some developers want the > > real > > > >>> identifierForVendor value and not the first one > > > >>> > > > >>> > > > >>> > > > >>> I think keychain is very complex and will add a lot of code to the > > > >>> plugin just to store a value, and some users might want the real > > > >>> identifierForVendor value. If an user wants to store the value can > > use > > > a > > > >>> keychain plugin. > > > >>> > > > >>> > > > >>> El martes, 23 de agosto de 2016, Shazron <shaz...@gmail.com> > > escribió: > > > >>> > > > >>>> Done. > > > >>>> > > > >>>> On Tue, Aug 23, 2016 at 10:15 AM, Zam Light < > love8879...@gmail.com > > > >>>> <javascript:;>> wrote: > > > >>>> > > > >>>>> Hi: > > > >>>>> > > > >>>>> i want to solve this issue with below link, could someone assign > me > > > >> to > > > >>>> it? > > > >>>>> > > > >>>>> https://issues.apache.org/jira/browse/CB-9963? > > > >>> focusedCommentId=15432832& > > > >>>>> page=com.atlassian.jira.plugin.system.issuetabpanels: > > > >>>>> comment-tabpanel#comment-15432832 > > > >>>>> > > > >>>>> > > > >>>>> -- > > > >>>>> Best Regards, > > > >>>>> Zam > > > >>>>> > > > >>>> > > > >>> > > > >> > > > > -- > > > > Best Regards, > > > > Zam > > > > > > > > > -- Best Regards, Zam
