BUG: Timetracks lost after start it
Closed this issue · 4 comments
I had it now multiple times, but can't 100% reproduce it.
From time to time I do the general way to start a timetrack... fill all the fields an click Enter (or with Mouse on Button Start).
Then the screen switch back to the overview.
Now there should be a red-button with the elapsed time... means the timetracker start to track the times.
But in some cases, there is nothing at all. Only the Input-Field to start a new timetrack.
Happend multiple times now, so I filled this bug.
Is there a way to activate Developer-Console to see what's going wrong in this cases?
Not sure, but it might be the case, if you don't explicit choose the Customer and Project but use the pre-setting that was made if tab was open?!?
mhh no, it's not the issue.
But today I have many trouble to start tasks. I currently have to do some tasks in a row (each task round about 5 - 10 Minutes).. and I found, that i nedd up to 5 times enter the new Timeentry to get it work once.
I use the newest version of the app v1.0.9
Hi,
I'm sorry about issues, you actually have. Can you please check, if task start in Kimai?
If starts, try open some task in CodeTimer and go back to main page.
If active task appears, that means CodeTimer need some delay to check active tasks.
If not starts in Kimai, maybe there is problem with description or connection to Kimai server.
Developer console can be opened with argument --window-enable-inspector.
If you are using Linux, go to app directory, open terminal and run command ./CodeTimer-linux_x64 --window-enable-inspector.
I've tried what you suggest and found that it also wasn't started at kimai.
If I try to start codeTimer with the inspector-parameter, application doesn't work anymore:
On CLI I got this message too:
(process:33537): GLib-CRITICAL **: 09:58:50.647: g_uri_get_scheme: assertion 'uri != NULL' failed
But this also happend if I start it from console (cli) without the parameters. Only if I start it from KDE it seems to work.
But here the error-logs from dev-console (as I've inject the parameters to the KDE-Starter):
Hmm interesting.
Are you sure, you can access Kimai server? Maybe is problem with SSL protocol, because in summary is https, but in request/response is only http.