Preflight, upload, and processing
ProductionDirect deployment uploads an existing configured binary; it does not rebuild it or guarantee store publication.
What you need
A signed IPA/APK/AAB, exact identifier match, valid store credentials, a matching store application, and acceptable version identity.
What LaunchLayer does
Validates preflight, blocks mismatches and invalid signatures, prevents accidental duplicate active uploads, preserves job history, supports actionable retry or result recovery, and monitors processing.
What you still need to do
Resolve store-side requirements, complete declarations and review, manage testing tracks or rollout, and wait for store processing.
Common problems
Invalid credentials, wrong bundle ID or package name, duplicate version/build number, expired profile, failed runner, missing result artifact, or delayed processing. Retry creates a new attempt; it does not overwrite history.