fastlane
invalid option: --capture_output
New Issue Checklist
- [x] Updated fastlane to the latest version
- [x] I read the Contribution Guidelines
- [x] I read docs.fastlane.tools
- [x] I searched for existing GitHub issues
Issue Description
In the issue template it says:
You can use
--capture_outputas the last command line argument for many commands to get that collected for you.
However that command produces an error: invalid option: --capture_output.
Command executed
fastlane match --capture_output
Complete output when running fastlane, including the stack trace and command used
fastlane match --capture_output [✔] 🚀 [20:28:01]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile invalid option: --capture_output
Environment
✅ fastlane environment ✅
Stack
Key Value OS 12.2 Ruby 3.0.3 Bundler? false Git git version 2.32.0 (Apple Git-132) Installation Source /opt/homebrew/Cellar/fastlane/2.200.0/libexec/bin/fastlane Host macOS 12.2 (21D5039d) Ruby Lib Dir /opt/homebrew/Cellar/ruby/3.0.3/lib OpenSSL Version OpenSSL 1.1.1l 24 Aug 2021 Is contained false Is homebrew true Is installed via Fabric.app false Xcode Path /Applications/Xcode_13.2.1.app/Contents/Developer/ Xcode Version 13.2.1 Swift Version 5.5.2 System Locale
Variable Value LANG LC_ALL en_US.UTF-8 ✅ LANGUAGE fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration # You can find the documentation at https://docs.fastlane.tools # # For a list of all available actions, check out # # https://docs.fastlane.tools/actions # # For a list of all available plugins, check out # # https://docs.fastlane.tools/plugins/available-plugins # # Uncomment the line if you want fastlane to automatically update itself # update_fastlane fastlane_version "2.94.0" default_platform(:ios) platform :ios do before_all do setup_circle_ci end desc "Run tests" lane :tests do run_tests(scheme: "TestappTests") end desc "Take snapshots" lane :screenshots do capture_screenshots(scheme: "TestappScreenshots", add_videos: "video.mov") end desc "Push a new release build to the App Store" lane :release do match(type: "appstore", app_identifier: ["com.rrainn.ios.testapp"], force: true, readonly: false) capture_screenshots(scheme: "TestappScreenshots", add_videos: "video.mov") gym(scheme: "Testapp", workspace: "Testapp.xcworkspace", include_bitcode: true, export_method: "app-store") # Build your app - more options available deliver(force: true) end end`./fastlane/Appfile`
app_identifier("com.rrainn.ios.testapp") # The bundle identifier of your app apple_id("[email protected]") # Your Apple email address itc_team_id("118418113") # iTunes Connect Team ID team_id("33LGSB2522") # Developer Portal Team ID # For more information about the Appfile, see: # https://docs.fastlane.tools/advanced/#appfilefastlane gems
Gem Version Update-Status fastlane 2.200.0 ✅ Up-To-Date Loaded fastlane plugins:
No plugins Loaded
Loaded gems
Gem Version did_you_mean 1.5.0 atomos 0.1.3 rexml 3.2.5 CFPropertyList 3.0.5 claide 1.1.0 colored2 3.1.2 nanaimo 0.3.0 xcodeproj 1.21.0 rouge 2.0.7 xcpretty 0.3.0 terminal-notifier 2.0.0 unicode-display_width 1.8.0 terminal-table 1.8.0 plist 3.6.0 public_suffix 4.0.6 addressable 2.8.0 multipart-post 2.0.0 word_wrap 1.0.0 optparse 0.1.1 tty-screen 0.8.1 tty-cursor 0.7.1 tty-spinner 0.9.3 artifactory 3.0.15 babosa 1.0.4 colored 1.2 highline 2.0.3 commander 4.6.0 excon 0.90.0 faraday-em_http 1.0.0 faraday-em_synchrony 1.0.0 faraday-excon 1.1.0 faraday-httpclient 1.0.1 faraday-multipart 1.0.3 faraday-net_http 1.0.1 faraday-net_http_persistent 1.2.0 faraday-patron 1.0.0 faraday-rack 1.0.0 faraday-retry 1.0.3 ruby2_keywords 0.0.5 faraday 1.9.3 unf_ext 0.0.8 unf 0.1.4 domain_name 0.5.20190701 http-cookie 1.0.4 faraday-cookie_jar 0.0.7 faraday_middleware 1.2.0 fastimage 2.2.6 gh_inspector 1.1.3 json 2.5.1 mini_magick 4.11.0 naturally 2.2.1 rubyzip 2.3.2 security 0.1.3 xcpretty-travis-formatter 1.0.1 dotenv 2.7.6 bundler 2.2.32 simctl 1.6.8 jwt 2.3.0 uber 0.1.0 declarative 0.0.20 trailblazer-option 0.1.2 representable 3.1.1 retriable 3.1.2 mini_mime 1.1.2 memoist 0.16.2 multi_json 1.15.0 os 1.1.4 signet 0.16.0 googleauth 1.1.0 httpclient 2.8.3 webrick 1.7.0 google-apis-core 0.4.1 google-apis-playcustomapp_v1 0.7.0 google-apis-androidpublisher_v3 0.15.0 google-cloud-env 1.5.0 google-cloud-errors 1.2.0 google-cloud-core 1.6.0 google-apis-iamcredentials_v1 0.10.0 google-apis-storage_v1 0.11.0 rake 13.0.6 digest-crc 0.6.4 google-cloud-storage 1.36.0 emoji_regex 3.2.3 jmespath 1.5.0 aws-partitions 1.547.0 aws-eventstream 1.2.0 aws-sigv4 1.4.0 aws-sdk-core 3.125.3 aws-sdk-kms 1.53.0 aws-sdk-s3 1.111.1 set 1.0.1 forwardable 1.3.2 logger 1.4.3 pathname 0.1.0 shellwords 0.1.0 cgi 0.2.1 date 3.1.3 timeout 0.1.1 stringio 3.0.1 securerandom 0.1.0 uri 0.10.1 ipaddr 1.2.2 openssl 2.2.1 digest 3.0.0 io-nonblock 0.1.0 io-wait 0.2.0 zlib 2.0.0 resolv 0.2.1 time 0.1.0 open-uri 0.1.0 mutex_m 0.1.1 net-protocol 0.1.1 ostruct 0.3.1 english 0.7.1 erb 2.2.0 strscan 3.0.1 abbrev 0.1.0 io-console 0.5.7 tempfile 0.1.1 delegate 0.2.0 fileutils 1.5.0 tmpdir 0.1.2 base64 0.1.0 singleton 0.1.1 net-http 0.1.1 open3 0.1.1 nkf 0.1.0 prettyprint 0.1.1 pp 0.2.1 find 0.1.0 yaml 0.1.1 psych 3.3.2 generated on: 2022-01-14
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
Thanks @fastlane-bot... waiting for a reply from someone from Fastlane.
This issue still occurs on fastlane 2.204.3.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
Care to comment on this @joshdholtz??? @fastlane-bot should not be trying to close issues as stale when there has been absolutely NO involvement from the Fastlane team.
This issue still occurs in fastlane 2.205.1...
Completely understand that this is open source, and most efforts are volunteer driven. However, there has to be a balance between that, and just closing issues as stale when it's clearly still an issue.
It's not worth my time to continuously comment on this issue to keep it open, even tho it is still an active issue...
Hanging out with family right now but I'll prevent the bot from closing this and look into it later this week!
@joshdholtz Thanks! No pressure, mainly just want the bot to stop trying to close a perfect valid issue. Enjoy your weekend!!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
@joshdholtz What is going on here? Totally fair that we all get busy, and this is open source software. But kinda frustrating to have the bot constantly trying to close this issue.
Is there not a tag that can be applied to turn off the bot for this issue?
@fishcharlie My apologies! Again 😔
Turning this into my highest priority because it is annoying. I will look at the bot code to create tag for that tonight but I will also look at this issue tonight
@fishcharlie Ahhh! Did some digging into this and it doesn't look like any of the major tools (match, sigh, etc) support this 😱 Will get a PR up for this
@joshdholtz Awesome. Thanks so much for your help on this. Don't wanna ask too much of you, but if there is any chance you'd also be willing to look at #19800 I'd REALLY REALLY appreciate it. Think it has something to do with capitalization mismatch when comparing strings.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:
This issue will be auto-closed if there is no reply within 1 month.
Will try to look into soon! Been on family leave for 7 weeks and starting to ramp back into things 🙂