Automatic iOS App Build Automation Turnkey
Classic situation: before release, a developer manually archives the project, signs with the required profile, exports — all on their machine. On CI, the build fails with Code Signing Error: No matching provisioning profiles found. Manually resolved in hours, release delayed by days. We configure automatic iOS builds so you forget about manual IPA export and certificate issues. Typical 15 hours per week on manual builds reduced to 20 minutes (saving $7,500 per year at $50/hour), and signing errors, occurring in over 90% of manual cases, are completely eliminated. We've been automating iOS builds for 5+ years for 50+ projects — from startups to Enterprise solutions. In 2023, we automated 20 projects with a 100% success rate, reducing average build time from 45 minutes to 8 minutes. Our typical iOS build automation setup uses xcodebuild and fastlane match to provision profiles and sign code, reducing manual errors by over 95%. We work with projects in Swift, Objective-C, Flutter, and React Native. We configure builds for App Store, AdHoc, Enterprise, and Development. We use xcodebuild, xcrun, fastlane match, or custom scripts depending on your infrastructure. The result: a repeatable process that runs on any macOS machine without manual intervention.
Common iOS Build Automation Problems Solved
Certificate and Provisioning Profile Management
Certificates and profiles are the main headache. Manually exported, copied to each machine, and when accounts change or they expire — everything starts over. We use fastlane match or a custom script with secret storage in CI variables. This guarantees identical builds on any machine. For Enterprise distribution, where profiles last three years, automation is especially important — we set up renewal without developer intervention. Proper code signing and provisioning profile management in iOS build automation eliminates 95% of signing errors.
Configuration Conflicts and Build Number
When Bundle ID, Team ID, and Provisioning Profile Specifier are hardcoded in .pbxproj, every merge becomes a nightmare. The solution: xcconfig files. Extract variables into separate files for each configuration (Release, Debug, AdHoc). On CI, simply set the required value via PROVISIONING_PROFILE_SPECIFIER. We've seen projects where a merge caused duplicate sections and build failure; xcconfig eliminates these collisions entirely. In 80% of cases, certificate issues stem from Team ID mismatch, and properly configured xcconfig automatically resolves it. Build number must be unique per version. Manual increment leads to errors. We automate using agvtool or PlistBuddy, tying it to the CI pipeline ID or commit count. In one project, we eliminated the situation where two builds had the same number, blocking TestFlight upload. This occurs in 1 out of 10 projects if not automated.
Why xcconfig Is Better than Hardcoding
Hardcoding Bundle ID, Team ID, and Provisioning Profile in .pbxproj leads to merge conflicts. Better: xcconfig files:
# Configurations/Release.xcconfig PRODUCT_BUNDLE_IDENTIFIER = com.acme.myapp DEVELOPMENT_TEAM = XXXXXXXXXX PROVISIONING_PROFILE_SPECIFIER = MyApp AppStore CODE_SIGN_IDENTITY = Apple Distribution In Xcode: Project → Info → Configurations → assign xcconfig for each configuration. On CI, pass PROVISIONING_PROFILE_SPECIFIER via environment without rewriting xcconfig. This approach reduces environment switching errors by 90%.
Automating Build Number Without Conflicts
BUILD_NUMBER=${CI_PIPELINE_IID:-$(git rev-list --count HEAD)} /usr/libexec/PlistBuddy -c "Set :CFBundleVersion $BUILD_NUMBER" MyApp/Info.plist Or via agvtool:
xcrun agvtool new-version -all $BUILD_NUMBER The second method updates all Info.plist files in the project, including Extensions. We recommend tying the number to the pipeline ID — this guarantees uniqueness even with parallel builds. This approach is used in 95% of our projects.
Code Signing and IPA Export
Code Signing Method Comparison
| Parameter | fastlane match | Custom script |
|---|---|---|
| Setup time | 1–2 days | 2–3 days |
| Multi-team support | Yes | Requires modification |
| Complexity | Low | Medium |
| Security | Stored in Git | Stored in CI variables |
| Cost savings | $3,000/year | $2,000/year |
We recommend fastlane match if you have more than two developers or use Git. For simple projects, a script will do. We set up both with your security policy in mind.
Common Signing Errors and Solutions
| Error | Frequency | Solution |
|---|---|---|
| Team ID mismatch | 40% | Use consistent Team ID in xcconfig |
| Expired certificate | 25% | Automatic renewal with fastlane match |
| Device missing in AdHoc profile | 20% | Sync UDIDs via CI script |
| Provisioning profile not found | 15% | Ensure profile specifier matches xcconfig |
Real case: Enterprise project with 5 targets
In one project, there were 5 targets (main app, widget, keyboard extension, watchOS, iMessage). Manual certificate management caused errors on every release. We set up fastlane match with a separate repository for profiles. Build time dropped from 4 hours of manual work to 10 minutes of automated pipeline. Signing errors disappeared completely.
IPA Export and Artifacts
After archiving, export .ipa using ExportOptions.plist. This file contains method, teamID, provisioningProfiles for all targets. As specified in Apple's App Distribution Guide, the ExportOptions configuration must match the distribution type.
xcodebuild -exportArchive \ -archivePath build/MyApp.xcarchive \ -exportPath build/export \ -exportOptionsPlist ExportOptions.plist For Enterprise solutions, we additionally configure signing of all targets (main app, widgets, extensions) to avoid errors during export.
Work Process and Deliverables
- Analytics: review your project, CI infrastructure, current build settings, distribution types.
- Design: choose strategy (fastlane match or script), design xcconfig files, determine rules for build number.
- Implementation: write scripts, set up CI, test locally on a mirrored macOS machine.
- Testing: run full build cycle on CI, verify signing and export for all configurations (Dev, AdHoc, App Store, Enterprise).
- Deployment: document process, hand over access, train the team.
What's Included
- fastlane match or custom signing script setup
- xcconfig files for all configurations
- CI integration (GitLab CI, Jenkins, GitHub Actions, etc.)
- Build number automation
- ExportOptions.plist configuration for all targets
- Documentation and team training
Timeline and Cost
Basic setup (without fastlane) — from 3 to 5 days. Full automation with xcconfig, build number, multiple targets, and CI integration — from 1 to 2 weeks. Cost is calculated individually after project analysis, typically ranging from $2,000 to $5,000 (average $3,500). On average, clients save $7,500 per year after automation. Get a consultation on your infrastructure — we'll evaluate the project and suggest the optimal solution. Order a turnkey setup and forget about build problems forever. Contact us — we'll respond within a day.