Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`androidCompileSdkExtension = "-"` silently becomes null, hiding the intended SDK extension level

Open Beginner friendly
#20 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
kotlin
Domain
build-system

Research direction

Start with gradle/libs.versions.toml:6 and follow androidCompileSdkExtension into ConfigureKotlinAndroid.kt. Confirm how the placeholder is parsed and whether it is overridden elsewhere. Done means the catalog and consumer express an explicit SDK-extension intent without silently converting the value to null.

Written by the indexing model from the issue text.

Description

good first issue

androidCompileSdkExtension = "-" silently becomes null, hiding the intended SDK extension level

Severity: Low
File: gradle/libs.versions.toml:6

The version catalog declares:

androidCompileSdkExtension = "-"

In ConfigureKotlinAndroid.kt this is consumed as:

compileSdkExtension = libs.versions.androidCompileSdkExtension.get().toIntOrNull()

"-".toIntOrNull() returns null, so compileSdkExtension is silently unset. This looks like a leftover placeholder from when the project targeted a specific extension level (e.g. "13" for Android 13 Tiramisu extension). It is never overridden anywhere, so the build silently uses no extension.

Why it matters

If a future AGP or platform release requires a specific SDK extension level for new APIs, the build will silently fall back to the base compileSdk rather than failing loudly. The "-" value communicates no intent — it should either be removed (letting the extension stay unset explicitly) or set to the actual desired value.

Dominant language
Kotlin
Stars
402
Forks
60
Avg merge
4h 8m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wangzhishou/OneBox

All issues in wangzhishou/OneBox

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.