Target API level 29
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system, mobile
Research direction
No file or test is named in the issue. Start by locating the Android build configuration that sets the library's current target API level of 27, then check the project's build and compatibility requirements. Done means the target level is updated to 29 and the project still builds successfully.
Written by the indexing model from the issue text.
Description
Hi,
Is there a reason for not targeting the API level 29?
We've experienced a problem with Samsung devices where the clock was behaving strangely (Felt like displaying random times). I tried to make detailed logging by forking the library and adding the modules to our project. Then we realized that we couldn't get the logs from Samsung device with API level 29. I only managed the logs working by targeting API level 29. We are still not sure if the original problem is solved of course.
There I was wondering why the library is targeting API level 27 and whether we can do anything about it or not.
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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 lyft/Kronos-Android
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lyft/Kronos-Android#67 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lyft/Kronos-Android#66 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
lyft/Kronos-Android#65 ·
-
Wrong TimeOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lyft/Kronos-Android#62 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
lyft/Kronos-Android#61 · 10 comments · 2 reactions ·
All issues in lyft/Kronos-Android
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
fwcd/tree-sitter-kotlin#289 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
navikt/syfo-oppfolgingsplan-backend#482 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
MorphiaOrg/morphia#4332 ·
Maintainers usually reply within 1 day