I see https://bugzilla.mozilla.org/show_bug.cgi?id=1419505 already exists for this, so this mail might just be a broader headsup!
On Mon, Feb 5, 2018 at 3:04 PM, Richard Newman <rnew...@mozilla.com> wrote: > As we briefly discussed some months ago, this will cause Sync devices to > collide: you'll have two profiles that both believe they're FxA device > 12345 and Sync client abcdef. > > Avoiding this should be possible by allocating a new Sync client ID, > forcing the clients collection to need a sync (lastSync = 0), and doing > something similar with FxA device registration. This could potentially > require the user to re-enter their FxA password, but I'm not sure. > > Dropping fx-data-dev, CCing FxA and Sync to discuss. > > On Mon, Feb 5, 2018 at 2:45 PM, Dave Townsend <dtowns...@mozilla.com> > wrote: > >> A new feature we are targetting for Firefox 60 involves giving each >> release channel a separate profile by default. In order to push users into >> this situation on upgrade non-release channels will make a clone of the >> release profile for use going forwards. Currently this is a complete copy >> of all files and settings from the release profile which raises a couple of >> immediate potential issues: >> >> The value of toolkit.telemetry.cachedClientID will be shared across >> potentially many profiles. I could probably regenerate this for each cloned >> profile if there is a procedure for doing this. >> >> Any unsent pings will be cloned and so may be sent as duplications. The >> only way to avoid this would be to not clone the ping but that might mean >> that those pings are never sent. I'm not sure which is preferable. >> >> Any other issues I'm not considering? >> >> _______________________________________________ >> Fx-data-dev mailing list >> fx-data-...@mozilla.org >> https://mail.mozilla.org/listinfo/fx-data-dev >> >> >
_______________________________________________ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
