Skip to main content

Troubleshooting and Required Screenshots

If you encounter issues exporting or uploading your iOS distribution build, please provide the screenshots below. They help us verify signing, export configuration, and Transporter behavior.

A) Signing configuration (critical)​

1) Xcode — Signing & Capabilities (Release / Distribution)​

Capture:

  • Xcode → Project → Target → Signing & Capabilities
  • Release configuration selected

Must show clearly:

  • Bundle Identifier
  • Team
  • Signing certificate (Apple Distribution)
  • Selected Distribution provisioning profile
  • “Automatically manage signing” setting

Why this matters: confirms the app is signed with the correct team, certificate, and provisioning profile.

2) Xcode — Build Settings (Code Signing)​

Capture:

  • Xcode → Target → Build Settings
  • Filter: Code Signing

Must show clearly:

  • Code Signing Identity (Release)
  • Provisioning Profile (Release)
  • Development Team

Why this matters: ensures no conflicting signing settings override the intended configuration.

B) Archive and export process​

3) Xcode Organizer — Archive summary​

Capture:

  • Xcode → Organizer
  • Selected archive

Must show clearly:

  • App name
  • Bundle ID
  • Version and build number
  • Archive date

Why this matters: verifies the archive was created correctly and matches the intended app.

4) Xcode — Distribution method selection​

Capture screens from the Distribute App flow showing:

  • Custom selected
  • App Store Connect selected
  • Export selected (not Upload)

Why this matters: confirms the correct export path for Transporter.

C) Transporter upload​

5) Transporter — App loaded screen​

Capture Transporter after the IPA is added.

Must show clearly:

  • IPA file name
  • App name
  • App Store Connect organization name shown at the top

Why this matters: shows which App Store Connect context Transporter is using during upload.

6) Transporter — Full error message (if any)​

Capture the complete error dialog/panel so we can see all error text.

Why this matters: Transporter errors usually pinpoint permission, bundle ID, or account mismatches.

Notes on sensitive information​

  • Do not share passwords, API keys, or private keys
  • Do not share certificate or provisioning profile files as screenshots
  • Screenshots may include app names, bundle IDs, and version numbers (this is OK)

Minimum required screenshots (if time is limited)​

If you can’t provide everything, please send at least:

  1. Signing & Capabilities (Release)
  2. Organizer archive summary
  3. Transporter error message

This set is usually sufficient for initial diagnosis.