The iPhone tile has read "Coming soon" for months, because this page
once described a submission that had not happened. It is open now, as
a TestFlight beta, and both language versions link to it.
It says TestFlight and it says beta. The opposite mistake became
available the moment the link existed: "out on iPhone" would be the
same overclaim wearing better news, and a beta link can be withdrawn.
iosLive stays OFF for that reason — it rewrites seven clauses elsewhere
to read "Both apps", which states general availability.
Three claims elsewhere were true only because no iPhone build existed,
and stopped being true when one did:
comparison.leaf ended a row with "so today that means two Android
phones". Two iPhones can hold that conversation now. Removed, and the
six pre-App-Store branches say "on iPhone as a TestFlight beta"
instead of "once Apple approves" — the approval is not what gates it.
metadata.leaf said group names come to iPhone once Apple approves.
The build carrying them is installable today.
engine.leaf said "there is no iPhone build to run one".
engine.leaf keeps its rule rather than being upgraded past it: that
page reports what has been RUN, and two iPhones negotiating v3 has not
been exercised on real hardware. It now says the build exists AND that
the pairing is unproven, because a build existing is not a pairing
having been observed.
4 new tests, including one that fails if either language page stops
naming TestFlight and one that fails if any page reverts to assuming no
iPhone build exists. 54 tests green.
The iPhone tile has read "Coming soon" for months, because this page
once described a submission that had not happened. It is open now, as
a TestFlight beta, and both language versions link to it.
It says TestFlight and it says beta. The opposite mistake became
available the moment the link existed: "out on iPhone" would be the
same overclaim wearing better news, and a beta link can be withdrawn.
iosLive stays OFF for that reason — it rewrites seven clauses elsewhere
to read "Both apps", which states general availability.
Three claims elsewhere were true only because no iPhone build existed,
and stopped being true when one did:
- comparison.leaf ended a row with "so today that means two Android
phones". Two iPhones can hold that conversation now. Removed, and the
six pre-App-Store branches say "on iPhone as a TestFlight beta"
instead of "once Apple approves" — the approval is not what gates it.
- metadata.leaf said group names come to iPhone once Apple approves.
The build carrying them is installable today.
- engine.leaf said "there is no iPhone build to run one".
engine.leaf keeps its rule rather than being upgraded past it: that
page reports what has been RUN, and two iPhones negotiating v3 has not
been exercised on real hardware. It now says the build exists AND that
the pairing is unproven, because a build existing is not a pairing
having been observed.
4 new tests, including one that fails if either language page stops
naming TestFlight and one that fails if any page reverts to assuming no
iPhone build exists. 54 tests green.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The iPhone tile has read "Coming soon" for months, because this page
once described a submission that had not happened. It is open now, as
a TestFlight beta, and both language versions link to it.
It says TestFlight and it says beta. The opposite mistake became
available the moment the link existed: "out on iPhone" would be the
same overclaim wearing better news, and a beta link can be withdrawn.
iosLive stays OFF for that reason — it rewrites seven clauses elsewhere
to read "Both apps", which states general availability.
Three claims elsewhere were true only because no iPhone build existed,
and stopped being true when one did:
phones". Two iPhones can hold that conversation now. Removed, and the
six pre-App-Store branches say "on iPhone as a TestFlight beta"
instead of "once Apple approves" — the approval is not what gates it.
The build carrying them is installable today.
engine.leaf keeps its rule rather than being upgraded past it: that
page reports what has been RUN, and two iPhones negotiating v3 has not
been exercised on real hardware. It now says the build exists AND that
the pairing is unproven, because a build existing is not a pairing
having been observed.
4 new tests, including one that fails if either language page stops
naming TestFlight and one that fails if any page reverts to assuming no
iPhone build exists. 54 tests green.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
359adc133cchanged the description