Easily build and sign your app using gym


gym is part of fastlane: The easiest way to automate beta deployments and releases for your iOS and Android apps.

What's gym?

gym builds and packages iOS apps for you. It takes care of all the heavy lifting and makes it super easy to generate a signed ipa or app file :muscle:

gym is a replacement for shenzhen.

Before gym

xcodebuild clean archive -archivePath build/MyApp \
                         -scheme MyApp
xcodebuild -exportArchive \
           -exportFormat ipa \
           -archivePath "build/MyApp.xcarchive" \
           -exportPath "build/MyApp.ipa" \
           -exportProvisioningProfile "ProvisioningProfileName"

With gym

fastlane gym

Why gym?

gym uses the latest APIs to build and sign your application which results in much faster build times.

Gym Features
:rocket: gym builds 30% faster than other build tools like shenzhen
:checkered_flag: Beautiful inline build output
:book: Helps you resolve common build errors like code signing issues
:mountain_cableway: Sensible defaults: Automatically detect the project, its schemes and more
:link: Works perfectly with fastlane and other tools
:package: Automatically generates an ipa and a compressed dSYM file
:bullettrain_side: Don't remember any complicated build commands, just gym
:wrench: Easy and dynamic configuration using parameters and environment variables
:floppy_disk: Store common build settings in a Gymfile
:outbox_tray: All archives are stored and accessible in the Xcode Organizer
:computer: Supports both iOS and Mac applications




fastlane gym

That's all you need to build your application. If you want more control, here are some available parameters:

fastlane gym --workspace "Example.xcworkspace" --scheme "AppName" --clean

If you need to use a different Xcode installation, use xcode-select or define DEVELOPER_DIR:

DEVELOPER_DIR="/Applications/" fastlane gym

For a list of all available parameters use

fastlane action gym

If you run into any issues, use the verbose mode to get more information

fastlane gym --verbose

Set the right export method if you're not uploading to App Store or TestFlight:

fastlane gym --export_method ad-hoc

To pass boolean parameters make sure to use gym like this:

fastlane gym --include_bitcode true --include_symbols false

To access the raw xcodebuild output open ~/Library/Logs/gym


Since you might want to manually trigger a new build but don't want to specify all the parameters every time, you can store your defaults in a so called Gymfile.

Run fastlane gym init to create a new configuration file. Example:

scheme "Example"

sdk "iphoneos9.0"

clean true

output_directory "./build"    # store the ipa in this folder
output_name "MyApp"           # the name of the ipa file

Export options

Since Xcode 7, gym is using new Xcode API which allows us to specify export options using plist file. By default gym creates this file for you and you are able to modify some parameters by using export_method, export_team_id, include_symbols or include_bitcode. If you want to have more options, like creating manifest file for app thinning, you can provide your own plist file:

export_options "./ExportOptions.plist"

