AppForShareCreate a free account

iOS and Android builds on GitHub Actions, without writing the workflow

Pro (up to 2 repositories) and Team (no repository limit)

Writing a mobile build workflow is a week of trial and error: signing, profiles, build numbers, Gradle signing properties, upload steps. AppForShare writes it for you from a short form, stores the secrets in your repository and opens one pull request. You read it and merge it.

The builds run on your own GitHub Actions minutes. Your code stays in your repository and your runner; AppForShare never builds on its own machines and never reads your code. When a run fails, it reads only that run's log, to explain the failure.

Example

acme/shop-app

  • iOS, TestFlightBuild 2611011042 uploaded
  • Android, Play internalVersion code 58 sent
  • iOS, testersRunning, 6 min
  • Android, testersFailed: keystore secret missing, 3 fix steps
  • Runner minutesYour GitHub account or your own runner
Status by GitHub webhook. Up to 3 runs at a time per repository.

Made for

  • Small teams and solo developers who want a real pipeline without becoming CI experts
  • Agencies that build several client apps and want the same setup in every repository
  • React Native, Flutter and native projects (Node.js and setup commands are part of the form)

What it ends

  • Copying a workflow from a blog post and fixing signing errors for days
  • Building on one laptop, so nobody else can ship when that person is away
  • Remembering to bump build numbers and version codes by hand
  • Uploading the .ipa or .aab yourself after every build

How it works

  1. Step 1

    Install the GitHub App

    Install "AppForShare Builds" on the repositories you pick. We check with GitHub that you can see that installation before it joins your workspace.

  2. Step 2

    Fill a short form

    iOS: scheme, configuration, Xcode version and where the build goes. Android: Gradle folder, module, variant, Java version and where the build goes. Pick the branch, the Node.js version and how build numbers are set.

  3. Step 3

    Merge one pull request

    We store the secrets and open a pull request from our own branch with one workflow file. We never push to your other branches and never merge.

  4. Step 4

    Start a build

    Press Build in the dashboard with release notes and a channel. Status comes back from GitHub as the run moves, and the result lands where you chose.

Where a build can go

iOS builds go to your testers as an AppForShare install link (ad hoc export, with every registered device in the profile), or to TestFlight with your App Store Connect key. Android builds go to your testers as an .apk link, or to a Google Play track as an .aab: internal, closed, open or production.

For Google Play, the runner uploads the .aab straight to Google. The file never passes through AppForShare servers; we open the upload and check the version code and SHA-256 in Play before the release is saved. A production release is always saved as a draft that you roll out in Play Console.

Signing that you control

iOS can use Xcode automatic signing with your App Store Connect key, or your own Apple Distribution certificate as repository secrets with manual signing on the app target. With manual signing we keep the matching profile in a secret before each run.

Android signs with your upload keystore, which you add as four GitHub secrets yourself. AppForShare never sees the keystore or its passwords. If your Gradle files already sign, choose that instead.

Why a build failed, in plain words

When a run fails or times out, AI reads the end of the failed job's log, with keys, tokens and passwords taken out first, and tells you the likely cause and the steps to fix it, such as an expired profile or a missing keystore secret. It shows under the run and in one email to the person who started it, for 1 AI action. It only reads; it never changes your code, the workflow or the repository, and never opens a pull request.

It also names the kind of failure (signing, profile, certificate, Xcode, Gradle, keystore, dependencies, a compile error, tests, the runner, the time limit, secrets or build settings), the step that failed and how sure it is. Ask again with Explain the failure in the dashboard, appforshare github-runs <run> --explain in the CLI, or from an AI tool through the MCP server.

Your own runners

Run builds on a Mac of your own, a Bitrise Build Hub machine pool (labels such as bitrise-m4-pro) or another runner vendor by giving up to 6 runs-on labels instead of a GitHub hosted machine. The workflow then skips the hosted disk clean up, so nothing on your machine is deleted, and the pull request says the workflow runs on your own runner.

Expo projects without native folders

An Expo project with app.json or app.config and eas.json, but without ios and android folders, gets an Expo preset: the workflow runs npx expo prebuild for the platform first, then builds the generated Xcode workspace or Gradle project as usual. Builds run on your own GitHub Actions minutes, not on Expo's machines, so there is no Expo build queue to wait in and no build credit to spend.

Flutter apps, iOS without a Mac of your own

A Flutter app gets a Flutter preset: the workflow sets up Flutter (the version pinned in .fvmrc, .flutter-version or pubspec.yaml, else the latest stable), runs flutter pub get, and builds with the Flutter tool. iOS is archived and signed on a GitHub macOS runner with your App Store Connect key, Android is built with flutter build apk or appbundle and your upload keystore. Version, build number, flavor and target file are part of the form. Builds run on your own GitHub Actions minutes.

Install links on the pull request

Builds started from a pull request branch, and uploads from the GitHub Action with pr-comment: true, keep one comment on the pull request with the iOS and Android install links, their QR codes, the store readiness result and the channel. Each new run updates the same comment instead of adding another, so reviewers install the build that matches the code they read.

Build numbers without thinking

Keep the number from the project, use the time (yymmddHHMM in UTC) or the run number, and override it for a single run when you need to. On Android the version code and version name are set by a small Gradle init script, so your Gradle files do not change.

Good to know

Questions

Do you build my app on your servers?
No. Every build runs on GitHub Actions in your own GitHub account, on your minutes. AppForShare writes the workflow, stores the secrets it needs and receives the result.
Can I read the workflow before it runs?
Yes. It arrives as a pull request with one file, .github/workflows/appforshare-ios.yml or appforshare-android.yml. Nothing runs until you merge it, and it only runs when someone starts a build.
Does it work with React Native and Flutter?
Yes. For React Native, pick the Node.js version and add setup commands such as npm ci and pod install. Flutter apps get a Flutter preset that sets up Flutter and builds with the Flutter tool, with your Flutter version, flavor and target file.
Does it work with Expo?
Yes. Expo projects without native folders get a preset that runs expo prebuild before the build. If you keep building on EAS instead, Connect Expo sends those builds to testers.
What does the AI see when a build fails?
The lines around the errors and the end of the failed job's log, at most 12,000 characters, with private keys, tokens, passwords, signed URLs, long random strings and email addresses taken out before it is sent. It does not see your code.
Can builds run on Bitrise Build Hub or my own Mac?
Yes. Give the runs-on labels of your runner in the setup instead of a GitHub hosted machine, on Pro and Team.
Which plan do I need?
Pro includes builds for up to 2 repositories. The iOS and Android setup of one repository count once. Team has no repository limit. Own runners and failure explanations are on both, and each explanation uses 1 AI action.

Read next

Try it on your own app

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

More features