Atrium 1.0.4
Nothing changes in the app itself. If you are on 1.0.3 there is no reason to
update.
What this fixes
F-Droid verifies a release by rebuilding it on their own machines and checking
the result against the published APK. Their rebuild of 1.0.3 came out 20 bytes
different, out of 25 MB, and nothing else: a fingerprint the compiler stamps
into one library, derived from where the build tools happened to live on disk.
The path itself never reaches the APK, but that fingerprint does.
The build now uses the same tool locations F-Droid does, and their rebuild
matches byte for byte.
Why it is worth a release
Once this works, F-Droid can ship APKs carrying this signature instead of
their own. Without it, an Atrium install from F-Droid and one from this page have
different signatures, and Android refuses to update across a signature change:
you would have to uninstall, losing your profiles, to move between them.
It also cannot be added later. Once an app ships under F-Droid's key, it stays
under F-Droid's key.
The F-Droid submission is still open and not yet merged.
Which APK
Most phones want app-arm64-v8a-release.apk. Use armeabi-v7a for older
32-bit devices, and x86_64 only for emulators and Chromebooks. Android 7.0
(API 24) or newer.
Same key as every release so far, so this installs as a normal update.
apksigner verify --print-certs should report:
5ebad1ff2f9cdc63f28b364addf9e858330db26909d9eba8dfbccb998de37351
Free software under the GPL-3.0-or-later.