Closed mstarke closed 9 years ago
It seems that the "error" is still reproduceable:
Result is a newly started timer with no start date.
i couldn't reproduce, but i think i found the problem while fixing #177. Should be gone now and this time finally. Maybe. ;)
Sometimes when quickly stopping and starting a tracker, the newly created tracker doesn't have a start date set and hence is unusable. Only solution right now is to manually set the started_on entry in the database.