AppForShareCreate a free account

From your upload to TestFlight or Google Play, with one confirm tick

Pro (TestFlight and Google Play testing tracks) and Team (adds a Google Play production draft)

Most build tools end with a file: an App Store signed .ipa, an .aab. Getting it to TestFlight or a Google Play track then means Transporter, altool, fastlane, eas submit or a Play Console upload page. AppForShare takes the same file you already upload and sends it to the store with your own App Store Connect key or Google Play connection.

Nothing goes to a store on its own. An Admin of your workspace picks the destination and ticks a confirmation naming the app, version and track. After that, TestFlight tester sync, the App Store review card and the Google Play releases page take over.

Start freeSee plans

Example

Shop app 2.4.0

  • iOS (118), App Store .ipaSent to TestFlight, processed
  • Android (58), .aabInternal testing, saved
  • Android (58), productionDraft, roll out on the releases page
Sent by Sara (Admin) with the workspace's own keys.

Made for

  • Teams that build on EAS, Codemagic, Bitrise or a laptop and want one place for test links and store uploads
  • Agencies that upload builds to a client's App Store Connect or Play Console through a client store connection
  • Developers who want a record of who sent which build to the store

What it ends

  • Installing Transporter or fastlane on one machine just to upload
  • Sharing Play Console access to let someone upload an .aab
  • Not knowing who sent build 118 to TestFlight

How it works

  1. Step 1

    Upload the store build

    Upload the App Store signed .ipa or the .aab from the dashboard, the CLI or CI. AppForShare keeps the store file next to the build. An App Store .ipa has no install link, since it cannot be installed from one.

  2. Step 2

    Pick where it goes

    On the build page choose TestFlight for iOS, or a Google Play track for Android: internal, closed or open testing on Pro, and production as a draft on Team.

  3. Step 3

    Confirm and send

    An Admin ticks the confirmation. AppForShare sends the file with your own key and follows it until Apple has processed it or Google Play has saved the release.

After the upload

An iOS build appears in TestFlight once Apple has processed it. TestFlight tester sync (Team) and the App Store review card then work with it as with any other build of that version. A Google Play release lands on the track you picked; production is always saved as a draft that an Admin rolls out from the Google Play releases page.

Every send is kept with the person, the time and the result on the build page, in the release page timeline and in the store connection activity.

Next to eas submit, fastlane and GitHub builds

If eas submit or fastlane already uploads in your pipeline, keep it. This is for builds that end up in AppForShare anyway, and for teams who would rather not keep store credentials on a build machine. Builds AppForShare sets up on your own GitHub Actions can still go to TestFlight or Google Play straight from the runner.

Good to know

Questions

Which plan do I need?
Pro sends to TestFlight and to Google Play internal, closed and open testing. Team also saves a Google Play production release as a draft.
Who can send a build?
An Admin of the workspace, with a confirm tick. Developers can upload the file; sending it to a store needs an Admin.
Can testers install the App Store build from a link?
No. Apple does not allow it. Testers get it through TestFlight; use an ad hoc build for install links.
Can I do it from the CLI?
Yes, as an Admin: appforshare store-upload <build> --to testflight --yes, or --to play:internal --yes. The MCP server only reads the result.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

Create a free accountPricing

More features