Vitor PamplonaandClaude Opus 5
a2f60eeeaf
v1.15.0 was tagged but never shipped. Its `Create Release Assets` run failed in
`deploy-android` at the first packaging task:
Execution failed for task ':amethyst:buildFdroidReleasePreBundle'
> Entry name contains invalid characters:
root/META-INF/zoomable-root:zoomable.kotlin_module
so no AAB, no APK, and none of the 47 assets were produced.
A `.kotlin_module` is named after the Gradle project path that produced it,
colons included. 14 of the 98 modules merged into the app carry one: zoomable,
Negentropy, vico, the seven coil3 artifacts, and four of ours -- Amethyst:quartz,
Amethyst:commons, Amethyst:quic and Amethyst:nestsClient -- so renaming our own
would not have been enough.
Bisected against the two toolchain bumps this cycle, since both landed after the
last good release: AGP 9.3.1 -> 9.4.0 and Kotlin 2.4.10 -> 2.4.20. With Kotlin
held at 2.4.20 and AGP reverted, both flavours' bundle tasks pass, so Kotlin is
not the trigger. The R8 output jar carries the identical 14 colon entries under
BOTH AGP versions -- 9.4.0 added the rejection rather than the names, in
JarFlinger.addJar, reached from PerModuleBundleTask.addHybridFolder.
`packaging.resources.excludes` was tried first and cannot work, at either
`META-INF/*.kotlin_module` or `**/*.kotlin_module`: with minification on, R8
emits the java resources itself and addHybridFolder hands JarFlinger its own
predicate, so those filters are never consulted. Confirmed by deleting the R8
output and re-running rather than reading a stale intermediate --
mergeJavaResource's jar holds zero kotlin_modules while R8's holds all 98.
So the entries are stripped from R8's jar in the moment before the bundle task
opens it, and the jar is put back exactly as R8 left it afterwards. Two details
carry their weight:
- the strip is doFirst on the CONSUMER rather than doLast on R8, so a
build-cache hit on R8 cannot skip it;
- the restore is what keeps R8 up to date. Without it Gradle sees a modified
output and re-runs R8 on every build -- measured here at ~2 min for an
otherwise no-op build. With it, a second run reports
minifyFdroidReleaseWithR8 UP-TO-DATE and finishes in 1s.
Pinning back to 9.3.1 was the alternative and is one line away; the catalog
comment records that, and says to drop the workaround when AGP fixes it.
Verified from a cleaned R8 output on both flavours:
buildFdroidReleasePreBundle and buildPlayReleasePreBundle both BUILD SUCCESSFUL,
each reporting "Stripped 14 colon-named entries from base.jar".
appCode 458 -> 459. RELEASE_NOTES_ID deliberately stays on the v1.15.0 note:
RELEASE_OPS has it repointed on x.y.0 only, and 1.15.1 ships that release's
contents.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgVDQQXAg4cmzsWHoJj61k
1.4 KiB
v1.15.1: Release Build Fix
v1.15.0 was tagged but never shipped: its Create Release Assets run failed in
deploy-android before producing a single artifact. This release carries the
whole of v1.15.0 plus the fix for that failure — read those notes
for what actually changed in the app.
Build
-
Strips colon-named
.kotlin_moduleentries out of R8's java-resource jar before the app bundle is written. AGP 9.4.0 refuses them:Execution failed for task ':amethyst:buildFdroidReleasePreBundle' > Entry name contains invalid characters: root/META-INF/zoomable-root:zoomable.kotlin_moduleA
.kotlin_moduleis named after the Gradle project path that produced it, colons included, and 14 of the 98 modules merged into the app carry one — zoomable, Negentropy, vico, seven coil3 artifacts, and four of ours (Amethyst:quartz,:commons,:quic,:nestsClient). The entries are byte-identical under AGP 9.3.1, which writes the bundle without complaint, so 9.4.0 added the rejection rather than the names.packaging.resources.excludescannot remove them — with minification on, R8 emits the java resources andPerModuleBundleTaskhandsJarFlingerits own predicate, so those filters are never consulted. Nothing reads a.kotlin_moduleout of an installed app either; the file exists for the Kotlin compiler to resolve top-level declarations across modules at compile time.