Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • đź””Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Set up
  • Navigate to the Integration settings view
  • Connect App Store Connect
  • Email forwarding

Was this helpful?

  1. Integrations
  2. App stores

App Store Connect

PreviousApp storesNextGoogle Play Console

Last updated 7 days ago

Was this helpful?

Set up

Navigate to the Integration settings view

  1. Select an app in the top left corner from the Switcher

  2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

  3. Click on Integrations in the sidebar

Connect App Store Connect

  • Find the App Store Connect integration module under the App store section

  • Click the Connect button

  • Enter your ASC API key’s Key ID and Issuer ID, and upload the .p8 key file

  • Click Save; you’ll be presented with a dialog in which to select the bundle ID of your app

You can generate API keys within App Store Connect.

  • You must be logged into App Store Connect with an Admin account to generate API keys.

  • Runway requires an API key with the App Manager role.

Email forwarding

You can set up forwarding from an inbox on your team’s side that receives emails from Apple about your apps, to a specially configured inbox on the Runway side, to have Apple communications forwarded into Slack or Teams by Runway (if you enable the corresponding notification type).

Specific steps to set up email forwarding will depend on your team’s email provider and any company-specific settings, but you’ll use the info below.

Forward emails from

Apple sends developer communications from many email addresses, so it is safest to forward from any addresses ending in apple.com. But if your team wishes to scope this more, here are the most commonly used Apple addresses:

developer@insideapple.apple.com

no_reply@email.apple.com

donotreply@apple.com

developer@email.apple.com

do_not_reply@apple.com

Forward emails to

forwarding+<Forwarding ID>@runway.team

The Forwarding ID to use will be surfaced in the App Store Connect integration module once you connect the integration.

⚙️
đź”—
Apple - Creating API Keys for App Store Connect API
Issuer ID, Key ID, and download link from the Users and Access section in App Store Connect