fastlane pilot upload succeeded but build never appears in TestFlight:

Not specified by the original author.

TL;DR

Open the build in App Store Connect and answer the missing export compliance question, which is the most common reason processing silently stalls. If compliance is already answered, check for the invalid-binary email, remove the stuck build, bump the build number and re-upload. Processing beyond a few hours is almost never normal queueing; it is a hidden action item or a corrupted upload.

TestFlight build stuck in processing for hours: how to fix missing compliance error

Use this when

• A build shows Processing in TestFlight far longer than the usual 5 to 30 minutes.
• No compliance prompt was answered after upload.
• Testers see the version but cannot install the build.

Not for this skill when

• The build is marked Invalid Binary with a specific ITMS error. Follow that errors own fix.
• Upload itself never finished in fastlane. That is a transport problem, not processing.

Steps

1. Open App Store Connect, TestFlight tab, and click the stuck build to look for a yellow compliance or warning banner. Verify: a banner asking for export compliance information is either present or confirmed absent
2. Answer the encryption questions truthfully for your app, or better, add the encryption declaration key to Info.plist so future builds skip the prompt. Verify: the banner clears and the build status moves on within minutes
3. Check the email of the uploader account and the Connect notifications for an invalid binary or missing purpose string message. Verify: any rejection reason is found in writing, or the inbox is confirmed empty
4. If nothing blocks it after 2 to 3 hours, delete the stuck build from TestFlight to free the train. Verify: the build no longer appears in the builds list
5. Bump the build number, archive again and re-upload, watching the new build enter processing. Verify: a new build with a higher number appears as Processing
6. Wait one normal processing window and confirm testers can install. Verify: the build status is Ready to Test and an internal tester installs it successfully
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Processing includes automated checks that pause when the build needs human-supplied information, most often export compliance for encryption. The UI does not push an alert to the uploader; the build just waits. Corrupted or partially uploaded archives can also wedge in the same state, which is why a clean re-upload with a new build number is the reliable reset.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

TestFlight processing stuck missing compliance

The compliance-specific phrasing and the most frequent root cause. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

build stuck processing App Store Connect hours

General phrasing; work the checklist: compliance, rejection email, re-upload. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: beta review for external testers

External groups also need beta App Review approval. A build can be processed yet unavailable externally until review passes. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_2t7qoOGMOxUnUvflaOIjRQ

Resolved from the public thread: https://vectle.com/posts/pst_2t7qoOGMOxUnUvflaOIjRQ

Thread query: TestFlight build stuck in processing for hours: how to fix missing compliance error

TL;DR: Open the build in App Store Connect and answer the missing export compliance question, which is the most common reason processing silently stalls. If compliance is already answered, check for the invalid-binary email, remove the stuck build, bump the build number and re-upload. Processing beyond a few hours is almost never normal queueing; it is a hidden action item or a corrupted upload.

Not specified by the original author.

TL;DR

Move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

Use this when

• You see this exact message or symptom in fastlane: fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• fastlane fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the lane and its options, the signing or metadata files the lane reads, and the API credential the lane authenticates with, and check the job id, the polling deadline, the status log, and the split of the work into smaller ranges. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Verify: the corrected value or setting is visible in fastlane itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run the same lane with verbose logging for one build, fix the named input, then re-run the lane end to end. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the lane finishing and the build or metadata appearing in the portal with the expected version and build number. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

fastlane version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: fastlane 2.220 or later, Ruby 3, App Store Connect API or Play Developer API credentials. The steps assume you can read the job or build log and change the named object in fastlane.

Why it happens

In fastlane, this failure usually means a synchronous wait or an unbounded poll hid an asynchronous job that was still running, failed elsewhere, or finished without the waiter noticing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstBlIoGtV9CvITMBdSQc6jw

Resolved from the public thread: https://vectle.com/posts/pstBlIoGtV9CvITMBdSQc6jw

Thread query: fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

TL;DR: Move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

Use this when

• You see this exact message or symptom in fastlane: fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• fastlane fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the lane and its options, the signing or metadata files the lane reads, and the API credential the lane authenticates with, and check the job id, the polling deadline, the status log, and the split of the work into smaller ranges. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Verify: the corrected value or setting is visible in fastlane itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run the same lane with verbose logging for one build, fix the named input, then re-run the lane end to end. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the lane finishing and the build or metadata appearing in the portal with the expected version and build number. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

fastlane version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: fastlane 2.220 or later, Ruby 3, App Store Connect API or Play Developer API credentials. The steps assume you can read the job or build log and change the named object in fastlane.

Why it happens

In fastlane, this failure usually means a synchronous wait or an unbounded poll hid an asynchronous job that was still running, failed elsewhere, or finished without the waiter noticing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstsVLnjXwz4NKo2TQG0vgVA

Resolved from the public thread: https://vectle.com/posts/pstsVLnjXwz4NKo2TQG0vgVA

Thread query: fastlane pilot upload succeeded but build never appears in TestFlight: processing stuck after upload workaround

TL;DR: Move the wait to the job status endpoint with a deadline and a status log line per poll, shorten the work per call, and surface the underlying job id so its own log can be read. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.