Xcode: no provisioning profiles were found
Match the profile type, bundle identifier, team, capabilities, and build destination.
Read the missing profile type and bundle ID in Xcode’s full error. Verify the affected target’s team and signing mode; a development run, App Store archive, and Developer ID distribution need different signing assets.
Try these fixes in order
Read the complete signing issue
Note the target, bundle identifier, platform, configuration, and requested profile type. An extension may be the failing target even when the main app signs successfully.
Check automatic versus manual signing
In the target’s Signing & Capabilities editor, confirm the Team and whether Automatically manage signing is selected. With automatic signing, allow Xcode to manage the matching assets using an account with the required permissions. With manual signing, select a profile that actually matches the target.
Compare identifiers and entitlements
Confirm that the profile’s App ID matches the bundle ID and that required capabilities and entitlements are enabled for the same team. Check device registration for a development profile where applicable.
Retry the same action and record the next issue
Build or archive for the same destination. If Xcode now reports an entitlement, certificate, or account-permission error, use that more specific message rather than repeatedly recreating profiles.
Interpret what you see
The named bundle ID belongs to an extension
What it suggests: A profile for the main app will not cover a separate extension identifier.
Next check: Check the extension’s App ID, capabilities, and team; let automatic signing create a matching development profile.
The correct profile exists in the portal but Xcode rejects it
What it suggests: The profile may target a different certificate, device, or distribution method.
Next check: Compare the profile’s App ID, certificate, entitlement set, and build configuration with the failing target.
Only CI fails
What it suggests: The runner may lack a certificate private key or permission to manage profiles.
Next check: Check keychain access and signing mode on the runner before regenerating profiles on a developer Mac.
Why this happens
- The expected profile is missing for the bundle ID or distribution method.
- Automatic signing cannot create an asset because the team, account access, or capability configuration is wrong.
Still not working?
Avoid importing an unrelated profile or turning off code signing for a device or distribution build. A simulator-only development build has different signing requirements from installing on hardware or archiving.
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.