[Tyme 3 Time Tracker] ... Something went wrong - loading tasks

[hazardawareness]

Extension

https://www.raycast.com/melkstam/tyme-3-time-tracker

Raycast Version

1.83.2

macOS Version

15.0.1

Description

Error:

TypeError: Cannot read properties of undefined (reading 'name')

t0:start-task-tracking.tsx:13:70

---
10: 
11: function StartTrackerForTask() {
12:   // Get all tasks
13:   const { data: tasks, isLoading: tasksIsLoading } = useCachedPromise(getTasks, [], {
14:     keepPreviousData: true,
15:   })

### Steps To Reproduce

Open Raycast - Select Start Task - error

### Current Behaviour

_No response_

### Expected Behaviour

_No response_

[raycastbot]

Thank you for opening this issue!

🔔 @melkstam you might want to have a look.

💡 Author and Contributors commands

The author and contributors of `melkstam/tyme-3-time-tracker` can trigger bot actions by commenting: - `@raycastbot close this issue` Closes the issue. - `@raycastbot close as not planned` Closes the issue as not planned. - `@raycastbot rename this issue to "Awesome new title"` Renames the issue. - `@raycastbot reopen this issue` Reopens the issue. - `@raycastbot assign me` Assigns yourself to the issue. - `@raycastbot good first issue` Adds the "Good first issue" label to the issue. - `@raycastbot keep this issue open` Make sure the issue won't go stale and will be kept open by the bot.

[melkstam]

Hi and thanks for the report @hazardawareness!

I've sadly seen this before but I have a hard time reproducing this. This has also been reported in https://github.com/raycast/extensions/issues/10249.

Do you have any more any context about when this happened?

[hazardawareness]

@melkstam thanks. It happened directly after a tyme update so I assumed it was something to do with a change there but as you said it was isolated I tried to uninstall and then reinstall the extension and it fixed the issue.

Love the extension, use it every day. Next time this happens I'll see if I can debug exactly what might be causing it but uninstalling then reinstalling seemed to do the trick. Tried restarting, safe mode, quitting apps, etc before all that and nothing else helped.

[melkstam]

@melkstam thanks. It happened directly after a tyme update so I assumed it was something to do with a change there but as you said it was isolated I tried to uninstall and then reinstall the extension and it fixed the issue.

Love the extension, use it every day. Next time this happens I'll see if I can debug exactly what might be causing it but uninstalling then reinstalling seemed to do the trick. Tried restarting, safe mode, quitting apps, etc before all that and nothing else helped.

Thanks! I will continue to try reproducing the issue. I'm glad you like the extension!