Stopwatch continues running after stopped
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the Stopwatch feature's stop event from the Android view lifecycle to the rust-backend, focusing on what happens when the view is closed or another app is opened. Reproduce the reported start, stop, close, and reopen sequence, then verify that a stopped stopwatch remains stopped after app termination, reopening ActivityWatch, and switching apps.
Written by the indexing model from the issue text.
Description
I have encountered a bug in the "Stopwatch" feature. It sometimes restarts a stopwatch, after I already stopped it.
I assume that this happens when the view is closed/terminated, before the "stop event" (or whatever the correct term is) is sent to the rust-backend. The best method I found to reproduce is:
- Start a stopwatch
- Let the stopwatch run for some time
- Stop the stopwatch
- Close the view manually, by using the "overview" button of the phone and closing the app
- Re-open activitywatch
- The stopwatch runs again
This does not trigger the bug 100%, so I would assume that there is some racing condition or the operation takes some time. My assumptions would have been that after pressing stop, the termination is directly "committed", but this does not seem to be the case.
The bug also happens, when I don't close the view manually, just by switching to another app.
ActivityWatch: v.0.10.0 (rust) (Installed over Google playstore)
Android: 8.0.0 (Samsung Galaxy S7)
- Dominant language
- Kotlin
- Stars
- 270
- Forks
- 57
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 38
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ActivityWatch/aw-android
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ActivityWatch/aw-android#306 ·
Maintainers usually reply within 1 day
-
AuthSettingsActivity crashes on launch (InflateException: Material attributes under AppCompat theme)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ActivityWatch/aw-android#210 · 7 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ActivityWatch/aw-android#302 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
ActivityWatch/aw-android#300 · 6 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ActivityWatch/aw-android#296 ·
Maintainers usually reply within 1 day
All issues in ActivityWatch/aw-android
Similar issues
-
OAI-PMH
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
TeamAmaze/AmazeFileManager#4731 ·
-
Bug Needs review
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
breezy-weather/breezy-weather#2978 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AAswordman/Operit#1292 ·
Maintainers usually reply within 1 day