Before you can track a store submission with a Launch, you need to tell TestApp.io where you publish your app. Publishing Destinations are configured store connections that represent the places where your app is distributed — such as the Apple App Store, Google Play Store, or TestFlight.

What Are Publishing Destinations?

A Publishing Destination is a configured record of a store or distribution channel where you submit your app. Each destination includes a name, store type, and platform.

Once set up, destinations are reusable across all your versions and launches. You configure them once, then select them whenever you create a new Launch.

Setting Up Destinations

  1. Open TestApp.io and go to Team Settings.
  2. Navigate to Publishing Destinations.
  3. Click New Destination.
  4. Configure the destination:
    • Name — A descriptive label for this destination (e.g., "Production App Store" or "Internal TestFlight").
    • Store type — The type of store (Apple App Store, Google Play Store, TestFlight, etc.).
    • Platform — The platform this destination targets (iOS or Android).
  5. Save the destination. It is now available to use in any Launch.

Available Store Types

TestApp.io supports the most common mobile app distribution channels:

  • Apple App Store — For production releases to iOS and iPadOS users worldwide.
  • Google Play Store — For production releases to Android users.
  • TestFlight — For beta distribution to iOS testers through Apple's TestFlight program.
  • Custom destinations — For other distribution channels specific to your workflow, such as enterprise distribution or regional stores.

Choose the store type that matches where you are submitting your app. The store type helps TestApp.io categorize your submissions and provide relevant context when tracking launches.

Linking Destinations to Launches

Publishing Destinations connect to your release workflow through Launches:

  1. Navigate to a version and click New Launch.
  2. Select the publishing destination you want to submit to from the list of configured destinations.
  3. The Launch is now linked to that destination, and your submission will be tracked against it.

This link gives your team clarity on exactly where each submission is going, and it builds a submission history for each destination over time.

Submission History

Every time you create a Launch linked to a destination, it becomes part of that destination's submission history. Over time, this gives you a complete record of every version you have submitted to each store.

To view submission history:

  1. Go to Team Settings and open Publishing Destinations.
  2. Select a destination.
  3. View the list of all past Launches linked to this destination, including their statuses and dates.

Submission history is valuable for audits, retrospectives, and understanding your release cadence per store.

Managing Multiple Destinations

Most teams publish to more than one store. Here are common setups:

  • Standard mobile app: One App Store destination + one Google Play destination.
  • Beta program: Add a TestFlight destination for iOS betas alongside your production destinations.
  • Multiple regions or tracks: Create separate destinations for different Play Store tracks (e.g., "Google Play Production" and "Google Play Internal Testing").
  • Enterprise distribution: Add a custom destination for internal enterprise distribution channels.

There is no limit to how many destinations you can configure. Set up as many as your distribution workflow requires.

Tips

  • Set up all your destinations early. Configure your publishing destinations when you first set up your team in TestApp.io. This way, they are ready to go when you create your first Launch.
  • Use clear, descriptive names. Names like "iOS App Store - Production" or "Google Play - Internal Track" make it easy to pick the right destination when creating a Launch.
  • Review submission history after each release cycle. Use the history to understand your submission patterns and identify bottlenecks in your release process.
  • Pair destinations with Playbooks. Use platform-specific Playbooks alongside the matching destination to ensure every submission follows the right checklist.

Need help? Contact us and we'll get back to you shortly.