Signing for "App" requires a development team. Select a development team in the Signing & Capabilities editor
No Apple developer team is selected for the target, so Xcode can’t sign the app.
Seen on:
iOS
Meaning
Every target that builds for a device (app, extensions, widgets, CocoaPods resource bundles on Xcode 14+) needs a team. A free personal team works for device testing.
Common causes
- Team not selected (new project/cloned repo)
- Extension or Pods target without a team
- Logged-out Apple ID in Xcode
⚡ Quick fix
- Select the team in Signing & Capabilities for each target
- Sign in under Xcode → Settings → Accounts
- For Pods bundles set CODE_SIGNING_ALLOWED=NO in a post_install hook
Detailed fix by platform
Ruby
- swift
post_install do |installer| installer.pods_project.targets.each do |t| t.build_configurations.each { |c| c.build_settings['CODE_SIGNING_ALLOWED'] = 'NO' } end end
How to diagnose
- Targets — Which target is named?
- Account — Signed in?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Cannot preview in this file SwiftUI Preview: Cannot preview in this file — the preview crashed / failed to build
- Command CodeSign failed Command CodeSign failed with a nonzero exit code (errSecInternalComponent / resource fork, Finder information not allowed)
- doesn't include signing certificate Provisioning profile "x" doesn't include signing certificate "Apple Development: Name (ID)"
Most viewed in iOS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026