Paul HittandClaude Opus 5
77ca69b327
Five things were wrong, each hidden behind the one in front of it, and none of them was the app. Sign-up works: the run that finally got through created `andt34972750` on relay1 and registered a device, and the Account screen showed both. 1. The emulator still had a RELEASE-signed build on it, so the debug test APK could not install: INSTALL_FAILED_UPDATE_INCOMPATIBLE. Zero tests ran. The uninstall lived only in the "emulator already up" branch, on the reasoning that a cold boot starts clean. A cold boot starts with no snapshot; the disk image keeps what was installed. The script already PRINTED the leftover package and carried on, which is a check nobody acts on. It now clears on both paths and refuses to continue if anything is left. 2. The sign-in form scrolls, and `toggle-register` is below the fold. A tap aimed off-screen is not an error in Compose, it simply does not happen, so the form stayed on sign-in and the test waited thirty seconds for a register-only field. Same for `sign-out`, which is the last section of a long Account screen. 3. It waited for `device-id` after sign-up. Sign-up lands on Home and `device-id` is on Account, so it waited two minutes on a screen that was never going to show it and reported that the app had not signed in. It had: the dump said "Nobody here yet. Add someone by the username they signed up with", which is the empty contact list of an account created seconds earlier. It now waits for the nav pill and checks the device id on the screen that has it. 4. `performTextInput` appends, and only the relay field was cleared, so the second test in the class typed "19901990" into the age gate. Submit is enabled on exactly four digits, a disabled button swallows a tap, and the wait then blamed a screen the tap never reached. The same shape as the age-gate bug this suite was fixed for once already. `signingOutReturnsToSignIn` now passes, against a real relay, which it has not done in a long time. The remaining failure is not a test problem and is filed separately: creating a second account after signing out is refused with "Your session expired", because `signOut` clears the session in memory and leaves the stored credential on disk. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Flamenet Messenger. Android
The Android app, and the two libraries under it. The product's site is at https://flamenetmessenger.com.
engine/ the protocol: X3DH, Double Ratchet, sealed sender, safety numbers,
key transparency. Plain Kotlin/JVM — no Android in it at all.
client/ the relay transport: HTTP, auth, the §8 routes.
app/ the Compose app.
interop/ the cross-engine driver; not shipped.
engine and client are deliberately plain JVM libraries. The protocol has
nothing to do with Android, and keeping it off the platform means their tests
run anywhere a JVM does, no SDK, no emulator, no device, which is also what
lets them gate in CI on Linux:
./gradlew :engine:test :client:test
The app's own unit tests need the Android SDK but still no emulator (Robolectric):
./gradlew :app:testDebugUnitTest
Where it stands
PARITY.md is the definition of done for this app, read that, not this. Every row there names the iOS file it came from so it can be re-checked rather than trusted. Headlines: messaging, groups, attachments, voice notes, stories, calls, sealed sender, key transparency and the encrypted vault are built and tested, and a cross-platform round trip against iOS is verified.
If a claim here ever disagrees with PARITY.md or with the tree, believe those, and fix this.
Why the engine came first, and is held to the vectors
An Android client needs the protocol implemented a third time, and the third
implementation is the one that finds the places where the specification says
less than the two existing engines quietly agreed on, but only if it is
written against the spec and the published vectors rather than against a
reading of our own Swift and JavaScript. So the engine is held to
test/vectors/protocol-v1.json in
flamenet-e2e, the same file the
other two engines are checked against, read from that repository rather than
copied here, because a copied vector file drifts and a drifting vector file
stops being a check. PublishedVectorsTest looks for it beside this checkout
and fails loudly if it cannot find it; FLAMENET_VECTORS overrides the search.
Two implementations that agree may both be wrong in the same way, especially when one was written while reading the other. The audit-path ordering in §19 is the worked example: a top-down reading of a bottom-up path produces the correct root for every left-spine index, so it passes any test that only checks index 0. The vector file pins a right-descending index for that reason, and the Kotlin tests assert both that the published path verifies and that the same path reversed does not.
If this engine ever disagrees with the file, the interesting question is which of the three is wrong, not this one by default.
Contributing and security
- CONTRIBUTING.md, building (JDK 21,
JAVA_HOMEis not optional on a Mac), the test gate, and the platform traps that cost an hour each. - PARITY.md, what iOS does, what this does, and what is left. It is the definition of done for this app.
- SECURITY.md, threat model and where to send a vulnerability report. Not an issue tracker matter: security@flamenetmessenger.com.