cannot delete containers

[baddev]

Before submitting a bug report

• I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
• I searched for existing reports to see if it hasn't already been reported

Step to reproduce

I am unable to delete containers they keep coming back even after a uninstall and reinstall. Please help.

Actual behavior

delete container
after a while it comes back

Expected behavior

container shouldnt come back

Additional informations

No response

Provide a copy of Troubleshooting Information page (optional)

No response

[dannycolin]

Did you active Sync for Multi-Account Containers?

To find out:

1. Type about:addons in the address bar
2. Click on Multi-Account Containers in the addons list
3. Go to the addon "Preferences" tab
4. Look if "Enable Sync" is ticked.

[kurahaupo]

[edited, thanks @dannycolin]

As noted in #2436, containers are a core feature, functionally separate from any particular container management plug-in, with the exception that removing the only remaining container management plug-in will purge all containers.

[dannycolin]

Uninstalling and reinstalling won't have any effect whatsoever.

This isn't true. Uninstalling all addons using the container API will reset all container data to the default.

This is why I asked if @baddev has Sync enabled. On reinstalling the addon, Sync will restore the data from the remote server.

[kurahaupo]

@dannycolin Thanks for the correction.

If this is because Firefox Sync restores the containers, I then have to wonder how "enable sync" winds up being turned on when MAC is re-installed, in order for Firefox Sync to bring back the old containers?

Is it:

1. not reset when MAC is uninstalled (perhaps it should be); or
2. turned on by default when MAC is installed (perhaps it shouldn't be); or
3. something else?

It's hard to see what the perfect solution would look like, but erring on the side of keeping the containers when in doubt is probably better than unexpected deletions.

[dannycolin]

I then have to wonder how "enable sync" winds up being turned on when MAC is re-installed

It isn't enable by default. However during the first run, we ask the user if they want to enable it. Might be what happened here.

It's hard to see what the perfect solution would look like, but erring on the side of keeping the containers when in doubt is probably better than unexpected deletions.

Yes. The solution is to find out why deleting a container on one machine isn't honored by Sync.