Timer sometimes freezes

[bozhkov1]

You click on the tomato in order to start timer but it stays at the same minutes remaining forever until prompted again

[schmich]

I have seen this problem a couple of times. I think it might be related to #163.

It would be good to get more information on this, if possible. If you hit this issue again, can you check the logs and send me anything you see there (errors, debug information, ...)? See this short video on how you can access the extension's logs.

I will look into fixing #163 as well since it might be related to the issue you're seeing.

[bozhkov1]

i just found it out, if you close the browser , the timer freezes until restart

…

On Feb 19, 2018 8:51 PM, "Chris Schmich" ***@***.***> wrote: I have seen this problem a couple of times. I think it might be related to #163 <#163>. It would be good to get more information on this, if possible. If you hit this issue again, can you check the logs and send me anything you see there (errors, debug information, ...)? See this short video <https://i.imgur.com/2ivV7b4.gifv> on how you can access the extension's logs. I will look into fixing #163 <#163> as well since it might be related to the issue you're seeing. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Af2SgX4WYMtHoLnhNuE2nFqMpdW6kDZFks5tWdCsgaJpZM4SJ4PA> .

[schmich]

Thanks for the details. Yes, that is exactly the same behavior as #163.

It's an unfortunate problem. The timer runs inside of Chrome, so it relies on Chrome being open. There might be some way to keep the timer running in the background. I will have to investigate further.

For now, the workaround is to keep at least one Chrome window open.

[bozhkov1]

what i can think of is caching the timer parameters in some Temp folder in chrome , thus removing the freezing problem, but you still have to have chrome open , i think it is possible to have push notifications from an app in chrome even when closed , you should research that

…

On Feb 19, 2018 11:12 PM, "Chris Schmich" ***@***.***> wrote: Thanks for the details. Yes, that is exactly behavior as #163 <#163>. It's an unfortunate problem. The timer runs inside of Chrome, so it relies on Chrome being open. There *might* be some way to keep the timer running in the background. I will have to investigate further. For now, the workaround is to keep at least one Chrome window open. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Af2SgW0ayVwQtY3z_fcBHyvOKMIYBgZ4ks5tWfHbgaJpZM4SJ4PA> .