Seven modules, seven copies of the same Gradle block
Copy-pasted build config drifts silently per module. A convention plugin makes the shared part shared.
gradle
10 posts
A dependency that resolves in commonMain and only exists on Android
Gradle metadata decides which variant each target gets. A library with no native artifact fails at link, not at resolution.
A version catalog is a contract, and a transitive bump breaks it quietly
Declared versions are requests, not guarantees. Resolution picks the highest.
Source sets are a graph, and iosMain is not where you think it is
The default hierarchy creates intermediate source sets you never declared.
One Gradle build, five outputs, and the cache that only helps three
Android and JVM targets cache well. Native link steps mostly do not, and that asymmetry is where your CI time goes.
A task that captures Project is a bug, not a gap
Calling it a configuration cache incompatibility frames a real defect as a missing feature. The task captures a live object where it should capture a value.
A number in CI is the only budget that holds
A budget that lives in a shared understanding has already moved. A baseline works because changing it leaves a reviewable diff with somebody's name on it.
Thirty-six modules, one sync from deletion
Thirty-six fork modules were declared in a template-owned file that syncs by overwrite. The seam built for exactly this was present, documented and empty.
Killing the Gradle daemon costs you thirty minutes
Killing a build daemon discards the configuration cache, build cache, file watching and JIT state at once. Forty seconds becomes half an hour.
Compose has two version problems, and the BOM only solves one
The Compose BOM aligns runtime artifacts. The Kotlin/Compose compiler is a separate alignment problem, and mixing the two up produces errors that look like your code is wrong when it isn't.