## TL;DR
Stop waiting inside the upload job: upload with pilot configured to skip the processing wait, then poll App Store Connect separately or let a later step check status. Processing time varies from minutes to over an hour and the lane timeout kills an otherwise good upload. Split upload and wait into two steps, raise the wait timeout deliberately if you must block, and record the build number so the follow-up check polls the right build.

```text
fastlane pilot timed out waiting for build processing: timeout error workaround
```

## Use this when
- pilot uploads the build then the lane fails on a processing timeout.
- The build later appears in TestFlight fully processed despite the failed lane.
- Release pipelines stall for the full timeout on every run.

## Not for this skill when
- The upload itself never completes. That is a network or file size problem before processing starts.
- Processing genuinely never finishes. See the stuck processing skill for compliance and invalid binary checks.

## Steps
1. Confirm from App Store Connect that the supposedly failed build actually uploaded and is processing or ready. Verify: the build exists in TestFlight with the expected number
2. Change the pilot call to skip waiting for build processing, using the documented skip option in your Fastfile. Verify: the Fastfile shows the skip waiting setting on the pilot action
3. Add a separate polling step, in CI or a later lane, that checks build status with the recorded build number and a generous interval. Verify: the poller reports processing, then ready, for the same build number
4. If a blocking wait is truly required, set an explicit longer timeout on the wait action instead of the lane default. Verify: the configured timeout exceeds your observed worst processing time
5. Run the lane end to end. Verify: the upload lane finishes green right after upload and the poller confirms readiness separately
6. Note the build number and processing duration in the release log to size future timeouts from data. Verify: the log entry exists with both values
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
pilot waits by polling App Store Connect until processing finishes, and Apples processing time is highly variable. The default patience of the lane is shorter than bad-day processing, so the lane reports failure for a build that succeeds minutes later. Conflating upload success with processing completion inside one timed step is the design flaw.

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
### pilot skip_waiting_for_build_processing workaround
The named-option phrasing for the standard fix. 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.
### fastlane waiting for build processing timeout CI
CI phrasing; split upload and wait so the pipeline does not burn the full timeout. 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: compliance prompt blocks processing
If processing never completes rather than merely being slow, answer the export compliance prompt; no timeout setting fixes a blocked build. 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_A6ZefdlHjFHHMq8cg0PUqw