You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flutter build ios takes 30+s on my monster mac pro. Would be nice to get it faster.
Some candidates:
100+ms to read the CFBundleIdentifier from the project
1000+ms to print the build settings to do some variable substitution. Maybe we can cache this.
400+ms to check cocoapods version. Maybe we can ask for forgiveness instead of permission
1900+ms to check cocoapods dependencies. Don't know if there's any caching we can use
22000+ms to run /usr/bin/env xcrun xcodebuild clean build -configuration Release ONLY_ACTIVE_ARCH=YES -workspace Runner.xcworkspace -scheme Runner BUILD_DIR=build/ios -sdk iphoneos -arch arm64. Do we really need to clean first?
Actually the 22000+ms has a 13000+ms snapshot build component. Removing clean doesn't make much of a difference. Would be worth looking deeper into the xcodebuild's outputs and timings
We have a large project in which xcode_backend script occupies a pretty large time during iOS builds (~1 min out of 4+ min of build time).
I was wondering how can we profile it to better inspect why it takes so long to execute.
I was also wondering if it could be possible to parallelize it in any way with other steps of the build process.
Activity
xster commentedon Apr 4, 2017
Actually the 22000+ms has a 13000+ms snapshot build component. Removing clean doesn't make much of a difference. Would be worth looking deeper into the xcodebuild's outputs and timings
Hixie commentedon Dec 6, 2017
This is not on our immediate list of priorities, moving to next milestone.
jmagman commentedon Aug 16, 2019
You can run with
-showBuildTimingSummary:Dominated by the xcode_backend script run.
ezamagni-tg commentedon Aug 22, 2025
We have a large project in which xcode_backend script occupies a pretty large time during iOS builds (~1 min out of 4+ min of build time).
I was wondering how can we profile it to better inspect why it takes so long to execute.
I was also wondering if it could be possible to parallelize it in any way with other steps of the build process.