Per-device sync should fail engines instead of going read-only when meta/syncids has a newer format version
Categories
(Firefox :: Sync, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox162 | --- | fixed |
People
(Reporter: skhamis, Assigned: skhamis)
References
(Blocks 1 open bug)
Details
Attachments
(1 external file)
When meta/syncids has a version newer than we support, EngineSyncIDs.load uses an empty record in memory and marks it read-only. Engines missing from meta/global then keep syncing with their local sync IDs, which never match what newer clients use, so sync IDs stop detecting wipes for those engines. Nothing reports this, and it lasts until the record is replaced.
Instead, treat a newer format the way we treat a newer engine version: fail the affected engines with VERSION_OUT_OF_DATE until the client is upgraded. Engines listed in meta/global keep syncing as now, and we still never write over the newer record.
Application Services is making the matching change in sync15 (https://github.com/mozilla/application-services/pull/7737).
| Assignee | ||
Updated•12 days ago
|
Updated•12 days ago
|
Updated•12 days ago
|
| Assignee | ||
Comment 1•11 days ago
|
||
Previously a newer-format registry was ignored and treated as read-only, so
engines missing from meta/global kept syncing with local sync IDs that newer
clients never see. We should treat it like a newer engine version instead: those
engines fail with VERSION_OUT_OF_DATE until the client is upgraded.
Updated•11 days ago
|
Comment 3•3 days ago
|
||
| bugherder | ||
Description
•