Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app build was uploaded but it never shows up in TestFlight

Short answer

Apple processes every uploaded build before it shows in App Store Connect and sends an email when processing is done. Check the delivery log and your email first, then the build's status in TestFlight. A build waiting on export compliance answers also needs a reply from you before testers see it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The upload finished but the build is not in App Store Connect.
  • The build shows Processing for a long time.
  • I did not get the email that Apple sends when processing is done.
  • The build appears but testers cannot be given it.
  • My developer says it was uploaded and does not know what else to do.

Why does this happen?

  1. The build is still being processed

    Apple says a build must be processed before it appears in App Store Connect, and that you receive an email when processing is complete.

  2. The upload itself had a problem

    Xcode and Transporter show delivery progress, with warnings, errors and logs of past deliveries. A failed upload never reaches processing.

  3. The build was built with an unsupported Xcode

    Apple's page lists the Xcode versions that apps must be built with and uploaded with. A build made with an older version can be turned away.

  4. The build is waiting for encryption answers

    A build can sit in a status that needs export compliance information before it can be tested. The technical detail is on the fix page linked below.

  5. The email went to someone else

    The notification goes to the account that uploaded. If that was a former developer, you may never see it.

What can I do about it today?

  1. Check your inbox and spamLook for the Apple email about the build. Also ask the person who uploaded whether it came to them.
  2. Open TestFlight in App Store ConnectLook at the build list for the app and note the build number and its status.
  3. Ask for the delivery logAsk your developer to send you a screenshot of the delivery result from Xcode or Transporter.
  4. Do not upload the same build again and againA new build normally needs a new build number. Repeated uploads confuse the list.
  5. Look for a request for answersIf the build shows a warning about compliance information, ask your developer to answer it with you.

When should I bring someone in?

  • The build is missing and the delivery log shows an error nobody understands.
  • You cannot sign in to App Store Connect or have no role to see TestFlight.
  • A release date depends on this build.

How do I handle it?

  1. Read the delivery resultI look at the upload log first, since it says whether the build reached Apple.
  2. Check the build against Apple's requirementsVersion, build number, tools used and required settings are compared with the current rules.
  3. Answer the compliance questions with youThe answers are about your app, so I explain each question and you confirm them.
  4. Upload a corrected build only when neededIf the build cannot be fixed in place, a new one with a new number is uploaded.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How long does processing take?

The Apple page I read gives no time. It says only that processing must finish and that you get an email.

Will testers see the build automatically?

Not always. External testers need the build added to a group, and Apple may review the first build.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.