showBuildSettings&resolvePackageDependencies eat 20s of build time

[yakimant]

It's not a problem, until you have 70+ test schemes to run on CI.
It become 23m+.

Do we really need to run those? What is the reason?

FYI
#14777
#15717

[rogerluan]

Very interesting.

Digging into the links you posted I found this answer as to some of the "why's": #15732 (comment)

Does this answer your question? 🤔

[ethan-gates]

I've also been running into these over the past year or so of fastlane releases. For me, I was running into this while running scan, and looking at the fastlane core project model, it looks like fastlane will call xcodebuild -showBuildSettings when it needs a value that it doesn't have (via normal lane arguments). In particular, for my case I learned the absence of 'app_name', 'device', and 'deployment_target_version' arguments as well as the presence of the 'destination' argument can all implicitly trigger the show build settings command. Earlier this year I added those arguments (removing 'destination') and it removed the call for a few releases.

Just today I looked into why fastlane started running the command again despite keeping scan arguments the same, and learned that it's now checking for 'SUPPORTS_MACCATALYST' in the project file (as of a few releases ago).

It's a little difficult to determine what lane arguments can suffice for which build settings since AFAIK that mapping doesn't exist nicely in fastlane, but you can get an idea by looking at which build settings fastlane is looking for.

You can trace what build setting triggered the show build settings command by looking at the key argument to this function in project.rb (using fastlane as a local gem)

[yakimant]

Thanks for your information, @ethantakeshi!

Sounds tricky to find, what can cause to add 20s.
We are currently investigating a switch from scan to xcodebuild Fastalne action, which doesn't have this issue.