[Clockify] "Timer could not be started"

Open Beginner friendly
#28,716 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start with the Clockify extension at https://www.raycast.com/isma/clockify and reproduce the failure using the listed Raycast and macOS versions. Inspect the start-new-timer command and its error handling, then verify that a timer starts when a workspace requiring a description is used.

Written by the indexing model from the issue text.

Description

bug extension extension: clockify platform: macOS
Extension

https://www.raycast.com/isma/clockify

Raycast Version

0.64.3.0

OS Version

macOS Tahoe 26.5.1 arm64

Description

Unable to use the "Time tracking" command

https://cln.sh/pkFhstJ5

Steps To Reproduce
  1. Start "Time Tracking" command
  2. Select "Start new timer"
  3. Add description (mandatory for my workspace, all other fields are left blank, but adding them does not change anything)
  4. Click "Start"
  5. See error
Current Behaviour

Error: "TImer could not be started"
Unfortunately does not allow me to generate a log

Expected Behaviour

Tracking starts

Dominant language
TypeScript
Stars
7.8k
Forks
6.9k
Avg merge
1d 23h
Merged PRs (30d)
450

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raycast/extensions

All issues in raycast/extensions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.