Repository navigation
Nightbell 3.0.3: reproducible, and signed with my key
No code changes. This release exists so F-Droid can reproduce the build and ship the APK signed with my own key instead of theirs.
Why a release with no changes in it
F-Droid can publish an app one of two ways. Either they build it and sign it with the F-Droid key, or they build it, confirm their result is identical to the APK I published, and then ship mine with my signature on it. The second one is what lets you move between the GitHub download and the F-Droid listing without uninstalling, and it is not a decision that can be revisited: an app published under their key stays under their key.
Their check builds from source in their container and compares the result against the APK attached to the release, file by file. Against 3.0.2 it failed on two of the 148 files: classes.dex and assets/dexopt/baseline.prof.
One cause, not two
Their container runs openjdk 21.0.12+8. 3.0.2 was built here on 21.0.11+10. A different JDK hands R8 a different dex, and the baseline profile is compiled out of app/src/main/baselineProfiles/*.txt into dex method indices, so once the dex moves the profile moves with it. baseline.profm carries no indices and was identical throughout, which is the tell that this was one problem wearing two hats.
Checked rather than assumed, in two steps:
- Building the v3.0.2 tree on both JDKs gives two different
classes.dex, so the JDK is genuinely the variable and not a guess. - Their failed job uploads its own build as an artifact, so that build could be fetched and compared against a local one on the matched JDK. All 148 files identical, including the two that had differed.
The whole-APK hash still differs between any two builds, because zip metadata is not content. That is why the comparison is per-file.
One more file had to be dealt with after the JDK: META-INF/version-control-info.textproto, which AGP fills with the git revision the build came from. The first APK attached here was built a moment before the release commit existed, so it recorded the previous revision and nothing else in the APK differed at all. Rebuilt at the tagged commit, all 148 files match their container's output.
What this means for later releases
The matching JDK is a standing constraint now, not a one-off. Any future release whose APK is built on a different JDK will fail verification, and the failure is quiet: the app keeps working and simply stops being reproducible. The note lives in app/build.gradle.kts next to the version.
Updating
Same signing key as 3.0.1 and 3.0.2, so 3.0.2 updates in place. Coming from 3.0.0 still needs an uninstall first, because 3.0.1 changed the key. Coming from Pulse 2.x still needs export and import, because 3.0.0 moved the package.
If you are already on 3.0.2 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.3-release.apk 2,160,440 bytes
sha256 2340bb6126b70996e82fbb35e2f6a4f4e1cfb1841b27dd4def395f6761167866