Window tracking not working after upgrade to v0.12.0

[rtpHarry]

• I am on the latest ActivityWatch version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• OS name and version: macOS Monterey 12.5.1

• ActivityWatch version: 0.12.0

Describe the bug

Since upgrading my aw-watcher-window bucket is empty.

I'm trying to refresh my memory from a year ago. I remember the titles use to go blank after an update, but this time its just totally empty.

The AFK tracker is populating ok.

I've gone into system preferences > security and permissions > accessibility and added in the AW executable in the Applications folder. (Is there any other category it wants to have?)

I've closed the app, and confirmed that the localhost server is no longer there, so I don't think its still running in the background. After reopening it, still no improvement.

There are some links to various issues but they don't seem to cover this.

To Reproduce

Expected behavior

Documentation

Additional context

[rtpHarry]

Just to be clear, as per this doc:

https://docs.activitywatch.net/en/latest/updating.html#macos

It wasn't in the accessibility list any more, so i didn't just tick it, I added it in, and then restarted AW but still not populating the window bucket.

[ErikBjare]

There are some links to various issues but they don't seem to cover this.

What makes you think this isn't fixed by the workarounds in #334? Looks like a similar issue to me.

One of these days I'm buying a Macbook to get rid of these macOS issues once and for all.

[rtpHarry]

Thanks for your reply. A lot of the early issues in #334 was actually me having problems with it before.

But that was before you started bundling it as a .dwg and whatnot.

There is a post reply where I got it working by giving it the permissions - #334 (comment)

That hasn't worked this time.

I have just re-read #334 and tried giving it "full file system" (with a close, restart and test) and then "developer tools" permissions but it hasn't done anything to fix the window bucket being empty.

Strangely that does seem to have just changed what it sees my computer as. Before it was .local and now its .net:

The afk .net version is now collecting data, and the window .net bucket has not collected anything.

I also tried removing and readding the accessibility now that it has these two other extra permissions, but no improvement.

[ErikBjare]

Wow, that's pretty bad. The hostname change is probably not related though, more likely to be your computer taking a transient hostname from a router or something (it's pretty annoying).

I saw that you were early in that other issue, Have you tried configuring aw-watcher-window to use the old applescript method instead of jxa? (edit the aw-watcher-window.toml in the config dir).

What do the logs say?

[BelKed]

I had the same issue, but launching ActivityWatch using Terminal helped: #334 (comment)

[Gleek]

I seem to have the same problem. Windows watcher stopped working correctly after the v0.12.0 upgrade

The #334 (comment) method worked partially. As in, few windows started to report the title and name, but the rest did not.

The apps inside the Automation section in privacy seem to be related but I've no idea on how I could add more apps manually to the list.

Opening some apps would give me a popup asking permission for Terminal to control the app, which seem to add it the list but I don't get that for every other app (Emacs for example)

#785 might be related here

Checking the logs it seems there are some permission error

Exception: jxa error: Error: Error: ActivityWatch is not allowed assistive access.
2022-09-10 15:47:19 [ERROR]: Exception thrown while trying to get active window  (aw_watcher_window.main:77)
Traceback (most recent call last):
  File "aw_watcher_window/main.py", line 74, in heartbeat_loop
  File "aw_watcher_window/lib.py", line 55, in get_current_window
  File "aw_watcher_window/lib.py", line 27, in get_current_window_macos
  File "aw_watcher_window/macos_jxa.py", line 64, in getInfo

But I already have ActivityWatch and aw-qt from the bundle in the accessibility list as mentioned in the #334 comment

use the old applescript method instead of jxa

This seems to work without error, but then the window titles are not reported unfortunately (which is a deal breaker for me)

Edit:
Also, this is a regression from v0.11.0 for me. As none of the steps in the #334 were required to run it and things would run normally. Only issues earlier was that it refused to launch normally and I had to do a open -a /Applications/ActivityWatch.app to run it and it had a low res icon. Everything else ran smoothly.

[kortschak]

I'm seeing the same behaviour after upgrade to v0.12.0. AFK watcher is working fine, window watcher has empty buckets. The comment linked at #334 above does not appear to be the issue in my instance.

I see similar errors in the window watcher log.

