Atrium 1.0.3

Nothing changes in the app itself. If you are on 1.0.2 there is no reason to
rush.

What this is for

These APKs are the first built by CI rather than by hand. That is what lets
F-Droid rebuild the same tag on their own machines, check the result matches
these files byte for byte, and then publish these signatures rather than
their own.

Which matters for one reason: today, an Atrium install from F-Droid and one from
this page would carry different signatures, and Android refuses to update across
a signature change. You would have to uninstall, losing your profiles, to move
between them. Reproducible builds remove that. It also has to be set up before
the first F-Droid publish, because once an app ships under F-Droid's key it can
never be moved to the developer's.

The F-Droid submission is still open and not yet merged.

For anyone building from source

A release build is now unsigned unless you supply your own
app/android/key.properties, where it used to fall back to the debug key. An
unsigned APK will not install. To try a release build without a key of your own:

flutter build apk --release -PdebugSignRelease=true

Debug builds are unaffected. The unsigned default is deliberate: F-Droid's check
copies the signature off the published APK onto their own build, which only
works if their build has no signature of its own.

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.