-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
cloud syncing not working anymore #3113
Comments
Because Firefox sync storage for the new webext architecture is not shared with the legacy one. You will have to push again your data in the cloud. There is nothing uBO/webext can do, it does not have access to legacy cloud storage. |
Also, duplicate of #3022. |
...so? even with manually pushing once every instance of FF only sees its own data. I cannot sync between different machines. |
got it nailed. Having FF 52 ESR was the issue. I updated Firefox on my linux systems to FF 56 (same as on windows) and pop it syncs properly now. |
Right, sync storage was added in Firefox 53: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/storage#Browser_compatibility. Not available in Firefox for Android. |
I guess I better file tickets with Red Hat and SUSE requesting they update their ESR versions to something newer. |
So those of us that are on the ESR track are stuck on 1.13.8? |
SUSE will stay on ESR for their Enterprise and stable Leap releases. |
@gorhill, is there any way to support sync on 52ESR? Maybe fallback to the old method? |
Describe the issue
Since (i think) the update for mozillas new extension architecture cloud-syncing ublock origin settings between devices has stopped working.
Screenshot in which the issue can be seen
[Screenshot(s) for visual issues are mandatory]
Steps for anyone to reproduce the issue
setup mozilla sync
enable cloud support in ublock origin
observe that there are no settings to be imported, even after manually triggering a mozilla sync
Your settings
Your filter lists
default + DEU
Your custom filters (if any)
none so far since it's not syncing.
The text was updated successfully, but these errors were encountered: