TestFlight Says No Builds Available? How to Fix It

Quick answer: "No Builds Available" means that the tester has no build that they can install. In App Store Connect, open the TestFlight tab of your app and find the build status.

• Missing Compliance: answer the export compliance questions.
• Ready to Test: add the tester's group to the build, or click Notify Testers.
• Expired: upload a new build.

An external build must also pass TestFlight App Review first. If the status is Testing and the tester still sees no build, check the tester's iOS version. Also check the Apple Account that accepted the invitation.

Developers on the Apple Developer Forums see this message in different places in App Store Connect. It can show in a tester's status or in the public link section of a group. In all cases, start with the build status.

Start with the build status

In App Store Connect, open Apps and choose your app. Click the TestFlight tab. In the sidebar, under Builds, click the platform.

Each build shows a status. The table shows the statuses that are important for this problem. They come from Apple's App build statuses reference.

The causes, one by one

1. The build is still processing

After you upload a build, Apple processes it. You cannot test the build before processing ends. Apple sends you an email when processing ends.

To check the processing status, expand Build Uploads on the TestFlight tab. The Status column shows Processing, Failed or Complete.

According to Apple's help page, a build that stays in Processing for more than 24 hours can have a problem. In this case, file a Feedback Assistant ticket or contact Apple.

If the status is Failed, select the upload to see the errors. Fix the errors and upload the build again.

2. The export compliance question is not answered

If a build has no encryption information, its status is Missing Compliance. The build stays in this status until you answer the questions. To answer them, follow Apple's steps:

1. Click the build.
2. Click Provide Export Compliance Information.
3. Answer the questions.
4. Click Save.

You must have the Account Holder, Admin or App Manager role.

To stop these questions for each new build, add the ITSAppUsesNonExemptEncryption key to your Info.plist.

Apple's encryption export guide tells you to set the key to NO if your app uses no encryption or only exempt encryption. This includes the third-party libraries in your app. In all other cases, set the key to YES.

Encryption that is part of the operating system, such as HTTPS, is usually exempt. Read the guide before you choose.

In a 2020 forum thread, several developers fixed "No Builds Available" with this key. They added the key and uploaded a new build.

3. The build is not in the tester's group

A build goes only to the groups and individual testers that you add to it. The status Ready to Test shows this problem. The build is correct, but no tester has it yet.

Open the build and look at Groups and Individual Testers. To add a group, follow the steps in Add testers to builds:

1. Click the add button (+) next to Groups.
2. Select the group.
3. Click Add.

Three settings often cause this problem:

• Internal groups get builds automatically only if you selected "Enable automatic distribution". You must always add builds from Xcode Cloud by hand.
• TestFlight Internal Only builds go only to internal groups. If you uploaded a build with this option, external testers never see it. Upload a new build.
• External groups have an "Automatically notify testers" checkbox. If you cleared it, the approved build does not go to testers until you click Notify Testers under Status (Invite external testers).

A public link shows the same message when its group has no build. Our guide on TestFlight public links that don't work covers this case.

4. The build expired

Each build is available for testing for 90 days after the upload day (TestFlight for testers). After 90 days, the status changes to Expired. Then testers cannot open the beta.

Upload a new build with a new build string. Add the new build to the groups.

5. An external build is waiting for or failed TestFlight App Review

External testers get a build only after TestFlight App Review approves it. Many people call this review Beta App Review. Until the approval, the status is Waiting for Review or In Beta Review.

Internal testers do not wait for this review. Apple says that the first build you submit gets a full review. Later builds for the same version do not always get a full review (Invite external testers).

If the status is Rejected, click App Review in the sidebar under General. There you can read the reason. Fix the problem and submit a new build.

Our guide to adding external testers in TestFlight explains each step of the review.

6. The device or iOS version doesn't match the build

The TestFlight app needs iOS 16 or iPadOS 16 or later (TestFlight requirements). Your build also has its own requirements.

To find them, open the build and click the Build Metadata tab. Under device requirements, find Minimum iOS version (View builds and metadata).

Ask the tester for their iOS version. They can find it in Settings, General, About. If their version is lower than your minimum, the tester must update iOS, or you must lower the deployment target.

Each platform has separate builds. A macOS build does not help a tester on iPhone. Make sure that the group has a build for the tester's platform.

7. The tester accepted the invite with a different Apple Account

The email address in the invitation can be different from the tester's Apple Account. Apple's tester information reference says it "may or may not be the same". The problem starts when the wrong account accepts the invitation.

A typical forum report describes this case. Someone accepts the invitation on a device that uses a different Apple Account. For example, the device uses a personal account instead of a work account.

The beta then works on that device. But the invited person cannot get the beta with their own account.

In another thread, a developer posted the reply from Apple. Each tester can connect to only one Apple Account.

Apple suggests a fix. Remove the tester from All Testers for all apps. Then invite the tester again.

When the tester accepts, they must be signed in to TestFlight with the correct account. Some developers in the same thread say that these steps did not work for them.

8. An internal tester has no access to the app

Internal testers are App Store Connect users with one of these roles: Account Holder, Admin, App Manager, Developer or Marketing (TestFlight for developers).

You can limit users with the App Manager, Developer or Marketing role to specific apps. To give a user access to your app, follow Edit access to apps:

1. Go to Users and Access, then People.
2. Click the user.
3. Click Manage apps.
4. Select your app.
5. Click Save.

Then add the user to the internal group. Managed Apple Accounts created in reserved domains can't test builds at all.

When everything looks right

Sometimes the problem is in Apple's systems. An example is a January 2026 thread about internal testers not getting new builds. An App Store Connect Engineer replied there that the issue was resolved.

Check the Apple Developer System Status page. Look at the App Store Connect - TestFlight service.

Checklist

1. Build Uploads shows Complete, not Processing or Failed.
2. The build status is not Missing Compliance.
3. The build is less than 90 days old.
4. For external testers, the build passed TestFlight App Review.
5. You added the tester's group to the build, or you clicked Notify Testers.
6. If the tester is external, the build is not TestFlight Internal Only.
7. The tester's iOS version meets your minimum. The build is for the tester's platform.
8. The tester is signed in to TestFlight with the Apple Account that accepted the invitation.
9. Internal testers have a role that can test builds. They also have access to this app.

When testers can install the build, the next problem is to get feedback from them. Read why TestFlight testers don't send feedback.

After launch

TestFlight is for builds before release. After your app is live on the App Store, you still need people to use it. You also need them to tell you what breaks.

Raizy is a free feedback exchange for indie iOS developers. In a feedback session, another developer installs your app from the App Store on their own iPhone. They upload a short screen recording or a screenshot and write notes.

A moderator checks every feedback session before any credit moves. You earn credits by testing other developers' apps. Raizy does not take TestFlight builds.

See how feedback on a live iOS app works.