Target API level 29
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
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.
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.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100