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
  • Available actions:
  • Selected build in app store
  • (iOS) App review information
  • App store review automations
  • App submission checklist

Was this helpful?

  1. Using Runway
  2. Releases

App store review

PreviousApp submissionNextRelease

Last updated 1 year ago

Was this helpful?

From the App store review step (which may appear as “App Store review”, “Play Store review”, etc depending on your selected distribution platform), you can quickly see the status of your app update as it goes through the store review process.

Available actions:

  • (iOS) Developer Reject — Pull your in-progress submission from the review queue.

  • (Android) Mark submission rejected by Google — Manually flag a submission as having been rejected by Google.

A note on Google review: Because of a limitation with the Google Play Publishing API, Runway is unable to differentiate between updates that are in review with Google and those that have been released to the Google Play Store. Because of this, when you submit an Android build for review, Runway's Submission, Review, and Release steps will appear ready (green), though they may still be in review with Google.

Due to a limitation with the Google Play Publishing API, Runway cannot offer support for Managed Publishing. If you have Managed Publishing enabled on the Google Play Console, you must manually publish updates from there. Additionally, the status of an update may appear as Released or Staged Rollout In Progress in Runway even if it has not yet been made available for users via the Play Console.

Selected build in app store

The selected build module indicates which build was submitted for review, as well as its matching CI build identifier. This module will only appear after your app update has been submitted for review.

The selected build can’t be changed after your app update has been submitted for review. If needed, you can Developer Reject the current submission to select a different build, and then re-submit for review.

(iOS) App review information

Here, you can view and edit key information that will be passed along to Apple’s reviewers.

  • Contact: Information for the contact person in your organization if the App Review team needs additional information.

  • Sign-in required: Sign-in information for a demo account, if relevant.

  • Review notes: Additional information about your app that can help during the review process.

  • Review attachment: The review attachment file that will be made available to reviewers, if present.

App store review automations

You can configure the following App store review automations by visiting the Automations tab on this step:

App submission checklist

You can add checklist items to this step by visiting the Checklist tab.

For more details on App review information, visit .

cover any unique parts of your team's release process and live across all your releases. Steps with checklist items won't be marked as complete (green) in Runway until all checklist items have been completed (in addition to the normal criteria that would mark a step as completed).

🎛️
🔗
Apple’s documentation
Checklist items
(iOS) Apply default review attachment to new app versions in App Store Connect