Few errors in iOS release engineering are as frustrating as ITMS-90034: Missing or invalid signature. You have compiled your application, packaged an .ipa archive, initiated an upload to App Store Connect, and after waiting through the transfer, Apple's Transporter ingestion service terminates the upload with a failure notice:
Asset validation failed (90034)
The bundle at "Payload/MyApp.app" is not signed using an Apple Submission Certificate.
Ensure you use the correct code signing identity and provisioning profile.
Closely paired with ITMS-90035 ("Invalid Signature: The signature contains invalid certificates or signature formats"), this error indicates a fundamental mismatch in your cryptographic signing chain.
This guide explains why ITMS-90034 occurs, shows how to prompt your AI assistant to diagnose project signing settings, provides verified terminal commands to inspect signatures locally on macOS, and walks through pre-upload binary inspection and delivery using FlightDeck.
Why Apple Ingestion Rejects Binaries with ITMS-90034
Every iOS application submitted to App Store Connect must be cryptographically signed with an Apple Distribution Certificate and linked to an App Store Provisioning Profile. Apple enforces rigorous structural and cryptographic checks during ingestion:
- Development vs. Distribution Certificate Mismatch: Compiling with an Apple Development certificate or an Ad-Hoc / Enterprise provisioning profile causes ITMS-90034 immediately upon ingestion.
- Missing Apple Worldwide Developer Relations (WWDR) Intermediate Certificate: If your local macOS Keychain lacks the active Apple WWDR Intermediate Certificate (such as WWDR G3, G4, or G6), the certificate trust chain cannot be verified, rendering your distribution signature untrusted.
- Mismatched Bundle Identifier: The
CFBundleIdentifierdeclared inInfo.plistdoes not match the App ID embedded inembedded.mobileprovision. - Nested Framework / Dylib Signature Inconsistencies: Embedded dynamic frameworks (
Frameworks/.dyliborFrameworks/.framework) were signed with different team identities, contain conflicting bundle identifiers, or lack their own valid_CodeSignaturedirectory. - Debug Entitlements Present (
get-task-allow = true): If the binary allows debugger attachment, Apple's servers reject it as a development build.
FlightDeck Technical Boundary: FlightDeck does not generate private keys or sign binaries. Code signing is performed strictly by Apple build tools (codesign, xcodebuild) on your host machine prior to packaging the .ipa. FlightDeck's role is to inspect archive package structure offline before upload and deliver verified binaries to App Store Connect.
Diagnosing Code Signing Issues with Your AI Coding Assistant
When an upload fails due to ITMS-90034, you can ask your AI coding assistant in Cursor, Claude Code, or Antigravity to examine your project configuration and identify the root cause.
Diagnostic Prompt
Copy and paste this prompt into your connected AI coding assistant:
My iOS archive upload failed with Apple error ITMS-90034 (Invalid Signature). Help me diagnose the code signing configuration in my project. Check my Xcode build settings or signing identities, inspect the embedded provisioning profile and entitlements, and verify that all embedded frameworks are signed with the same distribution identity.
Your assistant will examine your project configuration files (such as project.pbxproj, ExportOptions.plist, or Fastlane configurations) and highlight mismatched identities, development certificates, or improper signing styles.
Local Terminal Diagnostics: Inspecting the Signature Chain
Before attempting another upload, you can inspect the extracted application bundle directly on your macOS workstation using native tools.
Inspect the Extracted .app, Not the .ipa: An .ipa file is a ZIP archive. Running codesign directly on an .ipa file returns an error: bundle format is unrecognized, invalid, or unsuitable. Always unpack the .ipa container and inspect the application bundle located inside the Payload/ directory.
1. Verify the Embedded Code Signing Identity
Unpack your .ipa into a clean temporary directory and inspect the Mach-O binary signature using macOS codesign:
# Create a clean temporary workspace and extract the archive
rm -rf /tmp/inspect_ipa
mkdir -p /tmp/inspect_ipa
unzip -q "MyApp.ipa" -d /tmp/inspect_ipa
# Inspect detailed signature metadata of the extracted .app bundle
codesign -dv --verbose=4 /tmp/inspect_ipa/Payload/*.app
Review the output for these key fields:
Executable=/tmp/inspect_ipa/Payload/MyApp.app/MyApp
Identifier=com.company.myapp
Format=app bundle with Mach-O thin (arm64)
CodeDirectory v=20500 size=18492 flags=0x0(none) hashes=570+5 location=embedded
Signature size=9055
Authority=Apple Distribution: Your Company Name (TEAMID1234)
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Nov 1, 2026 at 10:15:30 AM
If the top authority displays Apple Development: ... or iPhone Developer: ..., Apple's Transporter will reject the package with ITMS-90034. In modern Xcode workflows, Apple uses the unified Apple Distribution: [Name] ([Team ID]) certificate format.
2. Verify Nested Dynamic Frameworks
While codesign --verify --deep provides a quick baseline check, Apple's official Code Signing Guide (TN3126) warns that --deep applies the same flags indiscriminately and is not a substitute for inspecting individual nested components during troubleshooting. Check overall bundle satisfaction and inspect embedded frameworks:
# Verify bundle integrity
codesign --verify --deep --strict --verbose=2 /tmp/inspect_ipa/Payload/*.app
# Inspect each embedded dynamic framework directly
for fw in /tmp/inspect_ipa/Payload/*.app/Frameworks/*; do
if [ -e "$fw" ]; then
echo "=== Inspecting $(basename "$fw") ==="
codesign -dv --verbose=4 "$fw"
fi
done
This reveals whether an embedded third-party SDK or dynamic library was signed with a mismatched identity or lacks an embedded signature.
3. Inspect the Provisioning Profile and get-task-allow
Decode embedded.mobileprovision to confirm that the profile type is production:
security cms -D -i /tmp/inspect_ipa/Payload/*.app/embedded.mobileprovision > /tmp/profile.plist
plutil -p /tmp/profile.plist | grep -E "(Name|TeamIdentifier|application-identifier|get-task-allow)"
Expected output for App Store distribution:
"TeamIdentifier" => [
0 => "TEAMID1234"
]
"application-identifier" => "TEAMID1234.com.company.myapp"
"get-task-allow" => 0
get-task-allow determines whether a debugger can attach to the process. For production App Store and TestFlight builds, get-task-allow must be 0 (false). A value of 1 (true) indicates a development build and triggers ITMS-90034.
Resolving Common Signing Failures: Re-Export vs. In-Place Patching
Do Not Patch Signed Bundles In Place: Never attempt to resolve signing errors by manually modifying, adding, or deleting files inside an already-signed .app bundle. Modifying bundle contents invalidates the sealed resource manifest in _CodeSignature/CodeResources. Always fix the signing configuration in your build project and export a fresh, signed .ipa.
1. Native Xcode Projects
- In Xcode, select the application target and open Signing & Capabilities.
- If using Automatically manage signing, verify the correct Team is selected. When creating an archive, select Product > Archive, then use the Organizer's Distribute App flow to export with App Store distribution.
- If using Manual signing, ensure the Release build configuration specifies an App Store distribution profile and Apple Distribution signing identity.
2. Flutter Pipelines
When packaging Flutter apps for App Store Connect, ensure you build a release archive with an export options configuration:
flutter build ipa --release --export-options-plist=ExportOptions.plist
Your ExportOptions.plist must specify App Store distribution:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store</string>
<key>teamID</key>
<string>TEAMID1234</string>
<key>signingStyle</key>
<string>automatic</string>
<key>uploadSymbols</key>
<true/>
</dict>
</plist>
3. Missing Apple WWDR Intermediate Certificates
If codesign reports CSSMERR_TP_NOT_TRUSTED or errSecInternalComponent, your macOS Keychain may be missing intermediate authority certificates.
- Open the macOS Keychain Access app.
- Select the login keychain and check Certificates.
- Download the active Apple Worldwide Developer Relations Intermediate Certificates (G3, G4, or G6) from developer.apple.com/certificates and install them.
Pre-Upload Verification and Staging the Replacement with FlightDeck
Once the binary is rebuilt and signed with your distribution certificate, use FlightDeck through your AI coding assistant to inspect package structure offline before delivering it to Apple.
Pre-Upload Inspection Prompt
Inspect the rebuilt archive at [path/to/MyApp.ipa] using FlightDeck. Verify the bundle ID, version string, and package integrity, and stage an upload to App Store Connect when ready.
FlightDeck inspects the .ipa archive offline, confirming:
- The ZIP structure contains a valid
Payload/*.appbundle. CFBundleIdentifiermatches your registered App Store Connect application.CFBundleShortVersionStringandCFBundleVersionare properly formatted.- Target platform matches your App Store Connect application container.
Approval Center: Staging the Upload
When your assistant proceeds to deliver the verified binary, FlightDeck intercepts the mutating network request and stages it for your review. FlightDeck Desktop displays the Approval Center sheet:
Illustrative representation of the FlightDeck Approval Center sheet:
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â FlightDeck Desktop â Operation Approval Request â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ¤
â Operation: Deliver iOS Binary (.ipa) â
â Target App: [Your App Name] (App ID: 6812899314) â
â Binary Path: /path/to/MyApp.ipa â
â Version: 1.0.0 (Build 44) â
â Platform: iOS â
â Action: Upload binary parts to Apple Ingestion Storage â
â Impact: Stages build for Apple server processing. â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ¤
â [Reject Proposal] [Approve & Execute] â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Review the target app, version, and file path in FlightDeck Desktop, then click Approve & Execute. FlightDeck dispatches the multi-part upload to Apple's ingestion storage.
Summary Checklist and Related Resources
| Checkpoint | Requirement | Verification Method |
|---|---|---|
| Signing Authority | Must be Apple Distribution (not Development). |
codesign -dv --verbose=4 /tmp/inspect_ipa/Payload/*.app |
| Debugger Attachment | get-task-allow must be 0 (false). |
security cms -D -i .../embedded.mobileprovision |
| Nested Frameworks | All frameworks in Frameworks/ must match identity. |
codesign -dv --verbose=4 .../Frameworks/* (TN3126) |
| Pre-Upload Check | Valid ZIP container, bundle ID, and version match. | Conversational prompt to FlightDeck |
| Upload Delivery | Approved in FlightDeck Desktop Approval Center. | FlightDeck Desktop Approval Center sheet |
Related Resources
- Pre-Upload Binary Inspection: How FlightDeck Validates .ipa Files
- Uploading React Native and Expo IPAs to App Store Connect with AI
- From 'flutter build ipa' to App Store Connect: Automated Pipeline
- Why Is My TestFlight Build Stuck on Processing? Causes and Fixes
- Apple Developer: Code Signing Troubleshooting