A build release. The clock is unchanged from 0.2.3.
The release APK is now signed without re-aligning the archive. apksigner from build-tools 35 rearranges an APK while signing unless told not to, and the v2/v3 signatures cover the whole archive — so the signature no longer fitted a rebuild of the same source, and the check F-Droid runs to confirm a reproducible build failed with a CHUNKED_SHA256 mismatch. build-tools 34 preserved alignment by default, which is why this only appeared after the toolchain moved.
The build was never the problem: the pre-signature artifacts from two different machines were byte-identical throughout. Only signing rearranged things.
There is now a test that performs the whole transfer — build a release, rebuild unsigned, copy the signature across, verify — so this cannot come back quietly.
SHA-256 of reteclock-0.2.4.apk:
9f37d77d6b22ce14789ca8791f58a7eddbb3935f9fc362f9fb7d5873538966c3
Installs on Android 2.3 and newer. Built and verified against Android 4.4 (API 19).