Fastlane

Ship on Every Fastlane Run

Q: How do I keep my API key out of the Fastfile?

Set it as an ENV variable, either in a gitignored .env file locally or as a CI-provided environment variable, Fastlane's own recommended approach for any key.

Q: Does Fastlane need a specific CI service to run this?

No, that's the point. Run fastlane release from your terminal, or trigger it from whatever CI you already use.

Q: Can I add release notes automatically?

Yes, using the --notes flag on the upload command, either a static string or a value pulled from Fastlane's own build metadata.

Q: Does the sh action run from my project root?

No, it runs from inside the fastlane folder by default, worth accounting for in your file paths.

Drop a few lines into your Fastfile, and whichever lane builds your release now pushes it to AppShare too, no separate tool bolted on.

Connect to Fastlane

What You Get

Three Reasons Teams Automate This Step

Fits an Existing Lane

Add it to the release lane you already run, instead of standing up something new.

Works Anywhere Fastlane Does

Standalone from your terminal, or inside whatever CI is already calling Fastlane, same two lines either way.

No Separate Secrets Setup

Use the same ENV variable approach Fastlane already recommends for every other key you're managing.

SETUP

Add It to Your Fastfile

Use Fastlane to upload Android/iOS builds to AppShare in your existing lanes.

Open your Fastfile

Step 1

Find it in the fastlane/ folder at your project root.

Set your API key in .env

Secret

Add APPSHARE_TOKEN to fastlane/.env or set it in your CI environment.

Add the commands to a lane

Lane

Add the upload_to_appshare lane to trigger the CLI upload.

Commit & Run

Deploy

Run your lane locally or push to trigger your CI workflow.

Step 1 of 4

Step 1

Open your Fastfile

Open fastlane/Fastfile in your repository.

fastlane/Fastfile

default_platform(:android)

platform :android do
  # Your existing lanes
end

LIFECYCLE

What Actually Happens on a Push

The Lane Runs

Triggered manually, or by whatever CI step already calls fastlane release

Fastlane Builds the App

The lane runs its build action, gradle or gym, producing the actual file.

AppShare CLI Installs

The sh action installs AppShare CLI fresh, right after the build action finishes.

Build Gets Pushed

The CLI reads the ENV variable and uploads the file the build action just produced.

UNDER THE HOOD

Fastlane Just Runs the CLI

Those two lines in the lane are just AppShare CLI, running inside Fastlane instead of your terminal.

SEE CLI SETUP

Other Platforms

AppShare Works With Your Pipeline Too

GitLab CI/CD

Add a job to your .gitlab-ci.yml that pushes a build the moment your pipeline reaches it.

Learn More

Bitrise

Drop AppShare into a Bitrise workflow as a step, right alongside your existing build and test stages.

Learn More

Jenkins

Add an AppShare step to a Jenkins pipeline, scripted or declarative.

Learn More

CircleCI

Push a build from a CircleCI job as part of your existing config.

Learn More

Xcode Cloud

Trigger an AppShare release from an Xcode Cloud workflow, without leaving Apple's own CI environment.

Learn More

GitHub Actions

Trigger a release directly from a workflow file, on push, pull request, or tag.

Learn More

FAQ

Questions About the Fastlane Integration

Where does the AppShare code go?

Inside a lane in your Fastfile, the same file already handling your build and signing steps.

Does Fastlane need a specific CI service to run this?

No, that's the point. Run fastlane release from your terminal, or trigger it from whatever CI you already use.

Can I add release notes automatically?

Yes, using the --notes flag on the upload command, either a static string or a value pulled from Fastlane's own build metadata.

What happens if a step in the lane fails?

Fastlane stops the lane at that point, the same as any other action failing partway through.

Is Fastlane integration included on the Free plan?

It's bundled with CI/CD access generally, available from Free onward, nothing extra to unlock.

How do I keep my API key out of the Fastfile?

Set it as an ENV variable, either in a gitignored .env file locally or as a CI-provided environment variable, Fastlane's own recommended approach for any key.