Dark Reader no longer working / fails to initialize
Categories
(GeckoView :: Extensions, defect, P1)
Tracking
(firefox78 fixed, firefox79 fixed)
People
(Reporter: csadilek, Assigned: agi)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [geckoview:m79])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
Dark Reader stopped working in Nightly 79.0.20200605043926.
Still fine in Nightly 79.0.20200604092907.
Fenix bug: https://github.com/mozilla-mobile/fenix/issues/11336
Relevant entry from the logs:
can't access property "config", $sync is undefined index.js:1896
loadSettingsFromStorage moz-extension://f330e768-8120-488d-b54e-28e2209d7a63/background/index.js:1896
apply self-hosted:1941
applySafeWithoutClone resource://gre/modules/ExtensionCommon.jsm:614
wrapPromise resource://gre/modules/ExtensionCommon.jsm:843
withLastError resource://gre/modules/ExtensionCommon.jsm:762
wrapPromise resource://gre/modules/ExtensionCommon.jsm:831
loadExtensionFile moz-extension://6b69d78a-1335-42dd-b4fd-9f39115ab558/background-scripts/util.js:49
applyStoredRulesets moz-extension://6b69d78a-1335-42dd-b4fd-9f39115ab558/background-scripts/update.js:218
InterpretGeneratorResume self-hosted:1151
AsyncFunctionNext self-hosted:693
Unchecked lastError value: Error: An unexpected error occurred index.js:1894
loadSettingsFromStorage moz-extension://f330e768-8120-488d-b54e-28e2209d7a63/background/index.js:1894
Assignee | ||
Comment 1•5 years ago
|
||
Thanks. Bisecting...
Assignee | ||
Comment 2•5 years ago
|
||
14:44.57 INFO: Last good revision: 6bb6a5cdc941eaa15c0e36dcaf8e4ad8509d4e90
14:44.57 INFO: First bad revision: fc977a4eff9e6a1d27b1efdc3e0980bc5958976d
14:44.57 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6bb6a5cdc941eaa15c0e36dcaf8e4ad8509d4e90&tochange=fc977a4eff9e6a1d27b1efdc3e0980bc5958976d
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Mark any ideas? this seems to completely break storage.sync
on Android.
Assignee | ||
Comment 4•5 years ago
|
||
This also adds a smoke test which runs on all platforms to avoid regressions.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Ooof, thanks for catching this, Agi!
Wait, though—how did this sync before, given that we aren't shipping the Desktop FxA stack in GV? Or was Dark Reader effectively using storage.sync
for local storage only before?
I wrote about one way we could support storage.sync
in GV, so that Android Components could wire it up to our Rust component, in this comment—do you think that would work?
Assignee | ||
Comment 6•5 years ago
|
||
No worries! Yeah storage.sync
is effectively a local storage today on Android.
Yeah I just linked that comment on our bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1625257 the API you describe is very similar to what snorp and I were thinking last time we talked about this, it should work!
Comment 7•5 years ago
|
||
Gotcha! I'll follow bug 1625257; thanks for linking to it, and for the fix and test!
Assignee | ||
Updated•5 years ago
|
Comment 10•5 years ago
|
||
bugherder |
Comment 11•5 years ago
|
||
Comment on attachment 9155440 [details]
Bug 1644297 - Re enable old browser.storage.sync on Android.
I'm going to graft this to beta along with bug 1645598. The pref change is a no-op there, but this way 78 will get the new test file (which is modified in that other bug).
Comment 12•5 years ago
|
||
bugherder uplift |
Description
•