You can now easily request access to managed capabilities for your App IDs directly from the new Capability Requests tab in Certificates, Identifiers & Profiles > Identifiers. With this update, view available capabilities in one convenient location, check the status of your requested capabilities, and see any notes from Apple related to your requests. Learn more about capability requests.
Certificates, Identifiers & Profiles
RSS for tagDiscuss the technical details of security certificates, identifiers, and profiles used by the OS to ensure validity of apps and services on device.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi folks,
I'm trying to generate a provisioning profile that includes both Healthkit and MusicKit entitlements.
The healthKit pieces if fine, and included in the profile. However, despite selecting Musickit under services in the ID setup, the entitlement doesn't seem to be included in the profile.
Other steps taken: Setup the app in App Store Connect, generated a media ID and Key. Tried both automatic and manual signing.
Are there specifics tricks to getting this one to work?
I have two certificates in my Accounts>Manage Certificates section. One is active, the other is greyed out with a status of "Not in Keychain". I only have ONE certificate in the developer account online.
Timeline:
Had an issue with fastlane codesigning and was trying to resolve that. In that attempt I deleted my related Certificates from my keychain
Xcode showed them as disabled (greyed out) and not in Keychain.
Look up how to resolve, need to revoke certificates in Developer account online. I go and revoke those certificates. Nothing changes
I create new certificate and try to add it to xcode>account>certificate managment>"Apple Development". Get an error saying I can't add a new can't do that because a certificate is already pending.
I waited a day because I assumed like somethings with apple, updates are not immediate.
I come back the next day and am able to add a new certificate. However, the previous one that is greyed out and reads "Not in Keychain" under Status, is still there.
How do I remove that "Not in Keychain" certificate? I emailed developer support and they directed me here.
I have certificates in my xcode>settings>account>manage certificates that I cannot get rid of. I know that they are linked to certificates in developer.apple.com but I've removed them from there and they persist in xcode.
I have one that says "Not in Keychain", which is true. I deleted all the keychains related to these accounts in an attempt to fix something.
I also have ones that say things like "Missing Private key"
Our setup is that we have one main account "Company Inc." which I am setup to be an Admin in. I created a certificate under my credentials and added it to my keychain and showed up properly in xcode but I still have the other ones.
HOW DO I REMOVE THEM :sob:
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Signing Certificates
Developer ID
I'm trying to setup a macOS 26 build environment in a VM (using UTM and the virtualization framework Apple provides).
I have Xcode 26 installed and have logged into my Apple ID and verified that the team and other configuration looks fine in Xcode settings.
When trying to build the macOS app, I see errors saying the VM's device ID has not been registered. I have confirmed that the device ID is registered both in the Provisioning portal AND the downloaded .provisionprofiles (in Library > Developer > Xcode > UserData).
This problem appears on multiple targets (e.g. the main app and extensions).
If I try to manually provision the app, using the Provisioning portal, I can build the product, but it will not launch because of Gatekeeper issues.
Finally, signing to run locally doesn't work either. As the app launches, frameworks refuse to load because Team IDs don't match. With ad hoc provisioning, there are no Team IDs.
I've come to the conclusion that this just isn't possible.
Which is a shame because I need to support products with a build environment on macOS 15 and cannot move over to macOS 26 yet. I suspect many developers outside of Apple are in a similar position.
I tried to create a new IOS provisioning profile and re-apply it to the app using Xcode to build it, but I got into trouble.
The build is good, but it bounces when running the app.
I would appreciate it if you could let me know what to do.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Hello,
My project fails to build/run on a physical device or archive, due to a persistent provisioning error.
Exact Error: Provisioning profile "iOS Team Provisioning Profile: com.huiwan.Ohra-Journal" doesn't include the BGTaskSchedulerPermittedIdentifiers entitlement.
I have already performed extensive troubleshooting, and all local configurations appear to be correct:
Capabilities: "Background Modes" with the "Background processing" option is enabled in the target's "Signing & Capabilities" tab.
Info.plist: The Permitted background task scheduler identifiers key is present in the target's Info.plist, and it contains the correct task identifier (com.huiwan.ohra-journal.refresh).
Entitlements File: The .entitlements file is correctly configured by Xcode.
Full Reset: I have tried a complete reset procedure, including deleting ~/Library/Developer/Xcode/DerivedData and ~/Library/MobileDevice/Provisioning Profiles/, restarting Xcode, and letting the automatic signing system regenerate the profile from scratch. The issue persists.
Despite all these correct local settings, the provisioning profile automatically generated by Xcode is consistently missing the required entitlement. This strongly suggests a server-side issue with the provisioning service for my App ID (com.huiwan.Ohra-Journal).
I filed a bug report on the Feedback Assistant (FB20268285) a week ago but have not received a response. This issue is completely blocking my development and ability to submit the app.
Could you please investigate the status of my App ID and the provisioning services associated with it?
Thank you.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Xcode Server
Xcode
Signing Certificates
Developer ID
Hello,
Recently our team requested the "Notification (NSE) filtering" capability. Our request was rejected but we sent a new request with a more detailed explanation of our need.
However if we go check the status of the request in the Capability Requests tab the status is "No requests". We sent the new request yesterday.
Is it even possible to request a capability after a rejected request? We really need the capability and the absence of it is blocking our progress.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
I am a complete novice and I find that I cannot restore or delete the “Apple Development” certificate (I only use it for signing).
From what I understand, you need to be in a program to manage certificates, but I have no intention of distributing any applications and, from my point of view, it makes no sense to pay.
Am I wrong or am I doing something wrong?
Notes:
This happened after I installed Tahoe on a new installation.
I was able to restore it using a copy of the keychains folder I had from Sequoia.
Xcode (Apple Accounts - Manage Certificates) now shows me two certificates, indicating that one is not in the keychain and cannot be deleted.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
I’m running into an issue where the com.apple.developer.storekit entitlement is not being included in provisioning profiles, even though my App ID is properly configured for In-App Purchase.
Entitlements file: explicitly includes
<key>com.apple.developer.storekit</key>
<true/>
Capability: In-App Purchase is enabled in the Apple Developer Portal and shows as “Enabled.”
What I’ve tried:
Automatic signing in Xcode → profiles generated, but missing com.apple.developer.storekit
Manual signing → deleted and recreated provisioning profiles multiple times; entitlement still missing.
Waited several hours for possible propagation.
Verified that my in-app purchase products are set up correctly.
Error message:
Provisioning profile "iOS Team Provisioning Profile: zu.inniu" doesn't include the com.apple.developer.storekit entitlement
Question:
Has anyone else encountered this? Is there a step I might be missing to get StoreKit entitlements included in provisioning profiles, or could this be a backend issue that needs escalation through Apple DTS?
This is blocking me from building my app for physical devices, so any guidance would be greatly appreciated.
Thanks in advance!
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Entitlements
In-App Purchase
I am able to sign my application when logged in to the machine, however when build is running in CI (Jenkins), I get this:
"Warning: unable to build chain to self-signed root for signer.."
We just renewed or certificates, so I am not sure about previous procedure, but it used to work without temporary keychain and stuff, I believe.
What should be the recommended way to sign an application on CI?
What keychain should we use? system? temporary? other method?
Thanks,
Itay
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Hi, hoping someone can help here.
I recently updated my Mac to macOS 15 (Tahoe) and am using Xcode 15+ (possibly 16). I’m working on a Flutter app and testing on a real iPhone device.
Here's the situation:
I’m using the free Apple Developer account.
My signing certificate and provisioning profile both show as valid and active in Keychain and says "signing..." in Xcode.
When I build and run the app from Xcode, it works completely fine on a simulator.
But when I try to run the same project from VS Code using flutter run, whether on an simulator phone or my personal iphone, I get a code signing error, specifically:
Failed to codesign Flutter.framework with identity...
I believe the app is set to use the correct Team ID because it says my name and (team) (my team ID isBDKUKWVRBY), and I can see my certificate in Keychain under "My Certificates".
What I’ve already tried:
flutter clean
pod install / pod update
Manually selecting my team in Xcode Signing settings
Restarting my machine and VS Code
Confirming the same project builds on other machines
Verified provisioning profile is assigned to the project in Xcode
deleting and recreating a certificate
I have even had AI inside VS code take a shot at it and that couldn't fix either
My question:
Why would VS Code / Flutter not be able to use the same certificate and signing setup that works in Xcode? Is this an issue with Flutter tooling on macOS 15, or do I need to reconfigure signing differently now?
Any suggestions or fixes would be greatly appreciated!
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Hi,
My understanding from this information:
"
https://developer.apple.com/support/certificates/
iOS Distribution Certificate (in-house, internal-use apps)
Users will no longer be able to run apps that have been signed with this certificate. You must distribute a new version of your app that is signed with a new certificate.
"
is that even if I re-sign the app with a new Provisioning Profile based on a new Distribution Certificate the apps will stop working. I need to re-build my apps with a new Distribution certificate+Provisioning profile, when distributing in-house, right?
I can see that the apps continue to function when I re-sign them with a new Provisioning Profile, but according to the information above they will stop working the day (day after) the Distribution certificate they were built with expires.
/Rikard
We've been creating iOS apps for a few years now, but when I tried last month, I got an error in my XCode that says:
No profiles for 'com.os.hub.mth2' were found
Xcode couldn't find any iOS App Development provisioning profiles matching '***.***.***.***'.
I'm not sure if it's the cause or not, but when I look at the signing certificates, the Developer ID Application Certificate says:
Missing Private Key
The weird part of that is that I see a private key with this name in my Keychain access, so I'm not sure what's wrong.
There has been a significant time gap between now and the last time we created a mobile app, so I'm not sure if something changed in XCode/MacOS to cause this issue, or if something expired.
I'd appreciate any advice.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
App Store Connect
Notarization
Developer ID
I have 14 total devices, from way back. I am currently in a financial bind and can't renew just yet. BUT I am at past my time to reset the device list back to zero.
But the screen to do that is behind the paid account. Catch 22
Can we fix it?
As it stands I must email tech support, but this is a bug so I posted
New to working with xcode and building apps. I started last weekend, and deploying to my usb connected iPhone 16 was working great all week. Yesterday, I upgraded to a paid developer account to start using TestFlight, and I could no longer deploy to my phone.
Failed to install embedded profile for com.spred.spred-alpha : 0xe800801a (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).)
i using automatic provisioning - not a custom provisioning profile.
i have tried:
deleting all the certificates in keychain for my developer account and recreating them, and also doing the same in the developer portal.
logging out and logging back in with my developer id in xcode
deleting the app bundle directory and all other associated files in the Xcode/DerivedData directory
reinstalling Xcode
cleaning my build directory and trying again.
changing the bundle identifier to a new name. (It always matches the portal app name)
Among other things. It just won’t work. I can run the app inn a simulator, but not get it deployed to my phone.
what else can I do? The only things I can think of are that somehow Xcode is still stuck using the free account somehow, or that the free account cert originally used expired after 7 days, and now I’m in some stuck state.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Hello, when building and signing my application in a Github actions workflow, I am facing an issue on the latest version of xCode (16.4). This issue is resolved by downgrading to 16.3.
My CI/CD pipeline is running headless and installing provisioning profile to ~/Library/MobileDevice/Provisioning Profiles.
Hi,
I am experiencing an issue where Xcode displays a "Provisioning profile doesn't support the capability" error for the User Assigned Device Name capability, despite it being approved by Apple and visible in our provisioning profile on the Developer Portal.
Background
We have completed and submitted the required capability request form to Apple for the User Assigned Device Name capability and received approval. The capability appears correctly in our provisioning profile on the Apple Developer Portal and shows among the enabled capabilities alongside other standard capabilities like In-App Purchase and Push Notifications.
Issue
However, Xcode consistently displays the error message when trying to enable the User Assigned Device Name capability in our project settings, preventing successful builds with this functionality.
Troubleshooting Steps Attempted
We have tried multiple troubleshooting steps including:
Regenerating provisioning profiles
Performing clean builds
Clearing DerivedData
Manually installing profiles
Adding the com.apple.developer.device-information.user-assigned-device-name entitlement manually to our entitlements file
Toggling automatic signing on and off
Environment Details
Xcode Version: 16.4 (16F6)
iOS Deployment Target: iOS 13
Profile Type: Distribution provisioning profile
Capability: User Assigned Device Name
Despite the capability being approved by Apple and visible in our provisioning profile, Xcode does not recognize it. This appears to be a synchronization issue between the Apple Developer Portal and Xcode's capability validation system.
Has anyone encountered similar issues with recently approved capabilities, specifically the User Assigned Device Name capability? Could you please provide guidance on how to resolve this capability recognition issue? Any suggestions for resolving this discrepancy between the Developer Portal and Xcode would be greatly appreciated.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Xcode
Provisioning Profiles
I am trying to set up code signing for my macOS/Tauri app and I’m running into a problem with my Developer ID Application certificate in Keychain Access.
Steps I followed:
Generated a CSR on my Mac using Keychain Access → Certificate Assistant → Request a Certificate From a Certificate Authority.
Uploaded the CSR to the Apple Developer portal.
Downloaded the resulting .cer file and installed it in my login Keychain.
The certificate appears under All Items, but it does not show under My Certificates, and there is no private key attached.
What I expected:
The certificate should pair with the private key created during CSR generation and show under My Certificates, allowing me to export a .p12 file.
What I’ve tried so far:
Verified that the WWDR Intermediate Certificate is installed.
Ensured I’m on the same Mac and same login Keychain where I created the CSR.
Revoked and regenerated the certificate multiple times.
Tried importing into both login and system Keychains.
Problem:
The certificate never links with the private key and therefore cannot be used for signing.
Has anyone experienced this issue or knows why the certificate would fail to pair with the private key in Keychain Access? Any workaround or fix would be greatly appreciated.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Signing Certificates
Code Signing
Developer ID
Hi,
I need to bundle an additional binary along my yet published application.
It is a Audio Unit test application.
My yet published application implemented Audio Unit plugin support.
But upload is always rejected:
Validation failed (409)
Invalid Provisioning Profile. The provisioning profile included in the bundle com.gsequencer.GSequencer [com.gsequencer.GSequencer.pkg/Payload/com.gsequencer.GSequencer.app] is invalid. [Missing code-signing certificate.] For more information, visit the macOS Developer Portal. (ID: ****)
I have followed the instructions here: Embedding a helper tool in a sandboxed app
but no luck. Does anyone know whats going on?
I use Transporter to upload the application, the embedded.provisioningprofile is copied from Xcode build and code signing is done manually.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
macOS
Provisioning Profiles
Code Signing
Hi!
We are trying to request the SensorKit entitlement (com.apple.developer.sensorkit.reader.allow) for a research app we’re working on.
When we go to Apple Developer → Certificates, Identifiers & Profiles → Identifiers, we see the SensorKit capability listed under "Capability Requests", but:
There’s no form or button to submit the request, unlike with other capabilities.
We tested this using an Account Holder role, and also tried requesting other capabilities — which do show the form correctly, so this seems to be an issue specific to SensorKit.
We’d appreciate any guidance on:
Whether this is a known issue with the SensorKit request flow.
If there’s an alternative way to request this capability while the form is unavailable.
Thanks in advance!