Archived
Running the app on a phone threw "No AlgorithmParameterSpec classes are supported" the first time anyone tapped Create account. Android's provider is Conscrypt, not the JDK's, and its XDH key-pair generator rejects every parameter spec while its key factory does not speak the XEC* specs at all — none of which the JVM suite could see, because it passes there. X25519 now goes through PKCS#8 and X.509 encodings, which both providers already speak. That also removes the RFC 7748 little-endian BigInteger conversion entirely, and with it a class of byte-order bug that produces plausible keys agreeing with nothing. An instrumented suite runs the published vectors on a device, so the next provider difference fails in CI rather than in someone's hands. Three consequences worth stating plainly: minSdk is 33, not 26. Android exposes XDH from API 33; below that a provider has to be registered at startup and nothing here does that, so claiming 26 was claiming something untrue. Cleartext is refused with a reason rather than failing as an unexplained connection error. Bearer tokens ride every request, so a plain-http server would put an account on a café network. material-icons-extended is gone. It generates a class per icon and added 44 MB of dex for the five glyphs this app uses; three hand-written vector paths replace it.