aw-watcher-web: Firefox data is not shown in visualizations
I can see aw-watcher-web-firefox bucket in the timeline and in the raw data tab, but “Top Browser Domains” and “Top Browser URLs” visualizations show that there’s no data. Browser extension says that it’s connected to the server. I’m on Fedora 37 if it helps.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 9
- Comments: 33 (5 by maintainers)
The background script is not executed on browser startup because
persistentis set tofalse.https://github.com/ActivityWatch/aw-watcher-web/blob/b53d09997e97261e3246d1e225d12b4e4b85dd6f/manifest.json#L28
persistent: trueis also the default behavior when unset. And I don’t know of any extension that usespersistent: false.For reference:
https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/blob/ca628ccfa567eeb5e088c74812090659185132b2/extension/manifest.json#L2-L11 https://github.com/darkreader/darkreader/blob/6723337369f784468c28f1d757c46227255693aa/src/manifest.json#L22 https://github.com/darkreader/darkreader/blob/6723337369f784468c28f1d757c46227255693aa/src/manifest-firefox.json#L8-L10C2 https://github.com/ClearURLs/Addon/blob/14a0832973e137f0cbbbb1e9110c1286bc88e319/manifest.json#L57-L74 https://github.com/ajayyy/SponsorBlock/blob/b07381e5d0bae8cea21af7054f7a6464c889a6d4/manifest/manifest.json#L121-L125 https://github.com/gorhill/uBlock/blob/5ba3055bc77cf99ff20d5d29da53fc78b6b6e9e0/platform/firefox/manifest.json#L3-L5
I’m having this issue as well, it seems to work again if you disable then enable again in the extension menu (not in the firefox preferences)
I releases v0.4.8 with a possible fix this morning, it has been published on Mozilla Addons: https://github.com/ActivityWatch/aw-watcher-web/releases/tag/v0.4.8
Plrease report any continued issues you experience.
I’ve discovered a temporary solution that allows logging and synchronization by reloading the extension within the “Inspect” developer tools window while debugging is activated. It seems that when the extension is loaded in the typical manner, it doesn’t properly integrate with the browser and fails to operate in the background.
Workaround steps:
about:debuggingin the address bar.Hm, I toggled the checkbox off and then on, but the issue still persists. Could you describe what you did in a bit more detail? Maybe I’m missing some step.
Hi guys, we just released
v0.5.0, feel free to install and report if it still occurs 😃If your specific bug is still occurring, please open a new issue with exact details, as there are several different problems being discussed here.
If you have a browser named
unknownin the window watcher, the problem isn’t in the web extension, you probably need to installawatcher.IDK. Depends on your installation path.
For file name. IDK either. It’s hash instead of a readable filename. You can try to find the file with the same name in my image or search in the directory with tool like VSCode in the image
I had to give consent to the collection of offline data again, but now it seems to work 😃 (still, I will check it regularly the next days to make sure it works reliably)
Thanks for the fix!
It is unknown 😦
Same issue and I can reproduce @pi314ever 's solution. Seems like the extensions for some reason does not start properly when starting Firefox. I’m on Windows, both activity watch and the Firefox extension are up-to-date. @da-the-dev I just clicked on the aw extensions icon on the search bar (or in the extension menu in the search bar) and then there is a checkbox behind “Enabled” which I toggled (to disable the extension). Then I clicked somewhere else to close the pop-up and opened it again to toggle the checkbox again.