search

fastlane-old / gym

Building your iOS apps has never been easier
https://fastlane.tools
645 stars 54 forks source link

"No 'teamID' specified and no team ID found in the archive" #204

Closed AvdLee closed 8 years ago

AvdLee commented 8 years ago

Using gym as followed from the terminal:

gym build -s MyApp

I'm getting the following error:

Error Domain=IDEFoundationErrorDomain Code=1 "No 'teamID' specified and no team ID found in the archive" UserInfo={NSLocalizedDescription=No 'teamID' specified and no team ID found in the archive}

Any idea how to fix this?

I've checked my team setting in the project, which is setted correctly.

leecrossley commented 8 years ago

I'm also experiencing this issue with export_method "ad-hoc" in my gymfile

Sali0m commented 8 years ago

Having the same issue over here

gym --export_method enterprise use_legacy_build_api --scheme OurScheme

Resulting in this (first line is the latest before the error):

2016-02-15 15:14:07.809 xcodebuild[98931:1626590] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/jc/70y7nvgs2ml9yvlh6v5l2hv80000gn/T/6Play_2016-02-15_15-14-07.809.xcdistributionlogs'.
2016-02-15 15:14:08.156 xcodebuild[98931:1626590] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7f9c2b5d2e00>: Error Domain=IDEFoundationErrorDomain Code=1 "No 'teamID' specified and no team ID found in the archive" UserInfo=0x7f9c2b65ad10 {NSLocalizedDescription=No 'teamID' specified and no team ID found in the archive}
error: exportArchive: No 'teamID' specified and no team ID found in the archive

Error Domain=IDEFoundationErrorDomain Code=1 "No 'teamID' specified and no team ID found in the archive" UserInfo=0x7f9c2b65ad10 {NSLocalizedDescription=No 'teamID' specified and no team ID found in the archive}

I've checked that the server has the certificate and trusts them, and also checked for the provisioning profiles which are all on the server. Any Idea at what to try next?

aimak commented 8 years ago

We (@Sali0m, @delannoyk and I) found our error : it turns out that use_legacy_build_api should actually be --use_legacy_build_api :

gym --export_method enterprise --use_legacy_build_api --scheme OurScheme

When did that change ?

Anyway, sometimes must have changed in our environment that caused perfectly working builds (without legacy_build_api, then) to fail.

fastlane-bot-helper commented 8 years ago

This issue was migrated to https://github.com/fastlane/fastlane/issues/1825. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo :rocket: