Skip to content
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

Stopped working on Firefox (until reinstall) #105

Closed
NicoWeio opened this issue Apr 2, 2023 · 13 comments
Closed

Stopped working on Firefox (until reinstall) #105

NicoWeio opened this issue Apr 2, 2023 · 13 comments

Comments

@NicoWeio
Copy link

NicoWeio commented Apr 2, 2023

In the timeline and raw views, there was no browser activity from Firefox since the last day or so. The aw-watcher-web extension said Enabled and Connected, but the Last sync was a while back. Restarting the browser did not help, neither did disabling and re-enabling.
What finally solved my problem was uninstalling and reinstalling the extension, after which I was prompted to agree to AW's data collection.
I suspect this happened because of the now-live consent update discussed in https://github.com/orgs/ActivityWatch/discussions/818, but haven't had time to dig deeper.

@eskoONE
Copy link

eskoONE commented Apr 4, 2023

is it really working for you? because it did for me for a minute and then stopped recording again. im not sure whats causing this.

@cachedout
Copy link

I can confirm this behavior though in my case it appears that all tracking has stopped. I did remove and then re-install the browser plugin and it worked briefly before stopping again.

@NicoWeio
Copy link
Author

NicoWeio commented Apr 4, 2023

@eskoONE Yes, it's still working as expected since the reinstall. Did you see the new data collection prompt upon reinstallation? What does your browser extension say when you click it (Enabled / Connected / Last Sync)?
Since you and @cachedout describe the same phenomenon, it might be worth pointing out that I use activitywatch-bin from the AUR on Manjaro Linux and since the extension's reinstall, I run aw-server in a terminal ($ aw-server --verbose). You could try to do the same; maybe it tells you what the problem is.

@isle9
Copy link

isle9 commented Apr 6, 2023

Seems like the background script doesn't seem to start until you manually re-enable it every time you open the browser.

@NicoWeio
Copy link
Author

NicoWeio commented Apr 6, 2023

Thanks, @isle9!
I rarely restart my browser, so that might be the reason it kept working for me so far.

@ErikBjare
Copy link
Member

Asked ChatGPT4 by feeding it the source file and @isle9's description:

image

Making a PR and new release now.

ErikBjare added a commit that referenced this issue Apr 6, 2023
@ErikBjare
Copy link
Member

Reopening until new version has been approved by Mozilla

@ErikBjare ErikBjare reopened this Apr 6, 2023
@ErikBjare
Copy link
Member

New version should be out now. Let me know if you find any issues!

@isle9
Copy link

isle9 commented Apr 7, 2023

Unfortunately, it seems like the Mozilla version still doesn't work properly. The background script still doesn't run automatically.

This issues seems like it might be connected too.

@ArgonBeryllium
Copy link

ArgonBeryllium commented Apr 24, 2023

Bump, having this issue using the recently re-released addons.mozilla.org version.
I've verified using the Query Explorer that there is indeed no data being received by the server beyond the last sync until restart(unchecking and re-checking the Enabled box), after which point logging seems to continue normally. The data in between is either lost or was never logged to begin with.

I'm running AW v0.12.2 (rust) and Firefox v111.0(64-bit) on Arch Linux.

@maestromac
Copy link

Similar to others, I have to uncheck-recheck "enabled" every time I launch my Firefox to get it working.

Firefox 102.0.1 Fedora 38

@isle9
Copy link

isle9 commented May 28, 2023

Any chance this gets fixed any time soon or should I just switch to Chromium?

@ErikBjare
Copy link
Member

ErikBjare commented May 28, 2023

I released an updated version 6 days ago that should have fixed the bug: #107 (comment)

powellnorma pushed a commit to powellnorma/aw-watcher-web that referenced this issue Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants
@cachedout @ErikBjare @NicoWeio @maestromac @eskoONE @ArgonBeryllium @isle9 and others