Reversion to v0.11.0 has not fixed things. There is now no dashboard content is served, but screen is blank. Clearing the browser cache fixes this.

[ErikBjare]

This will be fixed soon, see: #334 (comment)

[ErikBjare]

All issues mentioned here should have been fixed in the just released v0.12.1.

Please let me know if I can close this issue.

[ErikBjare]

From all I've heard from users, this issue has been resolved in v0.12.1.

Thanks for reporting!

[Gleek]

Unfortunately, v0.12.1 didn't work for me.
There are no errors in the logs now:

➜  ~ cat ~/Library/Logs/activitywatch/aw-watcher-window/aw-watcher-window_2022-09-28T16-39-12.log 
2022-09-28 16:39:12 [INFO ]: aw-watcher-window started  (aw_watcher_window.main:62)
2022-09-28 16:39:13 [INFO ]: Using swift strategy, calling out to swift binary  (aw_watcher_window.main:67)
2022-09-28 16:39:13 [INFO ]: Connection to aw-server established by aw-watcher-window  (aw_client.client:429)

But it seems that the afk-watcher-window is not running as seen from the ps output

➜  ~ ps aux|grep ActivityWatch|grep -v grep
umar              1424   0.4  0.5  5205432  81832   ??  S     4:38PM   0:04.11 /Applications/ActivityWatch.app/Contents/MacOS/aw-qt
umar              1436   0.3  0.3  4492020  47588   ??  S     4:38PM   0:01.61 /Applications/ActivityWatch.app/Contents/MacOS/aw-watcher-afk
umar              1434   0.0  0.3  4376404  43864   ??  S     4:38PM   0:01.29 /Applications/ActivityWatch.app/Contents/MacOS/aw-server

Running it manually would give the following error:

➜  ~ /Applications/ActivityWatch.app/Contents/MacOS/aw-watcher-window
 2022-09-28 16:44:17 [INFO ]: aw-watcher-window started  (aw_watcher_window.main:62)
usage: A cross platform window watcher for Activitywatch.
Supported on: Linux (X11), macOS and Windows.
       [-h] [--host HOST] [--port PORT] [--testing] [--exclude-title] [--verbose]
       [--poll-time POLL_TIME] [--strategy {jxa,applescript,swift}]
usage: A cross platform window watcher for Activitywatch.
Supported on: Linux (X11), macOS and Windows.
       [-h] [--host HOST] [--port PORT] [--testing] [--exclude-title] [--verbose]
       [--poll-time POLL_TIME] [--strategy {jxa,applescript,swift}]
A cross platform window watcher for Activitywatch.
Supported on: Linux (X11), macOS and Windows.: error: unrecognized arguments: -B -S -E -s -c from multiprocessing.resource_tracker import main;main(5)
A cross platform window watcher for Activitywatch.
Supported on: Linux (X11), macOS and Windows.: error: unrecognized arguments: --multiprocessing-fork tracker_fd=6 pipe_handle=8
2022-09-28 16:44:18 [INFO ]: Using swift strategy, calling out to swift binary  (aw_watcher_window.main:67)
dyld: Library not loaded: /usr/lib/swift/libswift_Concurrency.dylib
  Referenced from: /Applications/ActivityWatch.app/Contents/MacOS/aw_watcher_window/aw-watcher-window-macos
  Reason: image not found
2022-09-28 16:44:19 [INFO ]: Connection to aw-server established by aw-watcher-window  (aw_client.client:429)

Changing the method to jxa also doesn't work with the following logs

Exception: jxa error: Error: Error: An error occurred.
2022-09-28 16:49:36 [ERROR]: Exception thrown while trying to get active window  (aw_watcher_window.main:110)
Traceback (most recent call last):
  File "aw_watcher_window/main.py", line 107, in heartbeat_loop
  File "aw_watcher_window/lib.py", line 55, in get_current_window
  File "aw_watcher_window/lib.py", line 27, in get_current_window_macos
  File "aw_watcher_window/macos_jxa.py", line 64, in getInfo

I'm on macOS Big Sur (v11.6.1)

Any help is appreciated! Thanks :)

Edit: I also get an error pop-up, that I hadn't noticed before, everytime activitywatch opens up. There's no error in the details. But it's consistently crashing