Xcodebuild -showBuildSettings timed-out

Archive Issues
,
1

Hi,

I’m having the following error happening randomly with around 60-70% of the builds, starting from today:

[13:57:59]: fastlane finished with errors
[!] xcodebuild -showBuildSettings timed-out after 10 seconds and 3 retries. You can override the timeout value with the environment variable FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT, and the number of retries with the environment variable FASTLANE_XCODEBUILD_SETTINGS_RETRIES

We have been using bitrise for the last 6 months without any problems (like this).

I set the FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT env variable to 600, but it seems like it’s ignored.

I’d need to resolve this ASAP unfortunately - are there any suggestions what could be the problem?
Build URL:
https://www.bitrise.io/build/5eab18f6125bd74c

2

This seems to be a fastlane bug, I’d suggest you to open an issue on their tracker (GitHub - fastlane/fastlane: 🚀 The easiest way to automate building and releasing your iOS and Android apps).

From our side, on the Xcode 8.3 stack you use there was no update since Xcode 8.3.3 so the most likely cause is a newer fastlane version or something in your code.

It seems you have the fastlane step on “update fastlane to the latest version”. This can be turned off if you want to. Related discussion:

3

Actually @dropsmark checked your log again, and it seems that the environment variable might have changed in recent fastlane versions.

In the log:

FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT

but what you have in your App Env Vars:

FASTLANE_XCODE_LIST_TIMEOUT

It seems you set the FASTLANE_XCODE_LIST_TIMEOUT env var, not the FASTLANE_XCODEBUILD_SETTINGS_TIMEOUT one.

Still might worth a report for fastlane as it seems they changed this and do not read the old one (they could of course, for backwards compatibility).

4

Actually it might be just a new option?.. Not sure, it’s a bit confusing - definitely worth to ask the fastlane guys, I have no idea whether this is a new variable in addition to the old one (in which case you should keep the current env var too and just add this one as well) or they replaced the old one with this one…

5

ahh great, thank you!! this was a lifesaver!

1 Like
6

Glad to hear it worked :blush: