Repository navigation
One small fix to the log. No change to how the app connects or forwards; no new settings or permissions.
A mesh relay's access token is no longer logged
If you have set a relay under Settings → Mesh relays for public names, the app reaches it through a local address that carries a random access token. The relay library wrote that address, token included, into the log (for example Connected to 'ws://127.0.0.1:…').
The token is new at every connect and only works on the phone itself, so a log you shared gave nobody access. It still does not belong in a log that is meant to be copied and sent to someone. It is now shown as <token>, at every log level, in the in-app log and in the system log.
Installing over 0.10.3 keeps identity and settings.
Checked with this release's APKs on a Pixel 9 Pro (arm64, installed over 0.10.3) and on an x86_64 emulator, each with a mesh relay set: after connecting, the log shows the relay's address with <token> and no token. The 32-bit ARM build was built and checked in CI but has not run on hardware for this release.
Which APK
Most phones: fips-android-v0.10.4-arm64-v8a.apk. If you are unsure, -universal.apk carries all three ABIs for a first install; the in-app updater picks the per-ABI APK.
Signing
Release certificate SHA-256: aa905e32bd0058874d252990abba26c78ddd8fca018195ebd1cd232a99a7a8e1