@dotproto Good news!
I’ve just managed to reproduce the issue I’ve mentioned above (where the bade doesn’t update).
It’s super random, I had to wait for the script to stop and then update storage and repeat like 10 times and NOW I have a stack trace error:
Text version:
WebExtension context not found! ExtensionParent.sys.mjs:1362:13
getContextById resource://gre/modules/ExtensionParent.sys.mjs:1362
recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1181
_recv resource://gre/modules/ConduitsChild.sys.mjs:90
receiveMessage resource://gre/modules/ConduitsParent.sys.mjs:470
(Async: JSActor query)
_doSend resource://gre/modules/ConduitsChild.sys.mjs:64
_send resource://gre/modules/ConduitsChild.sys.mjs:125
callParentAsyncFunction resource://gre/modules/ExtensionChild.sys.mjs:900
get chrome://extensions/content/child/ext-storage.js:318
callAsyncFunction resource://gre/modules/ExtensionCommon.sys.mjs:1196
callAsyncFunction resource://gre/modules/ExtensionChild.sys.mjs:726
callAndLog resource://gre/modules/ExtensionChild.sys.mjs:706
callAsyncFunction resource://gre/modules/ExtensionChild.sys.mjs:725
stub resource://gre/modules/Schemas.sys.mjs:2954
O moz-extension://6329fc15-83a7-467b-bd3d-f1a4a343afe0/background/background_sntd.js:1
ae moz-extension://6329fc15-83a7-467b-bd3d-f1a4a343afe0/background/background_sntd.js:1
InterpretGeneratorResume self-hosted:1417
AsyncFunctionNext self-hosted:804
(Async: async)
<anonymous> moz-extension://6329fc15-83a7-467b-bd3d-f1a4a343afe0/background/background_sntd.js:1
<anonymous> moz-extension://6329fc15-83a7-467b-bd3d-f1a4a343afe0/background/background_sntd.js:1
Something throws when the event should fire and that will fail to wake up the background script!
Please pass this to the devs, I’m still running 128.0b5 version.
I’ll go sleep now, good night
.
