The duration statistics of Activity usage are incorrect.
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 Android Activity onStart and onStop handling and reproduce rapid switches from activityA to activityB and back. Done means duration statistics and foreground/background switch detection remain correct during rapid Activity changes.
Written by the indexing model from the issue text.
Description
Translate the following sentence into English: "Activity usage duration statistics are performed in onStart and onStop. However, the statistics are incorrect when the Activity switches rapidly. For example, from activityA to activityB, then quickly back to activityA. This scenario can also lead to incorrect determination of foreground and background switches."
- Dominant language
- Java
- Stars
- 696
- Forks
- 290
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 Countly/countly-sdk-android
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Countly/countly-sdk-android#511 · 5 comments ·
Maintainers usually reply within 1 day
All issues in Countly/countly-sdk-android
Similar issues
-
False Negative: InnerTypeLastCheck does not report members declared after inner enums or annotationsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
checkstyle/checkstyle#22027 ·
Maintainers usually reply within 1 day
-
bug follow-up lane:auto
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Sanne/incus-spawn#1497 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
[BUG][RUST] chrono date-time path/query/header params are not serialized as RFC 3339Possibly taken @teovillanueva claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenAPITools/openapi-generator#25297 ·
Maintainers usually reply within 1 day
-
[CI] NettyClientTest.testServerDisconnection may fail with DisconnectExceptionPossibly taken @yangshangqing95 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day