Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4EC42200B7C for ; Thu, 25 Aug 2016 05:26:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4D35C160AC1; Thu, 25 Aug 2016 03:26:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6EBE5160AB1 for ; Thu, 25 Aug 2016 05:26:17 +0200 (CEST) Received: (qmail 3560 invoked by uid 500); 25 Aug 2016 03:26:16 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 3548 invoked by uid 99); 25 Aug 2016 03:26:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2016 03:26:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B3FD1C1CA4 for ; Thu, 25 Aug 2016 03:26:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.448 X-Spam-Level: ** X-Spam-Status: No, score=2.448 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLY=1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id wHdmhw3fjCSh for ; Thu, 25 Aug 2016 03:26:13 +0000 (UTC) Received: from mail-ua0-f172.google.com (mail-ua0-f172.google.com [209.85.217.172]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id CF8985F30C for ; Thu, 25 Aug 2016 03:26:12 +0000 (UTC) Received: by mail-ua0-f172.google.com with SMTP id k90so63007472uak.1 for ; Wed, 24 Aug 2016 20:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OeWJ3blWECPUvZgLFvB4sEyyucDKkH1wlZkEM0b2Oq0=; b=JJSmtycxue/N0NHb9S6LuDJEOXv4drg3+IDC72uwYqZ2e1+Xoq2LWFaaE4t1K+jr1b s6Nb+gBYZu3wZzTQyzYkNA/wUF4tM/GiZGTogm+qUQtuHAOpFecTWrsX5uT1PBByaa8C GJ33TzFfCUx2PRYZUbQIx+QkHQ+la8i0F79xzriek+/NVPbAM56cipdFC2YE4XVVAzoE aIVy2V+mpqjxSP4r5neMton3XYJq4aVJ4KOEaVHYE7oyBI1U33rWyS+2F8I9CICX4l0C 1S3dPVHl1YSuoMn9hUneI8RANELponxvAcOqKNG1cxluyCxuXu/JmUPrMqUdDNhZUAp+ tR0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OeWJ3blWECPUvZgLFvB4sEyyucDKkH1wlZkEM0b2Oq0=; b=kqZtrvW0zFTARfPSey6C33vKCuMNa03N6icieBAlM+H8EziktT8p5GQMjeut7tB4HU Yy+15UrTck9z3ftJ2g+RHN5KF7F7rMLQZYNI4aqdNX+Ht+c3ONzLZvzoTw+7V3dB11fO viplO517azzvf7hzsFA8FvGEmOfYyap22dn+QFfwybY8SzlpTMlaQvna4mIyBPuPfP6A 70ri1Bb1Gzazng5H48rXr/F4HQBBac1DFYYg5BAMnoff7WYB+fwkrRPVkgi87Dbf39OJ k2dj9UigSEgzahVw3shGKyz0j3gz4bO9TM3Zun91MoZUb7cYHPvUkCmmxxLmKYaHN2wa lGZA== X-Gm-Message-State: AEkooutu92T+IW2KFpp7Gu/xLfVggeNSdIh/ucTI77PfNyRrXAV1V5QGhrlimd31VGAbNfZbP2mA9c0q2uVpVA== X-Received: by 10.31.236.66 with SMTP id k63mr3684168vkh.48.1472095565601; Wed, 24 Aug 2016 20:26:05 -0700 (PDT) MIME-Version: 1.0 References: <2F738899-45B7-41DE-B1F9-941A7ABD374A@gmail.com> In-Reply-To: From: Zam Light Date: Thu, 25 Aug 2016 03:25:54 +0000 Message-ID: Subject: Re: CB-9963 iOS uuid should remain even after uninstall To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=94eb2c0920fa43685a053adcf5db archived-at: Thu, 25 Aug 2016 03:26:18 -0000 --94eb2c0920fa43685a053adcf5db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable okay, i respect all your suggestion, let's leave it unchanged. On Thu, Aug 25, 2016 at 5:32 AM Shazron wrote: > +1 leave unchanged. This is what Apple has intended, and going against th= e > 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 t= he > 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.macdonald@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 > > wrote: > > > > > I=E2=80=99ve got multiple cents worth of opinions on this one, so bul= let points > > > (each worth 2=C2=A2): > > > > > > Persistent UUID is (IMNSHO) anti-user and bad for privacy. I=E2=80=99= ve yet to > > see > > > a good reason why this would be a good thing to support, and I=E2=80= =99m glad > > Apple > > > doesn=E2=80=99t let apps get it anymore. As such, I=E2=80=99m OK with= the device plugin > > not > > > guaranteeing an immutable identifier. > > > I don=E2=80=99t like lots of inconsistency between platforms, though.= So for > the > > > same reason I=E2=80=99d vote -1 for device.uuidForVendor as iOS only = is the > same > > > reason I don=E2=80=99t like the fact that UUID currently behaves diff= erently > > across > > > platforms. > > > But I don=E2=80=99t like adding lots of code and using keychain to fi= x that. > Not > > > everyone who uses device is going to need the keychain, and so (for t= he > > > 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 someon= e > > need > > > it, well=E2=80=A6 they can create a plugin for it. > > > Somewhat related: what=E2=80=99s device.serial used for? Since it sup= ports only > > > Android & OS X, perhaps it should also go away? > > > > > > ~ Kerri > > > > > > > On Aug 24, 2016, at 03:00, Zam Light wrote: > > > > > > > > i knew apple restricted the real uuid usage, > > > > but let's minimize the thing, other platform seems to return reliab= le > > > > 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 fo= r > > iOS > > > > platform only? > > > > > > > > On Wed, Aug 24, 2016 at 8:07 AM Jesse > wrote: > > > > > > > >> Please do not add this to the cordova-plugin-device, if you want t= o > > > 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 < > > > >> jcesarmobile@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 th= e > > real > > > >>> identifierForVendor value and not the first one > > > >>> > > > >>> > > > >>> > > > >>> I think keychain is very complex and will add a lot of code to th= e > > > >>> plugin just to store a value, and some users might want the real > > > >>> identifierForVendor value. If an user wants to store the value ca= n > > use > > > a > > > >>> keychain plugin. > > > >>> > > > >>> > > > >>> El martes, 23 de agosto de 2016, Shazron > > escribi=C3=B3: > > > >>> > > > >>>> Done. > > > >>>> > > > >>>> On Tue, Aug 23, 2016 at 10:15 AM, Zam Light < > love8879201@gmail.com > > > >>>> > wrote: > > > >>>> > > > >>>>> Hi: > > > >>>>> > > > >>>>> i want to solve this issue with below link, could someone assig= n > me > > > >> to > > > >>>> it? > > > >>>>> > > > >>>>> https://issues.apache.org/jira/browse/CB-9963? > > > >>> focusedCommentId=3D15432832& > > > >>>>> page=3Dcom.atlassian.jira.plugin.system.issuetabpanels: > > > >>>>> comment-tabpanel#comment-15432832 > > > >>>>> > > > >>>>> > > > >>>>> -- > > > >>>>> Best Regards, > > > >>>>> Zam > > > >>>>> > > > >>>> > > > >>> > > > >> > > > > -- > > > > Best Regards, > > > > Zam > > > > > > > > > --=20 Best Regards, Zam --94eb2c0920fa43685a053adcf5db--