+ Nicole Yee
On Mon, Feb 5, 2018 at 5:03 PM, Mark Hammond wrote:
> Richard does raise some other points not covered in bug 1419505. I just
> opened bug 1435917 (blocking bug 1415385) for this.
>
> Thanks,
>
> Mark
>
> On 6/02/2018 10:05 am, Dave Townsend wrote:
>
>> I think we have the sync case
Richard does raise some other points not covered in bug 1419505. I just
opened bug 1435917 (blocking bug 1415385) for this.
Thanks,
Mark
On 6/02/2018 10:05 am, Dave Townsend wrote:
I think we have the sync case covered in
https://bugzilla.mozilla.org/show_bug.cgi?id=1419505
On Mon, Feb 5, 2
I think we have the sync case covered in
https://bugzilla.mozilla.org/show_bug.cgi?id=1419505
On Mon, Feb 5, 2018 at 3:04 PM Richard Newman 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
>
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 wrote:
> As we briefly discussed some months ago, this will cause Sync devices to
> collide: you'll have two profiles t
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
5 matches
Mail list logo