fastlane: Cannot specify or inherit team_id from action latest_testflight_build_number
New Issue Checklist
- Updated fastlane to the latest version
- I have read the Contribution Guidelines
Issue Description
Complete output when running fastlane, including the stack trace and command used
[10:58:01]: fastlane beta
[10:58:01]: Driving the lane 'beta' š
[10:58:01]: --------------------------------------------
[10:58:01]: --- Step: latest_testflight_build_number ---
[10:58:01]: --------------------------------------------
[10:58:01]: You passed invalid parameters to 'latest_testflight_build_number'.
[10:58:01]: Check out the error below and available options by running `fastlane action latest_testflight_build_number`
[10:58:01]: Variable Dump:
[10:58:01]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"beta"}
[10:58:01]: Could not find option 'team_id' in the list of available options: app_identifier, username, version, initial_build_number
Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
lane :beta do
increment_build_number(
build_number: latest_testflight_build_number(team_id: "1234567") + 1
)
gym(
workspace: "XXX.xcworkspace",
scheme: "XXX Prod",
clean: true
)
deliver(
force: true,
)
commit_version_bump(
message: 'Build Version Bump by Fastlane',
force: true
)
push_to_git_remote
end
Environment
fastlane version (fastlane -v): 1.64.0 Do you use bundler, rbenv or rvm?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 17 (2 by maintainers)
Commits related to this issue
- [fastlane] Add new team_id option to latest_testflight_build_number Fixes https://github.com/fastlane/fastlane/issues/1464 — committed to fastlane/fastlane by KrauseFx 8 years ago
- [fastlane] Add new team_id option to latest_testflight_build_number (#5668) * [fastlane] Add new team_id option to latest_testflight_build_number Fixes https://github.com/fastlane/fastlane/issues/... — committed to fastlane/fastlane by KrauseFx 8 years ago
@jstubenrauch Thanks for reaching out. We will look this over soon. Hope you hava a great weekend š
I would also very appreciate if this could be added. But I think what we need here is support for the
itc_team_idnot theteam_idIām waiting until I have to send a new build to TestFlight, should happen sometime between today and monday! Thanks!
The motivation for this issue is to prevent being prompt for a Team (I have multiple). Just to add to the issue, I have a
team_idset in my Appfile and I also tried setting in various locations in the Fastfile but thelatest_testflight_build_numbernever read it and would always prompt me to enter a team. I finally tried setting it directly and found it was not a valid option.