This series is not an introductory article. If you don’t know how to install or use it, you can search the Internet. Please note: This series was written in 2018 and some of the things in it, such as fir. Im, don’t work anymore.
Since last year (2017), I have been working on some Fastlane tools on and off, so this series of articles is a summary of my experience. This is an outline.
The outline
- Fastlane combat: 1, automatic packaging (1)
- Fastlane combat: 2, automatic packaging (ii)
- Fastlane actual combat: 3, management certificate
- Fastlane combat: 4, add test machine
- Fastlane combat: 5, new internal purchase project
- 6. Generate IPA from Archive
background
I joined the company last year, and I play the internal test package twice a day. Just try to do something to lighten the human burden. Finally found a Mac Mini to do the packing. Then, because there are a number of new vests, so I tried to study the management certificate, new in-app purchase projects these gameplay.
Similarly, due to the problem of vest package, other departments or test machines need to add UDID, so it takes a lot of time to complete this step manually, so WE also studied it.
results
The final result is satisfactory. The effect is as follows:
- Automated packaging (AdHoc):
- Supports remote login host packaging
- Support to automatically add, identify the version number, and add in sequence
- (Git) support automatic pull, tagging, push
- Support to play obfuscated vests, and merge changes into non-obfuscated code branches
- Support push to
fir.im
, send the pin message - Support a file + configuration file to play different vests
- Management certificate: failure, the effect is not good
- Add a new test machine
- New in-app purchase project
- Generate IPA through Archive
Some of them are relatively rare online reference, sorting out here, I hope to help you.