The BUILD_UPLOAD_STATE_UPDATED event fires when the processing state of an uploaded build changes. After you upload a build through Xcode or CI, Apple processes it — this event tells you when that processing completes, fails, or reaches a new state.
When does it fire?
This event triggers on build processing transitions:
- Processing — Apple is processing the uploaded build
- Failed — the build failed processing (common causes: missing entitlements, invalid provisioning, code signing issues)
- Valid — the build passed processing and is ready for testing or submission
- Invalid — the build was flagged as invalid during processing
Payload highlights
The payload includes the app ID, build number, version string, the processing state, and the platform (iOS, macOS, tvOS, etc.). For failed builds, the payload often includes enough context to understand what went wrong.
How Yeethook helps
Build processing can take anywhere from a few minutes to over an hour. Instead of refreshing App Store Connect, Yeethook sends a Slack message the moment processing completes. If a build fails, your team knows immediately and can fix the issue.
Common use cases
- Get notified when your CI build finishes processing on Apple's servers
- Catch build processing failures before they block your release
- Track build processing times across multiple apps
- Alert QA when a new build is ready for TestFlight testing