You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
A user tracks time, and the timer shows the last screenshot.
The user closes the timer.
The user removes time intervals/screenshots from the Gauzy UI.
The user starts the timer again.
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:
Ensure that the timer makes an API call to fetch the last worked interval and screenshot when it starts.
Display the retrieved screenshot in the timer, or handle the case where no screenshot exists.
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.
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:
Expected Fix:
Steps to Implement:
Additional Information:
Resolves #8348
The text was updated successfully, but these errors were encountered: