# Xcodebuild -showBuildSettings timed-out

**URL:** <https://discuss.bitrise.io/t/xcodebuild-showbuildsettings-timed-out/2513>\
**Category:** Issues\
**Tags:** fastlane, xcode\
**Created:** [August 18, 2017, 9:08pm UTC](https://discuss.bitrise.io/t/xcodebuild-showbuildsettings-timed-out/2513 "2017-08-18T21:08:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [August 19, 2017, 6:02am UTC](https://discuss.bitrise.io/t/xcodebuild-showbuildsettings-timed-out/2513/2 "2017-08-19T06:02:10Z")

</div>

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](https://github.com/fastlane/fastlane)).

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:

> [@How to use a specific version of fastlane?](http://discuss.bitrise.io/t/how-to-use-a-specific-version-of-fastlane/1001):
>
> If you use our fastlane step to run your fastlane config, and you want to use a specific version of fastlane: Add a Script step right before the fastlane step Specify this as the content of the Script step: set -ex gem uninstall fastlane --all --executables gem install fastlane --version 2.18.3 --no-document Make sure that the Should update fastlane gem before run? (update\_fastlane) option of the fastlane step is set to false. That’s all. Of course, replace 2.18.3 with the version you want…

---

_[View the full topic](https://discuss.bitrise.io/t/xcodebuild-showbuildsettings-timed-out/2513)._