When TestFlight shows Could not install app or Couldn't load the app, the cause is almost always on the tester's device or the build's requirements, not a broken app: the most common reasons are the tester's iOS version being lower than the build's minimum, a network hiccup during download, the build having expired, or not enough free storage. Have the tester confirm their iOS version meets the build's minimum, retry on a stable Wi-Fi connection, free up space, and make sure the TestFlight app is up to date, then reopen TestFlight and tap Install again. On your side, check that the build's minimum iOS version does not exclude your testers and that the build has not expired, since a build older than ninety days can no longer be installed.
Short answer
The error is usually a device or build-requirement issue, not a broken app. Per Apple's TestFlight documentation, builds have a minimum iOS requirement and expire after ninety days, so a tester on an older iOS or trying an expired build cannot install it. Have the tester check that their iOS version meets the build's minimum, retry on stable Wi-Fi, free up storage, update the TestFlight app, and restart the device. On your side, per Apple's iOS support guidance, confirm the build's minimum deployment target does not exclude your testers and that the build is current. If it persists, distribute a fresh build built for a lower iOS version.
What the error means
The Could not install app or Couldn't load the app message is TestFlight reporting that it was unable to download or install the beta build on this device, and it is deliberately generic, which is why it needs some diagnosis. It does not mean your app crashed or that the build is fundamentally broken; it means the installation itself did not complete, usually because a condition on the device or a property of the build prevented it. So the fix is to find which condition applied, rather than to assume something is wrong with your code.
The reason it lands on developers is that external testers see this vague message and turn to you to explain it. Because the common causes are a handful of specific, checkable things, an iOS version below the build's requirement, a network problem, an expired build, or insufficient storage, you can usually resolve it by walking the tester through a few checks or by adjusting the build. Treating it as an install-condition problem rather than an app failure points you at the right fixes quickly, most of which the tester can do themselves.
iOS version mismatch
An iOS version mismatch is one of the most common causes, and it happens when your build requires a newer version of iOS than the tester's device is running. Every build has a minimum iOS deployment target, and if the tester's device is on an older iOS than that minimum, TestFlight cannot install the build on it, producing the error. This is especially common when you raise your deployment target and a tester has not updated their device, or when a tester is on an older or unsupported device.
There are two ways to resolve it. The tester can update their device to an iOS version that meets or exceeds the build's minimum, which is often the simplest fix if their device supports the newer iOS. Alternatively, if you need to support testers on older iOS versions, you lower your build's minimum deployment target and distribute a new build, so it can install on their devices. To diagnose it, compare the tester's iOS version against your build's minimum: if the device is below it, the mismatch is the cause, and one side or the other needs to change.
Network issues
A network problem during the download is another frequent cause, since TestFlight has to download the build and a flaky or slow connection can interrupt it, producing the couldn't load or could not install message. This is often transient, so the first thing to try is simply retrying the install on a stable connection. Switching from a weak cellular signal to a reliable Wi-Fi network, or vice versa if Wi-Fi is the problem, resolves many of these cases.
Have the tester confirm they have a working internet connection, then reopen the TestFlight app and tap Install again, since a fresh attempt on a good connection often succeeds where an interrupted one failed. If the connection drops repeatedly, moving to a different network or waiting until they have stable signal helps. Because network-caused failures are not about your build at all, they usually clear on retry, so a network issue is worth ruling out early with a simple reattempt before looking at build-side causes.
Other common causes
Beyond iOS mismatch and network, a few other conditions cause this error. An expired build is a frequent one: TestFlight builds expire ninety days after upload, and an expired build can no longer be installed, so if the build the tester is trying is old, you need to distribute a newer, unexpired build. Insufficient storage on the device is another, since the install needs enough free space, and a nearly-full device fails to install until the tester frees some. A device with an incorrect date and time can also fail installs.
Some causes are about access rather than the device. If the tester was not properly invited, has not accepted the invitation, or the build is not actually available to their tester group, they cannot install it, so confirm they are on the tester list and the build is distributed to them. An outdated TestFlight app or one that needs a restart can also misbehave. Ruling out these, expiry, storage, date and time, invitation, and the TestFlight app itself, covers most cases that are not iOS mismatch or network.
Tester-side fixes
Most of the fixes are things the tester can do, so walk them through the quick checks first. Ask them to confirm their device is running an iOS version that meets the build's minimum, connect to a stable Wi-Fi network, and ensure they have enough free storage, then reopen TestFlight and tap Install again. If it still fails, have them update the TestFlight app to the latest version and restart their device, which clears a surprising number of transient install problems.
A few more tester-side steps help in stubborn cases: checking that the device's date and time are set automatically and correct, deleting any partially-installed version of the app before retrying, and confirming they accepted the TestFlight invitation for your app. These are quick to try and resolve the common device-side causes, so having the tester run through them, ideally in order from the most common, iOS version and network, to the less common, usually clears the error without any change on your side.
Developer-side checks
When the tester's checks do not resolve it, a few things on your side are worth confirming. Check your build's minimum iOS deployment target and compare it to what your testers actually run, since a target set too high silently excludes anyone on an older iOS, and lowering it and distributing a new build fixes that. Confirm the build has not expired, and if it is near or past ninety days, upload and distribute a fresh one, since testers cannot install an expired build regardless of their device.
Also verify the distribution side: that the build is actually assigned to the tester's group and that the tester is correctly on the list, because an access gap looks like an install failure to the tester. If a specific build seems broken for everyone, distributing a new build is a reliable reset. Between the tester-side checks and these developer-side ones, the cause is usually found, and the fix is either a device change the tester makes or a new build you distribute with the right minimum iOS version.
Causes and fixes
Matching each cause to who fixes it speeds resolution. The table below pairs them.
| Cause | Who resolves it | Fix |
|---|---|---|
| iOS below the build's minimum | Tester or developer | Update iOS, or lower the deployment target and rebuild |
| Network interruption | Tester | Retry the install on stable Wi-Fi |
| Expired build, over ninety days | Developer | Distribute a fresh, unexpired build |
| Insufficient storage | Tester | Free space and retry |
| Invitation or access gap | Developer or tester | Confirm the invite and that the build is assigned |
Read the table by who acts: iOS version and network are usually tester-side, while an expired build or access gap is developer-side.
Fix checklist
Working through these steps resolves the error. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Check the iOS version | Confirm it meets the build's minimum | [ ] |
| Retry on stable Wi-Fi | Rule out a network interruption | [ ] |
| Free up storage | Ensure space to install | [ ] |
| Update TestFlight and restart | Latest app, reboot the device | [ ] |
| Confirm the build is current | Not expired past ninety days | [ ] |
| Confirm the invitation | Tester is on the list and the build is assigned | [ ] |
The step that resolves most cases is checking the iOS version against the build's minimum, since a mismatch there is the single most common reason a tester cannot install.
Prep the build to avoid install issues
While the install error itself is an operational issue rather than a security one, the moment you are preparing or redistributing a build to fix it is a reasonable time to confirm the build is otherwise sound before your testers receive it.
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 your testers install is checked for security problems. To be clear about the boundary: PTKD does not fix a TestFlight install error, which comes down to iOS versions, networks, and build settings, and it does not manage your distribution. It checks the build itself, so the version that finally installs is also one you have verified.
What to take away
- The Could not install or Couldn't load the app error is usually a device or build-requirement issue, not a broken app, and it is generic by design.
- An iOS version below the build's minimum is the most common cause, fixed by the tester updating iOS or by you lowering the deployment target and rebuilding.
- A network interruption during download is common and usually clears on a retry over stable Wi-Fi, so rule it out early.
- Also check for an expired build past ninety days, insufficient storage, an outdated TestFlight app, and whether the tester is properly invited and assigned the build.
- Walk the tester through the device-side checks first, confirm the build and distribution on your side, and scan the build with a tool like PTKD.com.