or you can provide hash of values directly in the Gymfile:

  method: "ad-hoc",
  manifest: {
    appURL: " App.ipa",
  thinning: "<thin-for-all-variants>"

Optional: If gym can't automatically detect the provisioning profiles to use, you can pass a mapping of bundle identifiers to provisioning profiles:

  method: "app-store",
  provisioningProfiles: { 
    "com.example.bundleid" => "Provisioning Profile Name",
    "com.example.bundleid2" => "Provisioning Profile Name 2"

Note: If you use fastlane with match you don't need to provide those values manually.

For the list of available options run xcodebuild -help.

Setup code signing

Automating the whole process

gym works great together with fastlane, which connects all deployment tools into one streamlined workflow.

Using fastlane you can define a configuration like

lane :beta do
  gym(scheme: "MyApp")

# error block is executed when a error occurs
error do |lane, exception|
    # message with short human friendly message
    message: exception.to_s, 
    success: false, 
    # Output containing extended log output
    payload: { "Output" => exception.error_info.to_s } 

When gym raises an error the error_info property will contain the process output in case you want to display the error in 3rd party tools such as Slack.

You can then easily switch between the beta provider (e.g. testflight, hockey, s3 and more).

For more information visit the fastlane GitHub page.

How does it work?

gym uses the latest APIs to build and sign your application. The 2 main components are

When you run gym without the --silent mode it will print out every command it executes.

To build the archive gym uses the following command:

set -o pipefail && \
xcodebuild -scheme 'Example' \
-project './Example.xcodeproj' \
-configuration 'Release' \
-destination 'generic/platform=iOS' \
-archivePath '/Users/felixkrause/Library/Developer/Xcode/Archives/2015-08-11/ExampleProductName 2015-08-11 18.15.30.xcarchive' \
archive | xcpretty

After building the archive it is being checked by gym. If it's valid, it gets packaged up and signed into an ipa file.

gym automatically chooses a different packaging method depending on the version of Xcode you're using.

Xcode 7 and above

/usr/bin/xcrun path/to/ -exportArchive \
-exportOptionsPlist '/tmp/gym_config_1442852529.plist' \
-archivePath '/Users/fkrause/Library/Developer/Xcode/Archives/2015-09-21/App 2015-09-21 09.21.56.xcarchive' \
-exportPath '/tmp/1442852529'

gym makes use of the new Xcode 7 API which allows us to specify the export options using a plist file. You can find more information about the available options by running xcodebuild --help.

Using this method there are no workarounds for WatchKit or Swift required, as it uses the same technique Xcode uses when exporting your binary.

Note: the script wraps around xcodebuild to workaround some incompatibilities.

Use the 'Provisioning Quicklook plugin'

Download and install the Provisioning Plugin.

Supported platforms ios, mac
Author @KrauseFx
Returns The absolute path to the generated ipa file

2 Examples

gym(scheme: "MyApp", workspace: "MyApp.xcworkspace")
  workspace: "MyApp.xcworkspace",
  configuration: "Debug",
  scheme: "MyApp",
  silent: true,
  clean: true,
  output_directory: "path/to/dir", # Destination directory. Defaults to current directory.
  output_name: "my-app.ipa",       # specify the name of the .ipa file to generate (including file extension)
  sdk: "10.0"  # use SDK as the name or path of the base SDK when building the project.


Key Description
workspace Path to the workspace file
project Path to the project file
scheme The project's scheme. Make sure it's marked as Shared
clean Should the project be cleaned before building it?
output_directory The directory in which the ipa file should be stored in
output_name The name of the resulting ipa file
configuration The configuration to use when building the app. Defaults to 'Release'
silent Hide all information that's not necessary while building
codesigning_identity The name of the code signing identity to use. It has to match the name exactly. e.g. 'iPhone Distribution: SunApps GmbH'
skip_package_ipa Should we skip packaging the ipa?
include_symbols Should the ipa file include symbols?
include_bitcode Should the ipa file include bitcode?
export_method Method used to export the archive. Valid values are: app-store, ad-hoc, package, enterprise, development, developer-id
export_options Specifies path to export options plist. Use 'xcodebuild -help' to print the full set of available options
export_xcargs Pass additional arguments to xcodebuild for the package phase. Be sure to quote the setting names and values e.g. OTHER_LDFLAGS="-ObjC -lstdc++"
skip_build_archive Export ipa from previously built xarchive. Uses archive_path as source
build_path The directory in which the archive should be stored in
archive_path The path to the created archive
derived_data_path The directory where built products and other derived data will go
result_bundle Location of the Xcode result bundle
buildlog_path The directory where to store the build log
sdk The SDK that should be used for building the application
toolchain The toolchain that should be used for building the application (e.g., org.swift.30p620160816a)
destination Use a custom destination for building the app
export_team_id Optional: Sometimes you need to specify a team id when exporting the ipa file
xcargs Pass additional arguments to xcodebuild for the build phase. Be sure to quote the setting names and values e.g. OTHER_LDFLAGS="-ObjC -lstdc++"
xcconfig Use an extra XCCONFIG file to build your app
suppress_xcode_output Suppress the output of xcodebuild to stdout. Output is still saved in buildlog_path
disable_xcpretty Disable xcpretty formatting of build output
xcpretty_test_format Use the test (RSpec style) format for build output
xcpretty_formatter A custom xcpretty formatter to use
xcpretty_report_junit Have xcpretty create a JUnit-style XML report at the provided path
xcpretty_report_html Have xcpretty create a simple HTML report at the provided path
xcpretty_report_json Have xcpretty create a JSON compilation database at the provided path
analyze_build_time Analyze the project build time and store the output in 'culprits.txt' file
xcpretty_utf Have xcpretty use unicode encoding when reporting builds

To show the documentation in your terminal, run

fastlane action gym

View source code

Back to actions