# Build Not Showing in TestFlight? Fix the Bundle ID

If your iOS build uploads successfully but never shows in TestFlight, and the upload log says `Cannot determine the Apple ID from Bundle ID`, the cause is almost always a bundle ID mismatch: App Store Connect has no app record matching the bundle ID your build was signed with, so Apple has nowhere to file it. The certificate is rarely the problem. The fix takes about five minutes once you know which of two cases you are in.

This is one of the most common issues no-code and low-code builders hit on their first iOS submission, and it produces a confusing symptom: the build reports success, yet TestFlight stays empty with no failed or processing status to explain why.

You are probably here because you are seeing one of these:

*   The build finishes green in Despia or Codemagic, but no build appears in TestFlight.
    
*   App Store Connect shows no build at all, not even a failed one.
    
*   The upload log contains `Cannot determine the Apple ID from Bundle ID`.
    
*   You have retried for days or weeks and the TestFlight page is still blank.
    

All four point at the same root cause.

## Why does a successful build not appear in TestFlight?

A successful build means your app compiled and signed correctly. The IPA is a valid binary. What failed is the final step: Apple could not attach the upload to an App Store Connect app record, so the process stops one step short of TestFlight.

Every iOS app in App Store Connect is identified by a bundle ID, a reverse-domain string like `com.acme.app`. When Despia uploads your build, Apple looks for an app record in your account that uses that exact bundle ID and files the build under it. If no record uses that bundle ID, Apple rejects the handoff and the build has nowhere to go.

That is also why there is no failed build in your TestFlight history. The build never got far enough to be attached to an app, so there is nothing to display. From the TestFlight side it looks like you never submitted anything, which is why weeks of retries still show a blank page.

## What does "Cannot determine the Apple ID from Bundle ID" mean?

This is the exact line in the upload log that confirms the diagnosis:

```plaintext
ERROR: Cannot determine the Apple ID from Bundle ID 'com.acme.app' and platform 'IOS'
```

"Apple ID" here means the app's internal record ID inside App Store Connect, not your Apple login email. Apple is saying it has no app matching that bundle ID on the iOS platform. When you see this error, you do not have a signing problem, a build problem, or a certificate problem. You have a missing or mismatched app record. That is the entire failure.

## How to find the bundle ID Despia is using

Before touching App Store Connect, confirm the exact string your build is signed with. In Despia, go to App > Publish > iOS > Bundle ID and copy it. This is the value that has to match on Apple's side. Every example below uses `com.acme.app` as a stand-in for your real bundle ID.

## Fix 1: create the missing App Store Connect record

If you have never created the app in App Store Connect, that is the whole problem. Create the record:

1.  Go to [App Store Connect > Apps](https://appstoreconnect.apple.com/apps).
    
2.  Click the blue plus button near the top left, then choose New App.
    
3.  Tick iOS as the platform.
    
4.  Give it a name.
    
5.  In the Bundle ID dropdown, select `com.acme.app`. If it is not listed, register it first at [Apple Developer > Identifiers](https://developer.apple.com/account/resources/identifiers/list), then return to this screen.
    
6.  Set an SKU (any short text works), and save.
    

Once the record exists, run one new build. It lands in TestFlight within a few minutes.

## Fix 2: correct a listing pointing at the wrong bundle ID

This case catches people who did everything else right. You created the listing earlier with a different bundle ID than the one Despia now builds against, so the build and the record never match.

1.  Open your existing app in [App Store Connect](https://appstoreconnect.apple.com/apps).
    
2.  In the left sidebar, open App Information.
    
3.  Find the Bundle ID field.
    

Sometimes there is a dropdown here and you can select `com.acme.app` and save. If that works, you are done, run one more build.

Sometimes it is no longer possible. Once Apple has locked a record to its original bundle ID, the dropdown will not offer the new value and the field is fixed. When that happens you cannot reuse the listing. Create a fresh one using Fix 1 with the bundle ID Despia actually builds against. The old listing can sit unused.

## Why AI setup advice causes this

Most bundle ID mismatches trace back to setup steps from an AI assistant that is confident and wrong. It tells people to revoke a valid certificate, invent a new bundle ID mid-setup, or bump a build number that was never the issue. Each of those wastes a build and stacks a new mismatch on top of the first.

The setup runs in a fixed order for a reason. The bundle ID in Despia, the identifier on Apple Developer, and the app record in App Store Connect all have to carry the same string, created in the right sequence. The Despia documentation walks that path start to finish so nothing ends up crossed:

[iOS automatic deployment guide](https://setup.despia.com/deployment/apple-ios/automatic)

Follow it from the top once and the build that has been failing for weeks goes straight through.

## FAQ

**Is my certificate the problem if the build does not show in TestFlight?** Almost never. If the build reports success, the certificate signed it correctly. A build that uploads but does not appear in TestFlight is a bundle ID or app record issue in App Store Connect, not a signing one.

**Why is there no failed build in my TestFlight history?** Because the build was never attached to an app record. Apple could not match the bundle ID to a listing, so the upload was rejected before it became a build Apple could display. An empty history is the expected symptom of this error.

**Do I need to increase the build number or version to fix it?** No. The build number is not the problem and raising it just spends another build. The record on Apple's side needs to exist and match your bundle ID.

**Can I change the bundle ID of an existing App Store Connect app?** Sometimes. If the App Information page shows a Bundle ID dropdown, you can switch it and save. If Apple has locked the field, the bundle ID is permanent for that record and you need a new listing that matches your build.

**How long does a build take to appear in TestFlight once the record exists?** Usually a few minutes after a successful upload, though Apple can take longer to finish processing. If it does not appear at all and the record exists with the correct bundle ID, check the upload log for a different error.

## Get it on the stores

Take the app you already built and ship it to iOS and Android without a CLI or a Mac. Code signing and submission run from the browser, and the setup guide keeps every ID lined up so your first build reaches TestFlight.

[See the setup docs at setup.despia.com](https://setup.despia.com/deployment/apple-ios/automatic)