deliver • snapshot • frameit • PEM • sigh • produce • cert • spaceship • pilot • boarding • gym • scan
-------Get in contact with the developer on Twitter: @KrauseFx
Features • Installation • Setup • Quick Start • Commands • Uploading an APK • Images
supply
is part of fastlane: connect all deployment tools into one streamlined workflow.
- Update existing Android applications on Google Play via the command line
- Upload new builds (APKs)
- Retrieve and edit metadata, such as title and description, for multiple languages
- Upload the app icon, promo graphics and screenshots for multiple languages
- Have a local copy of the metadata in your git repository
Install the gem
sudo gem install supply
- Open the Google Play Console
- Open Settings => API-Access
- Create a new Service Account - follow the link of the dialog
- Create new Client ID
- Select Service Account
- Click Generate new P12 key and store the downloaded file
- Make a note of the Email address underneath Service account - this is the issuer which you will need later
- Back on the Google Play developer console, click on Grant Access for the newly added service account
- Choose Release Manager from the dropdown and confirm
cd [your_project_folder]
supply init
- Make changes to the downloaded metadata, add images, screenshots and/or an APK
supply run
supply
: update an app with metadata, a build, images and screenshotssupply init
: download metadata for an existing app to a local directorysupply --help
: show information on available commands, arguments and environment variables
You can either run supply
on its own and use it interactively, or you can pass arguments or specify environment variables for all the options to skip the questions.
To upload a new binary to Google Play, simply run
supply --apk path/to/app.apk
This will also upload app metadata if you previously ran supply init
.
To gradually roll out a new build use
supply --apk path/app.apk --track rollout --rollout 0.5
After running supply init
, you will have a metadata directory. This directory contains one or more locale directories (e.g. en-US, en-GB, etc.), and inside this directory are text files such as title.txt
and short.txt
.
Here you can supply images with the following file names (extension can be png, jpg or jpeg):
featureGraphic
icon
promoGraphic
tvBanner
And you can supply screenshots by creating directories with the following names, containing PNGs or JPEGs (image names are irrelevant):
phoneScreenshots/
sevenInchScreenshots/
(7-inch tablets)tenInchScreenshots/
(10-inch tablets)tvScreenshots/
Note that these will replace the current images and screenshots on the play store listing, not add to them.
fastlane
Toolchain
fastlane
: Connect all deployment tools into one streamlined workflowdeliver
: Upload screenshots, metadata and your app to the App Storesnapshot
: Automate taking localized screenshots of your iOS app on every deviceframeit
: Quickly put your screenshots into the right device framesPEM
: Automatically generate and renew your push notification profilessigh
: Because you would rather spend your time building stuff than fighting provisioningproduce
: Create new iOS apps on iTunes Connect and Dev Portal using the command linecert
: Automatically create and maintain iOS code signing certificatescodes
: Create promo codes for iOS Apps using the command linespaceship
: Ruby library to access the Apple Dev Center and iTunes Connectpilot
: The best way to manage your TestFlight testers and builds from your terminalboarding
: The easiest way to invite your TestFlight beta testersgym
: Building your iOS apps has never been easier
Please submit an issue on GitHub and provide information about your setup
This project is licensed under the terms of the MIT license. See the LICENSE file.
This project and all fastlane tools are in no way affiliated with Apple Inc. This project is open source under the MIT license, which means you have full access to the source code and can modify it to fit your own needs. All fastlane tools run on your own computer or server, so your credentials or other sensitive information will never leave your own computer. You are responsible for how you use fastlane tools.