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

Unresponsive stopwatch notification #179

Closed
3 tasks done
aaronsbytes opened this issue Sep 29, 2023 · 1 comment · Fixed by #297
Closed
3 tasks done

Unresponsive stopwatch notification #179

aaronsbytes opened this issue Sep 29, 2023 · 1 comment · Fixed by #297
Labels
bug Something isn't working

Comments

@aaronsbytes
Copy link

Steps to reproduce

  1. Open the latest ClockYou release
  2. Go to the stopwatch section
  3. Start the stopwatch
  4. Close the app

Expected behavior

The stopwatch should react to the button presses of the notification. Dismissing the notification should kill the background process.

Actual behavior

You will now find a notification of the stopwatch, which is unresponsive. It does not react to clicking the "stop" or "pause" button. Even if you dismiss the notification, the background process will still continue to run.

Clock You version

0.6.2

Android version

Android 13 / GrapheneOS

Other details

No response

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I will fill out all of the requested information in this form.
@aaronsbytes aaronsbytes added the bug Something isn't working label Sep 29, 2023
@CT-66
Copy link

CT-66 commented Dec 11, 2023

I've noticed the stopwatch notification displays options to stop and resume even after a stopwatch has been reset.

@SuhasDissa SuhasDissa linked a pull request Feb 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants