Closed BobVul closed 4 years ago
It's probably possible to get into this state by manually disabling credit-card support in Firefox, but leaving it enabled in sync. Setting services.sync.engine.creditcards
and services.sync.engine.creditcards.available
to false should fix this.
Thanks for the response.
I also had to remove services.sync.engineStatusChanged.creditcards
(/set it to false) otherwise it kept trying (and failing) to update enabled engines.
To be honest, I mostly care because it's been causing about:sync to constantly report errors. Seems like it doesn't affect anything else syncing, thankfully. It's good to have that cleared, though!
Should I leave this issue open to track actual support for creditcards? I'm personally happy with just disabling it and leaving it at that.
Hm. services.sync.engine.creditcards
keeps getting reset to true
...
Hm.
services.sync.engine.creditcards
keeps getting reset totrue
...
That's probably OK so long as .available
remains false. I don't think we need this open for now, but feel free to reopen or ping me if you have more issues.
[edit: s/true/false/]
I'm seeing errors from the creditcards engine, even if I disable it.
Is there any way to prevent these errors? I'm happy to fully disable this engine (on either the client or server), but even that causes errors.
With creditcards enabled (default):
With creditcards disabled via preferences: