Open
Bug 1264584
Opened 9 years ago
Updated 2 years ago
Duplicate devices in Synced Tabs
Categories
(Firefox for iOS :: Sync, defect, P3)
Tracking
()
People
(Reporter: csuciu, Unassigned)
References
Details
(Whiteboard: [device-manager] [MobileCore])
1. Sign in with the same FxA on two iOS devices
2. Open a few tabs on each device then sync between devices
3. On first device, sign out/sign in with the same FxA
4. Sync again on both devices
5. Check the 'Synced Tabs' panel on the second device
Result: On the second device, in 'Synced Tabs' panel, the first device will be duplicated
There are discussion about fixing this issue on Android and Desktop here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1264498
https://bugzilla.mozilla.org/show_bug.cgi?id=1250531
Updated•9 years ago
|
tracking-fxios:
--- → ?
Updated•9 years ago
|
Rank: 3
Updated•9 years ago
|
Comment 1•8 years ago
|
||
Mark, is this something we should deal with in Firefox for iOS?
Flags: needinfo?(markh)
Comment 2•8 years ago
|
||
(In reply to Stefan Arentz [:st3fan] from comment #1)
> Mark, is this something we should deal with in Firefox for iOS?
Probably - IMO users are not likely to actually hit this as they don't regularly disconnect then reconnect devices. However, desktop did it in the referenced bugs by doing simple stripping of devices that have another device with the same name and haven't synced in over a week - which isn't perfect, but possibly better than nothing.
Flags: needinfo?(markh)
Comment 3•8 years ago
|
||
We believe this should be fixed by using fxa's device manager registration work.
Priority: -- → P3
Updated•8 years ago
|
Whiteboard: [device-manager]
Updated•8 years ago
|
Updated•8 years ago
|
Whiteboard: [device-manager] → [device-manager] [MobileAS]
Updated•8 years ago
|
Updated•8 years ago
|
Whiteboard: [device-manager] [MobileAS] → [device-manager] [MobileCore]
Updated•8 years ago
|
Updated•8 years ago
|
Rank: 3 → 1
Updated•7 years ago
|
Updated•7 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•