-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling multi-account-containers causes desync #1650
Comments
Possibly related to #1413 ? |
Disabling the last Add-on that keeps the containers feature active resets containers to the default (#1236), but keeps MAC's storage, so when re-enabling the sync potentially might get confused. |
In my case containers and settings were partly restored by synch after re-enabling the addon. I had setup the Addon and enabled the synch feature. There should be a warning that disabling the Addon will delete all your custom settings. |
I recently had to disable all my addons to work out which was causing an issue. A common thing for people to do. I lost all my settings :(. I can reproduce trivially. First: Reproduction instructions:
Obviously this is showing that deletion of containers isn't working, not containers being lost. Theoretically that could be a separate issue, but I doubt it. |
It definitely sounds like a duplicate/variant of #1236 but seasoned with a bit of FxA sync on top of it! |
Actual behavior
After setting up sync in the addon, my containers properly synced. I then disabled the addon momentarily in order to log off a site in the default container. Upon re-enabling the addon, the containers added by sync are gone and have yet to come back even after closing and re-opening Firefox.
Expected behavior
The synced containers persist through a disabling and re-enabling of the addon
Steps to reproduce
Notes
I don't know if there's a way to manually initiate a containers sync. I tried initiating a normal Firefox Sync, though that didn't help the situation. I also tried adding a new container to see if that would a trigger a new container sync to re-add the lost containers with no luck.
The text was updated successfully, but these errors were encountered: