Connect your iOS bundle ID, signing, and app record

Your iOS build won’t sign or upload, and the error is pointing at identifiers and certificates. Those settings connect the build to its Apple developer team and App Store Connect record. Check that all three point to the same app before trying another upload.

Confirm that you can access the intended developer team and that its membership is active. Have the Account Holder accept required agreements. Record the bundle identifier you plan to keep for this app.

Match the record and build

1. Create the app record in App Store Connect before uploading. Select its platform, name, language, bundle ID, and internal SKU.
2. Set the same bundle ID in your build configuration. Similar app names don’t make different identifiers interchangeable.
3. Use that team’s distribution signing configuration. If your build provider manages certificates and provisioning profiles, follow its account-connection steps.
4. Check that enabled capabilities match the signing configuration. Ask the build provider to identify the specific mismatch in the signing log if they don’t.
5. Set the app version and build number, then create a distribution build with the required toolchain.
6. Upload with your supported build tool or service. Wait for processing before selecting the build in App Store Connect.

Check that the upload was accepted and, after processing, that the build appears under the app record you expected.

If signing still fails

Work through the error in this order: team, bundle ID, signing material, capabilities, then build configuration. Don’t start by revoking shared certificates; other apps or collaborators may rely on them.

If the upload succeeded but the build is missing or says Missing Compliance, follow the build-processing guide. Recreating the app record won’t resolve every processing problem.