You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate.
Windows 10 Version 21H1 (OS Build 19044.1889):
ActivityWatch v0.12.0:
Describe the bug
I am getting this error "TypeError: Cannot read properties of undefined (reading 'value'). See dev console (F12) and/or server logs for more info." when changing Start of day from the default value which is "4 AM" to "12 AM".
To Reproduce
Steps to reproduce the behavior, for example:
1. Go to 'Settings'
2. Click on the little clock icon and change the value form "4 AM" to "12 AM"
3. See error
Expected behavior
I expect the value to change with no errors.
The text was updated successfully, but these errors were encountered:
Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏
I am getting a similar issue, except the undefined property is 'hide'. For me, this also sets the color of all categories in the Activity page to grey.
To reproduce this issue, do the following:
Go to 'Settings'
Change the category for ActivityWatch from Work>Programming>ActivityWatch to Uncategorized>ActivityWatch.
Describe the bug
I am getting this error "TypeError: Cannot read properties of undefined (reading 'value'). See dev console (F12) and/or server logs for more info." when changing Start of day from the default value which is "4 AM" to "12 AM".
To Reproduce
Steps to reproduce the behavior, for example:
1. Go to 'Settings'
2. Click on the little clock icon and change the value form "4 AM" to "12 AM"
3. See error
Expected behavior
I expect the value to change with no errors.
The text was updated successfully, but these errors were encountered: