fastlane: team_id does not automatically select correct team when provisioning in iTunes Connect
Issue Description
My Apple ID belongs to two teams. I have specified the team_id I wish to use in my Appfile. It seems that there is no matching between the team_id and the iTunes Connect access corresponding to the team.
I searched for some way to indicate the correct iTunes Connect id (which is different from the team_id), but did not find one.
Unexpected output when running fastlane
Confusingly, I got this prompt even though I specified a team_id in my Appfile:
Multiple iTunes Connect teams found, please enter the number of the team you want to use:
1) "xxxxx" (2*******)
2) "yyyyy" (1******)
Configuration Files
Fastfile is copied directly from doc, only using :provision for the moment; there is one team_id specified in the Appfile and I’m not doing anything fancy.
Environment
fastlane 1.81.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
)?
NO
System ruby: ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]
All gems up to date.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 51 (6 by maintainers)
Commits related to this issue
- [spaceship] Validate team ID and show nice error message Related to https://github.com/fastlane/fastlane/issues/4301 — committed to fastlane/fastlane by KrauseFx 8 years ago
- Update team selection and documentation across all fastlane actions - Add team suport for ‘set_changelog’ - Update to the new way of passing the team ID and name - Make description more clear on what... — committed to fastlane/fastlane by KrauseFx 8 years ago
- Update team selection and documentation across all fastlane actions (#6444) * Update team selection and documentation across all fastlane actions - Add team suport for ‘set_changelog’ - Update to... — committed to fastlane/fastlane by KrauseFx 8 years ago
- [spaceship] Validate team ID and show nice error message (#6442) * [spaceship] Validate team ID and show nice error message Related to https://github.com/fastlane/fastlane/issues/4301 * Fix cod... — committed to fastlane/fastlane by KrauseFx 8 years ago
@biolinh in reply to your unanswered question:
I had a hard time to find out the iTunes Connect ids as well (thx apple for making this super hard to find out…), so I want to share my approach:
associatedAccounts
array with the differentcontentProvider
objects - the entry namedcontentProviderId
reflects the iTunes Connect id, lookup for the name value to pick the correct oneHope these hints will help you and other people saving time while finding out the correct value for itc_team_id.
@KrauseFx and fastlane team: thx for solving this issue. We con confirm it works with the newest version
1.105.2
(and choosing the correct (!) iTunes Connect id when finally accomplished to find out…)Yeah, you can already specify the Team ID for both the Dev Portal and for iTunes Connect, check out the docs here https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md
@TKBurner thanks for giving us free support of Fastlane and telling the team to have more attention on this fix! 😃
Just as we have:
We should have:
@TKBurner Basically
itc_team_id
work withgym
,pilot
but not withlatest_testflight_build_number()
. When I runlatest_testflight_build_number()
I gotthanks @TKBurner and @KrauseFx for your support 👍
If I may add a suggestion, I think it would be a cool addition to the docs that, if you are in two teams, you must specify both the team_id and itc_team_id at https://github.com/fastlane/fastlane/blob/505ce4f462a4d9083a5334c81a6aaac8fa302aee/fastlane/docs/Appfile.md When I was reading it for the first time I thought I only needed to choose one of the pairs, not both.
@ssteinerx Thanks! I’ll surface this with the team 👍
Hey everyone, I was doing a lot of experiments, and noticed some rough edges around how the team ID isn’t automatically converted from integer to strings, and how some actions have an inconsistent handling of the available teams.
I therefore pushed a bunch of PRs, that should fix all the issues you mentioned above:
--verbose
Appfile
and whatAppfile
is loaded when using the--verbose
flag when running fastlaneThe PRs are ready, as soon as they are reviewed and merged, we’ll publish new releases for all those tools 👍
@lfarah can you confirm that the team selection for iTunes Connect works for other tools (e.g. deliver, pilot), but not for
latest_testflight_build_number
?Thanks everybody for all the information provided, I hope the above posted pull requests will solve all the remaining issues 🚀
@ssteinerx I can’t wait to see this fixed either and sorry that this is still affecting you. ❤️
@lfarah Thanks so much!
I added our community PR flag to this as well so we can make sure to get as many resources on this as possible. If anyone is interested in investigating we’d love to see that.
To make sure that I’m definitive on what I’m communicating to the team:
The action latest_test_flight_build_number is not inheriting team id, and this is causing it to fail to run autonomously. Is that correct?
Thanks again 👍 👍
@KrauseFx yes, I use
update_fastlane
@TKBurner ENV[“ITC_TEAM_ID”] = “118033180” didn’t work: