Skip to content
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

[Fix] Error in Timer due to Missing Last Screenshot #8360

Closed
adkif opened this issue Oct 8, 2024 · 0 comments · Fixed by #8448
Closed

[Fix] Error in Timer due to Missing Last Screenshot #8360

adkif opened this issue Oct 8, 2024 · 0 comments · Fixed by #8448

Comments

@adkif
Copy link
Contributor

adkif commented Oct 8, 2024

Description:

Errors are occurring in the timer when it attempts to display the last screenshot. This issue arises when time intervals and screenshots have been removed in the Gauzy UI, but the timer is still trying to use locally stored information.

To reproduce:

  1. A user tracks time, and the timer shows the last screenshot.
  2. The user closes the timer.
  3. The user removes time intervals/screenshots from the Gauzy UI.
  4. The user starts the timer again.
  5. The timer shows an error while loading the screenshot because it no longer exists.

Expected Fix:

  • Before displaying any screenshots, the timer should make an API call to the Gauzy server to retrieve the last worked interval and screenshot.
  • The timer should no longer rely on local data for the last screenshot after restarting.

Steps to Implement:

  1. Ensure that the timer makes an API call to fetch the last worked interval and screenshot when it starts.
  2. Display the retrieved screenshot in the timer, or handle the case where no screenshot exists.
  3. Ensure no local screenshot data is used if the user removed intervals/screenshots.

Additional Information:

  • This fix will prevent errors when the last interval or screenshot has been deleted from the Gauzy UI but is still referenced locally by the timer.

Resolves #8348

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant