After uploading the IPA to App Store Connect, you may see a success message, but when you return to your app’s page, the build list is empty—this is a problem many developers have encountered. A successful upload does not guarantee that the build will appear; Apple’s backend performs a series of validations on the IPA, and builds that fail validation will not be displayed.

Check Your Email After a Successful Upload

Once the upload tool shows a success message, Apple sends a notification email to the email address associated with your developer account. It is recommended to check your inbox, including the spam folder. The email will clearly state whether the upload succeeded or failed, and failure emails include specific error reasons and codes. This is the most direct way to troubleshoot why a build hasn’t appeared.

Common error emails include: incorrect certificate type, app icon containing an alpha channel or transparency, missing permission declarations, and redundant binary uploads.

Wait for Processing Time

After a successful upload, the build will not appear immediately. Apple’s backend needs to scan and process the newly uploaded IPA, which typically takes 10-30 minutes, sometimes longer. In App Store Connect, on the “My App → Activity → Builds” page, if it shows “Processing,” the upload was successful—just wait for it to complete.

If it still hasn’t appeared after a few hours, it means the IPA was deemed problematic during processing, and you should have received a failure email in your inbox.

Duplicate Version Number

An IPA with the same version number can only be uploaded once. If you previously uploaded version 1.0 (build 1), uploading the same version again will result in error ITMS-90189 “Redundant Binary Upload.” The solution is to increment the Build Number in Xcode or your packaging tool and repackage. Apple requires that the combination of version number and build number must be unique for each upload.

Certificate Type Mismatch

An IPA signed with a development certificate cannot be submitted for release. It will be rejected by the system after upload, and the build will not appear. Confirm that you are using a Distribution (release certificate) and an App Store provisioning profile when packaging. Development certificates are only for testing on physical devices and cannot be used for release.

Bundle ID Must Match

The Bundle ID in the IPA must exactly match the Bundle ID of the app created in App Store Connect. If they do not match, the upload will fail, or the build will not appear. You can verify the Bundle ID setting in the configuration file of your packaging tool.

Troubleshoot and Re-upload with Appuploader

If the build does not appear after uploading with Appuploader, first check the upload logs to see if there are any errors. The upload interface supports switching channels; if one channel fails, you can try another. When using the command-line version, the log output is more detailed, making it easier to troubleshoot.

After identifying and fixing the issue, repackage, remembering to increment the version number or build number, and then upload again with Appuploader. Wait 10-30 minutes after uploading and refresh the build list page. If failures persist, carefully read the error codes in the email—most issues can be identified through the email information.