If TestFlight says no builds are available even though you uploaded one, the build almost always exists but is not yet available to testers, usually because it is still processing, its export compliance question is unanswered so App Store Connect is holding it, it has not been assigned to the tester's group, or App Store Connect has not finished syncing it to the TestFlight app. It does not normally take 24 hours: once processing finishes, export compliance is answered, and the build is assigned, it appears within minutes to a couple of hours. Check that the build finished processing, answer the export compliance question if it shows Missing Compliance, assign the build to your testers, and refresh TestFlight. A missing export compliance answer is one of the most common reasons a uploaded build never becomes available.
Short answer
The build exists but is being held or has not synced, most often due to unanswered export compliance or still-in-progress processing. Per Apple's export compliance guidance, a build with unanswered export compliance is held and not made available until you answer the encryption question in App Store Connect. Per Apple's TestFlight documentation, builds must finish processing and be assigned to testers before they appear. It does not usually take 24 hours; once processing, compliance, and assignment are done, the build syncs to TestFlight within minutes to a couple of hours. Check each of those, then refresh.
Why TestFlight shows no builds available
When TestFlight reports no builds available after you uploaded one, the build has not been lost; it is simply not yet in a state where testers can see it. A build becomes available to testers only after several conditions are met: it must finish processing, its export compliance must be answered, it must be assigned to the tester group in question, and, for external testers, it must have passed Beta App Review. Until all of those are satisfied, the build exists in App Store Connect but does not appear as available, which is what you are seeing.
So the message is about the build's readiness, not its existence. The productive approach is to check each condition in App Store Connect rather than assume the upload failed, because in most cases the upload succeeded and one of these steps is incomplete. The most common culprits are that the build is still processing or that its export compliance question has not been answered, both of which hold the build back, so those are the first two things to check when a uploaded build is not showing up for testers.
Is export compliance missing?
A missing export compliance answer is one of the most common reasons a uploaded build never becomes available, so check for it early. When you upload a build, App Store Connect asks whether your app uses encryption, for export compliance reasons, and until you answer that question the build is held with a Missing Compliance status and is not made available to testers. So a build can finish processing perfectly and still not appear, simply because the compliance question is waiting on you.
Resolve it by answering the export compliance question in App Store Connect for that build, which releases it once answered. If your app does not use non-exempt encryption, you can answer accordingly, and you can avoid the prompt on future builds by declaring the appropriate encryption usage key in your app's Info.plist, so the compliance state is set at build time rather than requiring a manual answer each upload. If your build shows Missing Compliance, answering that question is very often the entire fix, and the build becomes available shortly after.
Does it take 24 hours?
No, making a uploaded build available to testers does not normally take 24 hours, so a full day of waiting is not the expected behavior. Once the build has finished processing, its export compliance is answered, and it is assigned to testers, App Store Connect syncs it to the TestFlight app, and that propagation typically takes minutes to a couple of hours rather than a day. The idea that you must wait 24 hours is a misconception; most builds appear well within that.
Where longer waits come from is usually one of the prerequisites not being complete, not the sync itself. If the build is still processing, or its compliance is unanswered, or it has not been assigned, it will not appear no matter how long you wait, so the delay is the missing step, not a slow clock. So rather than waiting a day, check that processing finished, compliance is answered, and the build is assigned, then allow the short sync window. If everything is done and the build still has not appeared after a couple of hours, that is when a backend sync issue or a support case is worth considering, not before.
Other causes: assignment, review, and sync
Beyond processing and compliance, a few other conditions keep a build from appearing. Assignment is a common one: a processed, compliance-answered build still does not show for a tester if it has not been assigned to that tester's group, so confirm the build is added to the group the tester is in. For external testers specifically, the build must also have passed Beta App Review before it becomes available, so an external build waiting on review will not appear to external testers yet.
Backend sync delay is the last piece, and it is the one the phrase most literally describes: after all the conditions are met, App Store Connect and the TestFlight app take a short time to reflect the build, so a build that just became eligible may take a little while to show. This usually resolves on its own within the short window, and refreshing the TestFlight app or App Store Connect helps. So the full set of reasons is processing, compliance, assignment, review for external, and sync, and checking them in that order finds the cause.
Developer-side fixes
On your side, work through the conditions in App Store Connect. Confirm the build finished processing and is no longer showing as processing. Check its export compliance and answer the question if it shows Missing Compliance, which is frequently the fix. Make sure the build is assigned to the correct tester group, since an unassigned build is invisible to testers, and for external testers confirm Beta App Review has passed. These four checks cover the conditions that hold a build back.
If all of those are satisfied and the build still does not appear, give the sync a short window and refresh App Store Connect. Distributing or re-assigning the build to the group can also nudge it. Only after the build is genuinely processed, compliant, assigned, reviewed where needed, and past a reasonable sync wait should you consider that something is wrong, at which point contacting Apple Developer Support with your app and build details is appropriate. Most of the time, one of the four conditions was incomplete and completing it makes the build appear.
Tester-side fixes
If you are a tester who cannot see a build the developer says they uploaded, a few quick checks help. Make sure you are signed into the TestFlight app with the same Apple ID that received the invitation, since a build assigned to one Apple ID will not appear under a different one. Pull to refresh in the TestFlight app or reopen it, because the app may not have synced the newly-available build yet, and a refresh often brings it in.
Also confirm you have accepted the TestFlight invitation for the app and that you are in the tester group the build was assigned to, since being invited but in the wrong group, or not having accepted, means the build will not show. If the build genuinely is not yet available, it may still be processing, held on compliance, or awaiting review on the developer's side, which only they can resolve. So a tester's checks are mainly about the right account and a refresh, with the rest depending on the developer completing the build's conditions.
Causes and fixes
Matching the cause to a fix directs your check. The table below pairs them.
| Cause | Why no build appears | Fix |
|---|---|---|
| Still processing | Not yet available to testers | Wait for processing to finish |
| Missing export compliance | The build is held until answered | Answer the compliance question |
| Not assigned to the group | Testers cannot see an unassigned build | Assign the build to the tester group |
| Beta App Review pending, external | External build not yet released | Wait for Beta App Review to pass |
| Backend sync delay | Eligible but not yet propagated | Wait a short window and refresh |
Read the table in order: processing and compliance are the most common, so check them first, then assignment, review, and finally sync.
Fix checklist
Working through these steps makes the build appear. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Confirm processing finished | The build is no longer processing | [ ] |
| Answer export compliance | Clear any Missing Compliance status | [ ] |
| Assign to the tester group | The build is added to the right group | [ ] |
| Confirm review for external | Beta App Review has passed | [ ] |
| Refresh TestFlight | Pull to refresh with the correct Apple ID | [ ] |
| Escalate if still missing | Contact support after the conditions are met | [ ] |
The step that resolves the most cases is answering export compliance, since a Missing Compliance status silently holds an otherwise-ready build back from testers.
Use the wait to verify the build
While you complete the conditions that make the build available, the short wait is time you can use to confirm the build itself is sound before testers receive it, rather than only refreshing App Store Connect.
A scanner like PTKD.com analyzes your build and reports issues such as leaked keys and secrets, over-broad permissions, and insecure data handling by severity, mapped to OWASP MASVS, so the build that becomes available to testers is checked for security problems. To be clear about the boundary: PTKD does not answer your export compliance, assign builds, or manage TestFlight, which you handle in App Store Connect. It checks the build itself so the version that finally appears for testers is one you have verified.
What to take away
- TestFlight saying no builds available usually means the build exists but is held or not synced, not that the upload failed.
- A missing export compliance answer is one of the most common causes: a build with Missing Compliance is held until you answer the encryption question in App Store Connect.
- It does not normally take 24 hours; once processing, compliance, and assignment are done, the build syncs within minutes to a couple of hours.
- Also check that the build is assigned to the tester group and, for external testers, that Beta App Review has passed, then allow a short sync window.
- Confirm each condition in App Store Connect, have testers refresh with the correct Apple ID, and scan the build with a tool like PTKD.com.
