Fastlane: Gym: Could not find option for key :xcodebuild_list_silent

Created on 25 Jul 2016  路  3Comments  路  Source: fastlane/fastlane

New Issue Checklist

Using gym to build iOS app on Bitrise CI.
Fails with "Could not find option for key :xcodebuild_list_silent"
Running Xcode 7.3.1 on OS X 10.11.4.
The only thing that changed between the builds is the version of fastlane_core.
Green builds with fastlane_core-0.48.1
Red builds with fastlane_core-0.48.2

Complete output when running fastlane, including the stack trace and command used
[10:47:46]: -----------------
[10:47:46]: --- Step: gym ---
[10:47:46]: -----------------
[10:47:46]: Variable Dump:
[10:47:46]: {:PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :SIGH_PROFILE_TYPE=>"ad-hoc"}
[10:47:46]: Could not find option for key :xcodebuild_list_silent. Available keys: workspace, project, scheme, clean, output_directory, output_name, configuration, silent, codesigning_identity, include_symbols, include_bitcode, use_legacy_build_api, export_method, export_options, skip_build_archive, build_path, archive_path, derived_data_path, result_bundle, buildlog_path, sdk, provisioning_profile_path, destination, export_team_id, xcargs, xcconfig, suppress_xcode_output

Configuration Files

Please copy the complete content of your Fastfile and any other configuration files you use below:

Fastfile:

gym(
              workspace: './ios/Differ.xcworkspace',
              scheme: 'Differ',
              output_directory: './ios/build/'
            )

Environment

fastlane version (run fastlane -v): 1.98.0

Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? No

Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? Unknown, handled by CI

gym bug

Most helpful comment

Issue has been resolved in fastlane_core 0.48.3 which was just released. Closing

All 3 comments

It seems like this issue might be related to code signing :no_entry_sign:

Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues :+1:

Issue has been resolved in fastlane_core 0.48.3 which was just released. Closing

Wow, that was quick 馃槀

Was this page helpful?
0 / 5 - 0 ratings