-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple iTunes Providers causes failure #1524
Comments
I've never seen this error before. Was it introduced by a fastlane update or did it just happen? |
When did it start to occur? |
Wasn't a fastlane update. It just stopped working in the middle of last week. We updated to the latest version and had the same issue. |
This has probably something to do with your apple account / team. Could you contact the Apple support to request help with this issue? If they ask, you use the iTunes Transporter to upload the builds and it's failing with this error message. |
I experience the same problem with some iTunes accounts. What Transporter complains is that for Apple account with a multiple iTunes providers it expects -itc_provider command to specify which team(provider) we're uploading for. [13:41:45]: Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627) |
I maintain something similar to Fastlane used internally at my Company, for building and submitting our iOS apps. This also stopped working for us recently and I managed to fix it. If you are now submitting under a multiple-teams account you need to provide the team "Short Name" to the iTMSTransporter command:
This can be retrieved by team long name from iTMSTransporter itself using the command:
Which prints to the command line like so:
|
^^ @samrobbins |
Hi folks - we've released That includes #4746 to fix this. You can use the |
Our iTunes account has access to several different teams and until recently we didn't have any issues. However, today we ran into this issue:
The text was updated successfully, but these errors were encountered: