Making address: https://github.com/fastlane/fastlane

The document address: https://docs.fastlane.tools/

Main functions:

Sigh: Development certificate and description file download

Produce: Create new apps and development portals on iTunes Connect using the command line

Cert: Automatically creates and configures iOS code signing certificates

Spaceship: Ruby library access Apple Developer Centre and iTunes Connect

Pilot: The best way to manage your TestFlight testers and build from the terminal

The easiest way to invite your TestFlight beta testers

Gym: automatic iOS app signature packaging tool

Match: Use Git to synchronize your team certificates and configuration files

Scan: The easiest way to test your iOS and Mac apps

Sudo gem install fastlane –verbose

The prerequisites are Xcode and Xcode Command line installed

Use: xcode-select –install

Xcode -select: error: xcode-select: error: command line tools are already installed, use “Software Update” to install updates

Terminal CD to the project directory, initialize:

fastlane init

This will prompt you to fill in the Apple ID and password, etc., need to fill in for

Fastlane is already set up at path./fastlane/

Next, you can use the packing tool GYM to start packing:

gym –workspace “YOUR APP.xcworkspace” –scheme “YOUR APP.” –clean –output_directory OUTPATH –output_name IPA_NAME–export_method ad-hoc –configuration Release — use_legacy_build_API

Upload to fir. Im:

fir publish YOUR_APP.ipa -Q -T YOUR_TOKEN_ID

Remark:

1. Ensure that the CD has been placed in the project directory when packing;

2. Ensure the normal operation of the project without any mistakes;

3. If there are multiple targets, ensure that the scheme selected is correct;

4. Package options are currently available: App-Store, Package, ad-hoc, Enterprise, Development, and Developer-ID, also known as XcodeBuild

5. Configuration: Debug and Release are optional

Projects that rely on CocoaPods have problems like not finding third-party libraries:

❌ld: Library not found for-ltmcache

Solution: fix tripartite library references in project Build Settiing;