Launch and access status

What is publicly available now, including the unpublished TestFlight and closed account actions.

  • Launch status
  • TestFlight
  • Accounts

Availability

#

The public landing page, launch documentation, download-status page, sign-in, and health page are available. Public TestFlight access is not published. There is no public install link, build number, expiration, tester count, or waitlist.

Registration, verification, recovery, privacy, and terms are closed. Sign-in is for existing verified users only. Private shelves, history, catalog, sessions, devices, and settings require an authenticated account. Community, feed, posting, reactions, groups, discussions, tracker changes, and reviews are not public launch capabilities.

Prerequisites

#
  • No account is required to read this guide
  • An existing verified account is required to use sign-in

Steps

#
  1. Read this status before following an old install or account link.
  2. Use Getting started if you already have an authorized native build.
  3. Use sign-in only if you are an existing verified user.
  4. Return to the public download-status page for the current acquisition state.

Expected result

#

Every public action leads to a capability that is available in the current state. An open downloads page does not imply that a TestFlight build or install link exists.

Recovery

#

Do not retry or work around a closed registration, verification, recovery, privacy, terms, or TestFlight action. Return here and use the published documentation instead.

Product proof

#

The launch-state labels are derived from the website availability manifest. They do not fall back to sample account, waitlist, provider, or TestFlight data when state cannot be loaded.

Support and verification

#

This guide was verified against native app commit 910ef6e62eff5c99206a479148b6f2eda9d7338e on 2026-07-22 and website availability behavior reviewed on 2026-07-23. The public build number is not published.

If the public surface offers an action that conflicts with this guide, preserve the page URL and visible label, then use Troubleshooting and build information. Never share passwords, cookies, tokens, or verification codes.

Related docs

Continue through adjacent guides that share this article's tags, targets, or audience lanes.