-
-
Notifications
You must be signed in to change notification settings - Fork 541
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
aw-server-rust gives 404 when run from .app
on macOS
#441
Comments
Thanks for the descriptive report!
|
@mpeteuil did you try a hard refresh to the page? I had the same issue on Linux and that fixed it for me |
Thanks for the suggestion @nicolae-stroncea, unfortunately refreshing the page does not resolve the issue. This seems to be a routing problem. |
@mpeteuil It has now been fixed, the changes will be in the next release (v0.10) |
.app
on macOS
I am on the latest ActivityWatch version.
I have searched the issues of this repo and believe that this is not a duplicate.
OS version and name: MacOS Mojave 10.14.6
ActivityWatch version: 0.9.2
Describe the bug
Switching on
aw-server-rust
and turning offaw-server
seems to result in some of the dashboard (WebUI) functionality missing. I have verified thataw-server-rust
is running sincehttp://localhost:5600/api/0/buckets/
actually returns what you would expect when it's on.To Reproduce
.app
to theApplications
directoryaw-server
by opening the tray icon > modules and clickingaw-server
.aw-server-rust
by opening the tray icon > modules and clickingaw-server-rust
.{"reason":"Resource was not found.","status":404}
Expected behavior
The expectation is that reloading the WebUI after switching to
aw-server-rust
in step 8 would give the same result as theaw-server
running in step 5.Documentation
Here's a bit from the
aw-server-rust
logs:The
No matching routes for OPTIONS
message is most of the log file as you might expect with it being a heartbeat.Additional context
If there's more that could be helpful let me know and I'll add it.
The text was updated successfully, but these errors were encountered: