Skip to content

Nightbell 3.0.4: no Play dependency blob in the signing block

Choose a tag to compare

@riveerxd riveerxd released this 10 Aug 21:43
· 194 commits to master since this release

No code changes. Like 3.0.3, this exists so F-Droid can publish the app signed with my key instead of theirs.

What was in the way this time

Android Gradle Plugin writes a Dependency metadata block into the APK signing block by default, 6,486 bytes of it here, so that Google Play can report on the libraries a build pulled in. This app is not on Play.

F-Droid's APK scan raises it as CRITICAL: found extra signing block 'Dependency metadata'. That is a fair call. A signing block no tool outside Google can read is a blob nobody reviewing the app can account for. The scan runs against the published APK, so it is not optional for a release meant to go there.

dependenciesInfo { includeInApk = false }, and the same for the bundle this project does not build. Checked by parsing the signing block rather than trusting the setting:

before after
APK Signature Scheme v2 2,551 B 2,551 B
Dependency metadata 6,486 B gone
padding 3,195 B 1,497 B

Why not just rebuild 3.0.3

Because the blob lives or dies by a build setting, and the setting is source. F-Droid builds the tag, so a tag without dependenciesInfo produces an APK with the blob regardless of what is attached to the release.

Moving the v3.0.3 tag was the other option, and it breaks the thing 3.0.3 was for: the APK records the git revision it was built at, and that revision has to be the tag's own commit.

Releasing this app has three constraints now

Each of them fails quietly. The app keeps working and simply stops being reproducible, at which point F-Droid signs with their key and that cannot be undone later.

  1. Build on the JDK F-Droid's buildserver runs. Currently openjdk 21.0.12.
  2. Commit the version bump before building the APK, so the recorded revision is the release commit rather than the one before it.
  3. Ship no signing block beyond the signature.

All three are written next to the version in app/build.gradle.kts.

Updating

Same signing key as 3.0.1 through 3.0.3, so 3.0.3 updates in place. Coming from 3.0.0 still needs an uninstall first. Coming from Pulse 2.x still needs export and import.

If you are already on 3.0.3 there is nothing in here for you.

Verified

359 JVM tests and 173 on-device tests. minSdk 26 (Android 8.0), targetSdk 36.

Nightbell-3.0.4-release.apk 2,152,244 bytes
sha256 3c0536468cb9fc6c7e1bec22b9a04e9defbd0d9e42fe408b84b6e9756ff8b2c9