Xcode: signing requires a development team
Select the correct Apple account and team for the target that Xcode names in the signing error.
Open the named target in Xcode, choose Signing & Capabilities, and select the intended Team. If the team is absent, add the Apple account in Xcode Settings. Check every app and extension target that needs signing.
Try these fixes in order
Find the target named in the issue
Open Xcode’s Issue navigator and read which target and build configuration failed. An app extension, widget, or test host may have its own signing settings; changing only the project-level setting may not affect it.
Choose the intended Apple account and team
In Xcode Settings > Apple Accounts, sign in to the account that belongs to the development team. Select the affected target, open Signing & Capabilities, and choose its Team. A personal team can be suitable for local device development, while distribution requires the appropriate program and permissions.
Check bundle IDs and signing mode
Confirm that the target’s bundle identifier belongs to the selected team and that automatic or manual signing matches your project workflow. Do not change a released app’s bundle ID merely to suppress a signing error.
Build for the intended destination
Retry with the actual device or archive destination. If the message changes to a missing profile or entitlement mismatch, diagnose that exact issue separately; the team selection was only one part of signing.
Interpret what you see
The error names the app target
What it suggests: The app has no selected team for this build configuration.
Next check: Select the intended team in that target’s Signing & Capabilities, then rebuild for the same destination.
Only a widget or extension fails
What it suggests: Signing belongs to each target, not only the containing app.
Next check: Open the named extension target and check its team and unique bundle identifier separately.
Simulator succeeds but device fails
What it suggests: A simulator build may not require the same physical-device signing assets.
Next check: Check account membership, device registration, and automatic versus manual signing for the device build.
Why this happens
- No team is selected on the affected target.
- The required Apple account or team is absent from Xcode’s account settings.
Still not working?
If you are a contributor to an organization’s app, ask its account administrator to confirm your membership and signing access. Do not share certificates or private keys in a support post.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.