BelKed

It was fixed a while ago in https://github.com/ActivityWatch/aw-webui/pull/493 and released in [`v0.12.3b11`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b11). Installing [`v0.12.3b11`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b11) or [newer](https://github.com/ActivityWatch/activitywatch/releases) would solve the problem :)

I'm using [`v0.12.3b15`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b15) and I can see requests to `localhost:5600/api/0/settings` endpoint Just to note, [`v0.12.3b16`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b16) has some bugs; I would recommend downgrading to [`v0.12.3b15`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b15) if you're using [`v0.12.3b16`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b16) :)

It was fixed in https://github.com/ActivityWatch/aw-webui/pull/573 and the fix was released in [`v0.12.3b19`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b19). I have personally tested this version and can confirm that the behaviour from this issue is no longer...

Yup, there have been some minor changes to the web UI :) By the way, since the problem is fixed, feel free to close this issue ;)

There seems to be some problem with the latest beta version — see https://github.com/orgs/ActivityWatch/discussions/1005 :)

Could you please try the latest beta version ([`v0.12.3b15`](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b15)) to verify if the issue still occurs there?

There is a problem with `v0.12.3b16` which I can confirm. Please use `v0.12.3b15` in the meantime :)

Good observation :) It happens because the date in the URL is changed to `Invalid date` (at least in Firefox). For example: `http://localhost:5600/#/activity/BelKed/day/Invalid date/view/summary`

Would you mind trying the [latest beta](https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b12) to see if the problem still exists there? :)

I can reproduce this issue on my installation... Probably it's related to https://github.com/ActivityWatch/activitywatch/issues/724. ---