Why your TestFlight build doesn't show up after a successful upload
You push, the build runs, the archive and export steps succeed, the upload step succeeds, the workflow finishes green. You open App Store Connect to check on it and TestFlight shows... the previous build. Not a failed build. Not a processing build. Nothing new at all. This one is genuinely confusing the first time it happens, because there's no error anywhere — everything you can see reports…
After a successful upload of your TestFlight build, it may not appear in App Store Connect. This can be confusing because there is no error message indicating a failed upload. The issue arises when the upload tool, such as xcrun altool or the newer transporter flows, reports the transfer as successful even though App Store Connect discards the result due to a duplicate build.
To prevent this problem, ensure that your build number changes with each upload, even if the marketing version remains the same. In GitHub Actions, use the `github.run_number` as the dynamic build number in the `CURRENT_PROJECT_VERSION` setting to maintain a unique build number for every upload.
If this issue persists, verify that the dynamic build number is being correctly substituted in the archive step. A common mistake is setting the environment variable in the wrong step or shell context, causing the $BUILD_NUMBER variable to expand to an empty value.
To confirm if this is your issue, check the Build Activity or processing history in App Store Connect instead of just the current builds list. Sometimes, the duplicate-version upload may not even appear there. Additionally, ensure that processing has not exceeded a few minutes; if it's only been a short time, it may still be processing.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
