Jean-Luc Makiola
5c80f99179
All checks were successful
CI / ci (pull_request) Successful in 5m57s
F-Droid's binary scanner (the fdroiddata `check apk` job) rejects any
"extra signing block". Our release APK carried AGP's dependency-metadata
block (id 0x504b4453, ~8 KB) in the APK Signing Block. Disable it with
`dependenciesInfo { includeInApk = false; includeInBundle = false }`.
The block lives in the signing block, not the zip entries, so removing it
changes no build output — v2.7.5 is functionally identical to 2.7.4 and
still reproduces byte-for-byte. Verified locally: a releaseTest build now
carries only the v2 signature + verity padding (no 0x504b4453 block).
This was the last F-Droid blocker: v2.7.5 now clears vcsInfo (since 2.7.3),
foojay (since 2.7.4) and the dependency-metadata block. Bumps versionName
to 2.7.5 and retargets the official recipe draft at v2.7.5.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
7 lines
327 B
Plaintext
7 lines
327 B
Plaintext
### Changed
|
|
- Further build cleanup for the official F-Droid repository: stopped embedding
|
|
AGP's dependency-metadata block in the APK, which F-Droid's reproducible-build
|
|
scanner rejects as an extra signing block. No functional or visible changes —
|
|
the same app as 2.7.4, just without that Play-oriented metadata blob.
|
|
|