Why isn’t my TestFlight build showing up?
You uploaded the build. TestFlight shows nothing. This is almost never a broken binary. It is a processing or compliance state that has to clear before Apple makes the build available to testers.
What are the usual causes?
The build is still processing — large binaries can take 30 minutes or more. Export compliance is unanswered: Apple requires the encryption declaration before any external testing. The build expired or was invalidated by a newer upload. A missing icon, wrong version number, or signing issue failed Apple’s automated checks silently.
What about the export compliance question?
Every build asks whether the app uses encryption. Most apps answer yes because of HTTPS, then supply the standard exemption. If nobody answers, external testing stays blocked indefinitely while internal testing works — which makes the problem confusing. You can set the ITSAppUsesNonExemptEncryption key in Info.plist to answer it once for all future builds.
How do you stop guessing?
Read the build’s actual state in App Store Connect instead of re-uploading blindly. AiSCent checks build processing state, export compliance, and tester availability, so you know whether to wait, answer a question, or fix the binary.