Inside your app directory, you first need to setup and configure TiFastlane:
tifast setup
Once your configuration is set, then you want to initialize your app:
tifast init
And then finally when you are ready, you'll want to send your app for review at the App Store:
tifast send
Is that easy!
Below you will find full documentation on every step and other tools available to you.
tifastlane or tifast must be executed from your Titanium App directory. It will automatically read your tiapp.xml to determine your App configuration for all the tools.
- tifast setup
- tifast init
- tifast status
- tifast register
- tifast repairprofiles
- tifast downloadprofiles
- tifast send
- tifast pem
- tifast pilot
Each of TiFastlane's commands has it's own set of arguments you can use to further control. You can easily look at each avaiable argument with -h, for example:
tifast setup -h
This will configure TiFastlane on your current project.
tifast setup
TiFastlane needs to initialize the configuration files needed to keep iTunes Connect updated with the correct information. If the app is not in iTunes Connect then run to start fresh settings:
tifast init
If your app is already on iTunes Connect, then run the wizard which will automatically download all your current metadata and screenshots:
tifast init -s
You can view the current settings that would be used by running:
tifast status
You will see something like this:
Apple ID Username: contact@universopositivo.com.br
Name: Easy Ticket
AppId: br.com.universopositivo.easyTicket
Version: 1.0.0
CFBundleVersion: 107
GUID: "32cc538e-4fd3-4d6e-9999-870ce50ab039"
SKU: "xxxxxxxxxxxxxx"Register your Titanium App ID on the Apple Developer Program and iTunes Connect, and then generate the Provisioning Profiles for App Store, Ad Hoc and Development.
tifast register
Everything is done behind the scenes using produce and sigh or match depending on your choice. If the App ID already exists on the Developer Program or iTunes Connect it will be safely skipped.
For default provisiong profiles will be generated for all platforms, but if you wish you can target a single platform: appstore, adhoc, development or leave empty for all.
tifast register <platform>
Provisioning profiles will be generated by default using sigh but you can use match instead:
tifast register <platform> --match
If you decide to use match, make sure that you previously configured it.
Fix ALL invalid or expired Provisioning Profiles on the account.
tifast repairprofiles
Download and install ALL valid Provisioning Profiles on the account.
tifast downloadprofiles
When you have a new version of your App that you wish to push to iTunes Connect, all you have to do is:
tifast send
If you want to Upload an Beta version of your app.
tifast send -t
You can decide what you want to send to iTunes Connect (binary, screenshots, metadata, etc). For full listing of options run:
tifast send -h
Generate or rewnew your push certificates by using:
tifast pem [password]
For default certificates will be created for distribution using the password you define, if you want to target the development certificates then use:
tifast pem -d [password]
To renew push certificate, even if the current one is active for 30 more days
tifast pem -f [password]
All metadata and screenshots are easily maintained from the TiFLDelivery\APPID directory, here you will find the following files:
Deliveryfile
You can configure Price, Copyright, Developer Notes, etc. You can read the full documentation here.
./metadata/[LANG]/*.txt
In this directory you will see several text files with the contents of the metadata that is language dependant.
da, de-DE, el, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fi, fr-CA, fr-FR, id, it, ja, ko, ms, nl, no, pt-BR, pt-PT, ru, sv, th, tr, vi, zh-Hans, zh-Hant
./screenshots/[LANG]/.
As with metadata, screenshots support multi language. Based on the dimension of the images they will be correctly set to the appropiate device. The images are ordered alphabetically, so make sure to name them correctly to control the right display order.
By default the main configuration settings are stored in a file called tifastlane.cfg in your app project root.
If you want to be able to have multiple configuration files, for example, to login with other credentials, you can override the configuration file to be loaded by using the -c param.
For example:
tifast send -c otherconfig.cfg
This will make TiFastlane use the otherconfig.cfg file instead of the default tifastlane.cfg. All methods accept the configuration override.
Starting from XCode 8.3 the legacy build API was removed, so the way TiFastlane used to build the app broke. We fixed this issue on TiFast 0.9, but this change could break your builds on older versions of XCode and Titanium. If you want to force TiFast to use the old way to package you can do it using the --legacy option:
tifast send --legacy