'No "teamID" specified and no team ID found in the archive' when building iOS

Expo Application Services (EAS)
1

My iOS build is failing on EAS suddenly with the below error in the Fastlane phase.

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}

Certs and everything are generated by Expo so we’re not using local credentials. I’ve tried completely regenerating all credentials and still no luck

2

This only occurs using EAS both online and with the --local flag.

Downloading the credentials and manually archiving through XCode succeeds.

3

Looking further at the build logs and previous successful builds, it appears that the app is not being signed in failed builds.

In a successful build, we get the following printed in the logs.

› Generating debug MyApp » MyApp.app.dSYM
› Executing MyApp » Bundle React Native code and images
› Executing MyApp » [CP] Copy Pods Resources
› Executing MyApp » Upload Debug Symbols to Sentry
› Executing MyApp » [CP] Embed Pods Frameworks
› Signing   MyApp » MyApp.app
› Creating  MyApp » MyApp.app
› Archive Succeeded

Although in failed builds, we get the following:

› Generating debug MyApp » MyApp.app.dSYM
› Executing MyApp » Bundle React Native code and images
› Executing MyApp » [CP] Copy Pods Resources
› Executing MyApp » Upload Debug Symbols to Sentry
› Executing MyApp » [CP] Embed Pods Frameworks
› Creating  MyApp » MyApp.app
› Archive Succeeded

Does anyone know why EAS will sometimes not sign the application? Nothing has changed in the application code that could cause this.

4

Hi @catch.hoppa,

Can you share the link to the EAS Build that is failing? Happy to take a look to find what could be the cause. In general, if the project is configured with EAS correctly, this should not happen.

5

Sure, I’m assuming an Expo team member can access the below link even if it’s a private project. If not, let me know, and I’ll find some way to share it with you.

6

Thanks for sharing the link! Yes, it’s accessible to Expo team members. Let me get back to you.

7

Hey,

For people who stumble upon this issue in the future, I found what was causing the problem.

There was a sneaky ^ in the package.json file, so a native iOS dependency was changing.

The signing issue is related to CocoaPods (Xcode 14 build failed with manual code sign and app resource bundles · Issue #11402 · CocoaPods/CocoaPods · GitHub); the workaround specified in the Stripe iOS SDK fix the problem ([BUG] Can not create app build using Xcode 14. Keep saying select development team for signing "stripe-stripe" · Issue #2012 · stripe/stripe-ios · GitHub)

Thanks, @amanhimself, for offering to go over the build logs - I appreciate it.

1 Like
8

I am so glad you found the underlying issue and got it resolved. Thanks a lot for sharing the resolution here!