Skip to content
Latchkey

Xcode "Signing requires a development team" in CI

Xcode tried to code-sign the build but no development team is configured. On a fresh CI runner there is no signed-in Apple account, so automatic signing has nothing to sign with.

What this error means

The build fails at the signing step with "Signing for <target> requires a development team. Select a development team in the Signing & Capabilities editor." This is a configuration gap, not a transient failure.

xcodebuild output
error: Signing for "App" requires a development team. Select a development
team in the Signing & Capabilities editor.
(in target 'App' from project 'App')

Common causes

No team configured for automatic signing

Automatic signing needs a DEVELOPMENT_TEAM and an Apple Developer account logged in. A CI runner has neither unless you provide them, so signing cannot proceed.

Signing a build that does not need it

Simulator builds and many unit-test runs do not need a real signing identity. Leaving signing required forces a team even when one is unnecessary.

How to fix it

Skip signing for simulator builds and tests

If you only run on the simulator, disable code signing so no team is required.

Terminal
xcodebuild test -scheme App -destination 'platform=iOS Simulator,name=iPhone 16' \
  CODE_SIGNING_ALLOWED=NO

Provide a team and signing assets for device builds

For archives/distribution, supply the team ID and import the certificate and profile into a keychain (e.g. via fastlane match or a manual import step).

Terminal
xcodebuild archive -scheme App \
  DEVELOPMENT_TEAM=ABCDE12345 \
  CODE_SIGN_STYLE=Manual \
  PROVISIONING_PROFILE_SPECIFIER="App Distribution"

How to prevent it

  • Use CODE_SIGNING_ALLOWED=NO for test/simulator jobs that never need signing.
  • Manage real signing assets with fastlane match or a secured keychain step.
  • Keep the team ID in a CI secret, not committed to the project.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →