Open adamanldo opened 7 months ago
I find that with FF 128.03, MAC 8.1.3, it doesn't matter what I enable or try - I'm unable to create a new container and get it to synchronize to another FF installation.
FWIW i use 'MAC' instead of 'container'
I'm (mainly) in Nightly 132.0a1 (2024-09-23) (64-bit) mozilla-deb - 1.0
and just trying to spec up a normie 130.0.1 (64-bit) mozilla-deb - 1.0
and I see the same as you, @rob-miller ... well ... kind of.
I had already renamed a MAC (at least a week or more ago) ... but when I added the account to a brand new profile in 'normieFF' and synced for the first time ... it did not sync the renamed MAC (or any of the other, new, ones) to the new profile.
I am mentioning this here, as it feels like it would be the same components causing the issue.
I cannot now trust that it will safely not erase the container setup in this browser. Tiny bit worried about that, tbh ... as I rely upon it heavily for my work productivity.
edit
Hmmm ... I'm seeing a lot about this kind of thing in the issues, whilst perusing an open issue search on 'sync' or Danny's 'Sync' Component ... like this one from last year.
I wonder if this error that I've spotted in the extension inspector has anything to do with it:
Uncaught (in promise) Error: QuotaExceededError: storage.sync API call exceeded its quota limitations. 🤔
Is it possible that this is contributing, maybe?
Before submitting a bug report
Step to reproduce
Actual behavior
When Add-on syncing is disabled, multi-account containers do not sync even if synchronization is enabled in the multi-account container settings on both machines.
Expected behavior
There should be a prompt to let you know that the synchronization will not work unless Add-on synchronization is enabled.
Additional informations
No response
Provide a copy of Troubleshooting Information page (optional)
No response