1323240 - Wipe the dev server for chrome.storage.sync

Status: VERIFIED FIXED

(WebExtensions :: Untriaged, defect, P2)

Description

[Ethan Glasser-Camp (:glasserc)]

Bug 1319742 reports a bug where a bad keyring is introduced into the chrome.storage.sync Kinto server. This keyring causes syncing of chrome.storage.sync to fail forever. Once the fix is uplifted, and such keyrings are no longer being created, we should wipe the server to get rid of the bad keyrings, so that syncing can resume more-or-less normally. (Since this is for extensions with temporary IDs, their data was "already lost" when this bug happened.) When this happens, we should also send a notice to dev-addons to let them know that it's happened.

Comment 1

[Ethan Glasser-Camp (:glasserc)]

The fix was uplifted to Aurora today, but asking in #developers, someone told me that it can take a week or so for builds of Aurora to make it to users. So I will probably do the wipe either Dec 23 or Dec 28.

Comment 2

[Ethan Glasser-Camp (:glasserc)]

I did the wipe today. My posts to dev-addons got blocked because I'm not a member, but hopefully someone will moderate them through the queue. For posterity, the text of my email was:

Hi!

Due to https://bugzilla.mozilla.org/show_bug.cgi?id=1319742, anyone who has tried to use the storage.sync API in Nightly or Aurora will have a bad keyring on the dev server. Now that the fix has been uplifted to Aurora, I am going to delete all the data on the dev server.

This might cause problems with any Firefox profiles that were trying to use this functionality. You might get "server was flushed" errors and data failing to sync. If this happens, you can try creating a new profile, or if you really want to keep the profile, you can wipe just the storage-sync data (in storage-sync.sqlite) and restart Firefox.

Any problems, please feel free to contact me. (I'm not on this mailing list.)

Comment 3

[Vasilica Tamas, QA [:vtamas]]

Performed a bit of exploratory testing around https://bugzilla.mozilla.org/show_bug.cgi?id=1319742#c25 (where was specified that the old accounts will continue to fail syncing forever until the server will be wiped) and I confirm that this issue is no longer reproducible for old accounts while using webextensions with temporary add-on ID.