The iOS app could not sign up against a Swift relay at all. Sign-up died on a
bare "Server returned HTTP 404." with nothing pointing at the cause.
The cause: the relay served its route index under BOTH `api` and a legacy
prefix, while serving the actual routes only under `api`. The app settles its
REST prefix by probing for that index and keeping the first prefix that answers
-- so it adopted the legacy prefix, and every call 404'd.
⚠️ This was supposed to have been fixed yesterday, and was not. `f5614ab`
(Aug 21, "Serve the four routes the app was calling into a 404") is what
INTRODUCED the two-prefix index loop; it was the cause, not the cure. The rule
got written down and the code change never landed. My own notes asserted a fix
that no branch contained. Believe grep.
The rule, which is more general than this bug: **serve a discovery document only
where the things it describes exist.** A document listing routes a prefix does
not serve is worse than no document, because it is believed.
Fixed in three places, because one was not enough:
- the relay serves the index only under `api`;
- the client probes only `api` -- there is one prefix, and probing for others
only creates ways to be wrong;
- the index no longer advertises routes that are not mounted.
And the purge the owner asked for: no `WordPress`, `wp-json`, `wp/v2`,
`wp-admin`, `wp-login`, `wp_` or `wp-cron` anywhere in the relay, the iOS app,
the Android app or the tests. `/api/wp/v2/users/me` is now
`/api/flamenet/v1/messenger/me`; the user lookup moves alongside it; the dead
`ajaxURL` and the two error cases only a web login form could produce are gone.
⚠️ Recorded because it cost time: the deployed relay source on the box is NOT in
any branch. It carries multi-homing `envelope_id` work that exists nowhere in
git, so copying local files over it broke the build. Restored from the prod
tree, then patched in place. That divergence needs closing.
Adds CrossPlatformUITests (iOS) and CrossPlatformTest (Android) -- each driven
by arguments so the two platforms can be interleaved from a shell, because two
iOS accounts in one simulator prove only that the app agrees with itself.
With this, item 5 is done: a message typed in the iOS app arrived and rendered
in the Android app, through relay1, end-to-end encrypted.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
