Fix: “Signing for target requires a development team” in Xcode

Why this happens

Xcode needs a signing identity and a provisioning profile to install an iOS app on a physical device. The error Signing for "target" requires a development team means the app target does not have a team selected, or Xcode cannot use the selected team to prepare signing.

A team is associated with an Apple developer account. Xcode can use that account to create or select the signing assets for your app when automatic signing is enabled. If you have not added an account to Xcode, or the app target is assigned to no team, the build cannot complete for a device.

This is separate from a Swift compile error: changing source code will not resolve a missing signing configuration. The older message Code signing is required for product type 'Application' in SDK 'iOS 10.0' describes the same underlying issue: Xcode is trying to build an iOS application without usable signing settings.

How to fix it

1. Add your Apple ID to Xcode

1. Open Xcode and choose Xcode > Settings from the menu bar. In older Xcode versions, this window may be called Preferences.
2. Open Accounts.
3. Click the add-account button and sign in with the Apple ID associated with your development team.
4. Confirm that the team you need appears for that account.

An Apple ID used for development and a paid Apple Developer Program membership are not the same thing. If you only need to install a development build on your own device, a personal team may be available. Distribution and some team capabilities require the appropriate membership and permissions.

2. Assign the team to the app target

1. In the Project navigator, select the blue project icon.
2. Under Targets, select the iOS app target—not just the project entry.
3. Open Signing & Capabilities.
4. Turn on Automatically manage signing.
5. Choose your team from the Team menu.

If the project contains more than one app target, check each target that you intend to build or run. An extension or other separately signed target can have its own signing settings; selecting a team for the main app does not necessarily configure every target.

3. Check the bundle identifier

In the same signing settings, check the Bundle Identifier. It must be a valid identifier that your team can use. If Xcode reports that it cannot create or find a provisioning profile, try a bundle identifier that is unique within your team, then build again.

Keep the identifier consistent with the app you intend to develop. Changing it can make Xcode treat the build as a different app, so do not change an established production identifier just to silence a signing warning.

4. Build for the intended destination

Choose the device or simulator you actually intend to use from Xcode’s run-destination menu. A physical iPhone or iPad needs development signing to install and run the app. Simulator builds do not use an iPhone or iPad provisioning profile in the same way, so if you see this error while targeting a simulator, verify that the selected destination and scheme are correct and that you are not building a separate device destination as part of the operation.

After selecting the team and destination, build again. Xcode may need an internet connection to retrieve or create signing assets. If it reports a specific account, permission, or provisioning-profile problem, resolve that message rather than repeatedly changing unrelated build settings.

5. Check manual signing only if your project requires it

For most development projects, leave Automatically manage signing enabled. Xcode can then manage the development provisioning profile and signing configuration for the selected team.

Use manual signing only when your project or organization explicitly supplies and manages its signing assets. In that case, select a provisioning profile and signing identity that match the app’s bundle identifier and team. A profile for a different app ID or team will not fix the missing-team error.

Avoid copying old instructions that tell you to force a particular signing setting without checking the rest of the configuration. The available options can vary by Xcode version and project, and a manually selected profile can become stale or mismatched.

6. Respond to an “Untrusted Developer” alert on the device

If signing succeeds but iOS displays an Untrusted Developer alert when you launch the app, that is a separate device-trust issue. Follow the trust instructions shown by iOS for the developer profile. The settings location can differ between iOS releases. Trusting the developer does not replace choosing a team or signing the app correctly in Xcode.

How to prevent it

• Keep the Apple ID you use for development added to Xcode’s Accounts settings.
• Set the team on the app target, and check additional targets that need signing.
• Leave automatic signing enabled unless you have a reason to manage profiles manually.
• Use a bundle identifier that belongs to the selected team.
• Check the selected run destination before troubleshooting signing errors.

FAQ

Do I need a paid Apple Developer account to run an app on my iPhone?

Not necessarily. Xcode may provide a personal team for development with an Apple ID. App distribution and other capabilities can require an eligible paid membership and appropriate team access.

Why does Xcode still show the error after I added my Apple ID?

Adding an account alone does not assign a team to the app target. Open that target’s Signing & Capabilities settings, enable automatic signing, and select the correct team. Also check other targets if the project has extensions.

Should I change Code Signing Style to Manual?

Usually not. Automatic signing is the simplest choice for development because Xcode manages the provisioning profile. Use manual signing when you have matching signing assets that your project or organization requires you to select yourself.