Xcode build fails because an app extension target has no development team
Code signing is required for product type 'Application' in SDK 'iOS'Short answer
Xcode signs every target in an app, including extensions such as a sticker pack. The error means one target has no team. Open that target's Signing & Capabilities tab, turn on automatic signing and pick the same team you use for the main app. Add your Apple ID first if the Team menu is empty.
Fix it fast
1Find out which cause you have
Find which target has no team. List the targets, then open each one in the project editor and look at its Team field. Do not look only at the main app.
# Xcode: project editor > pick each target in the pop-up menu > Signing & Capabilities > Team2Match what you see, then jump to its fix
What does the error look like?
Code signing is required for product type 'Application' in SDK 'iOS'requires a development team
Cause 1 of 2
One target, usually an extension, has no team selected
1Check
A target's settings are separate from the project's, and each target needs its own team. In the project editor choose the target from the pop-up menu, open Signing & Capabilities and read Team.
# Xcode: Signing & Capabilities > Team, for the failing target2Fix
Select the failing target, open Signing & Capabilities, expand Signing if needed, enable automatic signing and choose your team in the Team menu. Apple requires every target in the project to belong to the same team, so repeat for each target.
# Xcode: select target > Signing & Capabilities > Automatically manage signing > Team3Verify
Build again. The error is gone and every target shows the same team.
# Product > Build in XcodeConfirmed by help.apple.com
Cause 2 of 2
No Apple ID is added to Xcode, so the Team menu is empty
1Check
Teams come from the accounts signed in under Xcode's Accounts settings. If you are not in the Apple Developer Program, Xcode creates a personal team for your Apple ID.
# Xcode > Settings > Accounts: is your Apple ID listed?2Fix
Click Add Account next to Team (or add the Apple ID in Accounts settings), then choose that account's team from the Team menu.
# Xcode: Signing & Capabilities > Team > Add an Account...3Verify
The Team menu lists your team and the build proceeds past signing.
# Product > Build in XcodeConfirmed by help.apple.com
How do I stop it coming back?
- After adding any extension or sticker target, set its team straight away.
- Use one team for every target in the project.
- Keep the Apple ID signed in under Xcode's Accounts settings on every build machine you use.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
Xcode finds no provisioning profile for your bundle ID
Xcode couldn't find any provisioning profiles matching
Xcode has no development profile that fits your bundle ID, team and device.
4 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fix