Certificates, Identifiers & Profiles

RSS for tag

Discuss the technical details of security certificates, identifiers, and profiles used by the OS to ensure validity of apps and services on device.

Certificates, Identifiers & Profiles Documentation

Posts under Certificates, Identifiers & Profiles subtopic

Post

Replies

Boosts

Views

Activity

New Capabilities Request Tab in Certificates, Identifiers & Profiles
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.
0
0
3.7k
Jun ’25
productbuild and Keychain Access concern
productbuild cmd: productbuild --component /Applications/Very\ Large\ Number\ Calculator.app /Applications --sign "3rd Party Mac Developer Installer: Alain_B " /Applications/Very\ Large\ Number\ Calculator.pkg Give this error: Cannot write product to "/Applications/Very Large Number Calculator.pkg". (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Alain_B ”.) But Keychain Access show "3rd Party Mac Developer Installer" is in Certificates: 3rd Party Mac Developer Application: 10 digits (64......J5) certificate login Nov 10, 2027 at 8:02:04 AM Alain_B private key login 3rd Party Mac Developer Installer: Alain_B (64......J5) certificate login Apr 19, 2027 at 8:32:51AM Apple Development: Alain_B (35......P5) certificate login Oct 19, 2027 at 9:29:59 AM Apple Development: Alain_B (Alain_B ) private key login Apple Distribution: Alain_B (64MZBY64J5) certificate login Oct 26, 2027 at 9:36:16 AM Alain_B private key login Apple Root CA certificate login Feb 9, 2035 at 4:40:36 PM Apple Worldwide Developer Relations Certification Authority certificate login Feb 19, 2030 at 7:00:00 PM Apple Worldwide Developer Relations Certification Authority certificate login Mar 18, 2036 at 8:00:00 PM Developer ID Certification Authority certificate login Feb 1, 2027 at 5:12:15 PM Developer ID Certification Authority certificate login Sep 16, 2031 at 8:00:00 PM What can I do ? Thank you.
3
0
217
1d
Can't build blocked by agreement
I recently switched from a personal to organization account, but the organization name didn't update in apple store. Also, i'm getting this error in codemagic "GET https://api.appstoreconnect.apple.com/v1/certificates?limit=100&sort=displayName&filter%5BcertificateType%5D=IOS_DISTRIBUTION returned 403: A required agreement is missing or has expired. - This request requires an in-effect agreement that has not been signed or has expired." And I already signed all the agreements, no warning boxes in apple store connect. Any suggestions?
1
0
170
1d
Developer ID Installer installation
I am trying to renew my Developer ID installer certificate in order to sign our custom pkgs for MDM deployment. I have sent a certificate signing request to the owner of our Apple Developer account and they issued a new Developer ID installer certificate using that CSR and sent me the resulting certificate. I am now having issues signing pkgs. I have the cert, the private key and the intermediate certificate but any pkg I sign is treated as not signed and gatekeeper does not like it. Is it not possible to Developer ID Installer certificates to non account holders? or am I doing something wrong? Any assistance would be great.
1
0
55
3d
0xe8008018 after account reinstatement — online authorization still returns REJECT_PROFILE for a valid certificate and profile
Our developer account was suspended and later reinstated. Membership is active again, but every development-signed build from our team still fails to install on a registered device: Failed to verify code signature of …/testIPA.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) MIInstallerErrorDomain error 13, LibMISErrorNumber = -402620392 We have gone as far as we can locally. The device log shows the rejection comes from Apple's server, so this can only be resolved by the Apple team that owns that service. I'm posting here to reach that team. What the device log shows The certificate and profile pass local validation. The install fails at the online authorization step, where the server rejects the profile: installd: [com.apple.mis:mis] Performing online authorization. online-auth-agent: (CFNetwork) … received response, status 200 online-auth-agent: [com.apple.mis:mis] The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,…,"validity":33} online-auth-agent: [com.apple.mis:mis] Permanently rejected profile: … installd: [com.apple.mis:mis] validation failed because of failing online authorization (-402620392) Troubleshooting stepsCertificate is valid (2026-11-03 → 2027-11-03); Apple OCSP returns good. codesign --verify --deep --strict passes. The Xcode-managed profile contains the certificate and the device; the device lists it as valid. Device clock is correct, Developer Mode is on, and the authorization request reaches Apple (HTTP 200). Revoked and recreated the development certificate, regenerated the profile: same result. New empty project with a never-used bundle ID: same result. Control: same Mac, same iPhone, same project signed with a different team's development certificate installs fine. The only variable is the team. Nothing on the Mac, the device, or in the project changes the outcome. Our working hypothesis When the account was suspended, the team was blocked in the service that authorizes signed apps at install time. When the account was reinstated, membership was restored but that block was not lifted. So the account looks normal everywhere we can see it, while the authorization server still treats the team as blocked. This is a hypothesis, not something we can confirm from our side. Two things point to it: Developer Support says the account is in good standing, yet the server answers REJECT_PROFILE for a valid certificate and profile. I found a thread here from a developer whose account was suspended and reinstated and who then could not sign. Developer Support could not resolve it, and it started working again by itself about a year later. That matches the wording of the suspension notice, which says developer services cannot be used for one year. It looks as if the signing restriction runs on its own timer and does not follow the account's reinstatement. What we have already tried with Apple I went through several rounds by email with Developer Support under case 103007200283 and supplied the screen recording and IPA they asked for. The case was passed to engineering. The answer was that the account status is normal, that they could not help further, and that I should look for help on the Forums. I have read many threads here about 0xe8008018. Most have very few replies, and none has a solution that applies when the certificate is valid and the rejection comes from the server. The core problem: which team owns this? I think the reason this has not been resolved is that the case never reached the right team. There are two candidates: The team that manages account status and permissions. They see an active membership, so they answer that the account is normal. The engineering team that runs the signing and install authorization service. That service is what rejects us, and only they can see or clear the state on that server. Our evidence points to the second. Developer Support has so far answered from the first. Environment Xcode 27.2 (27B52), macOS 27.0.1 iPhone 14 Pro, iOS 26.5.2 (23F84) Automatic signing, Apple Development certificate, team provisioning profile
0
0
287
1w
Bundle identifier after moving from a Personal Team to a paid Apple Developer Program enrollment
Application Group identifier unavailable after moving from a Personal Team to a paid Apple Developer Program enrollment Hi everyone, I built an app in Xcode using a Personal Team (free, signed in with my Apple ID) with the bundle identifier com.jcsnp.Minutely. My paid Apple Developer Program enrollment has been active since 5 Nov 2026, and I'm now trying to build and run the app under the new team. Xcode is blocking me on the App Group and the provisioning profile. Environment macOS 27, Xcode 27.2, iOS target 26.6 Paid enrollment: individual account, active since 5 Nov 2026 Errors Communication with Apple failed. An Application Group with Identifier 'group.com.jcsnp.Minutely' is not available. Please enter a different string. No profiles for 'com.jcsnp.Minutely' were found Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jcsnp.Minutely'. What I've tried Cleaning the build folder. The errors remain. Questions The App Group group.com.jcsnp.Minutely is reported as unavailable. Is it still registered to my old Personal Team, or to another account? If so, how do I release it or move it to the new team? Does the Personal Team's registration of the bundle ID need to be removed before com.jcsnp.Minutely can be registered under the paid team? Is there a recommended order for setting this up: registering the App ID and App Group in the developer portal first, then letting Xcode generate the profile? Thanks in advance for any guidance.
5
0
356
1w
Unexpected com.apple.macl extended attribute on macOS app bundle and provisioning profile
Hello, I'm investigating an unexpected com.apple.macl extended attribute while preparing a macOS application for Developer ID signing. I have observed the attribute in two places: On the root of an application bundle, where the recorded 72-byte attribute value changed during testing. On a Developer ID provisioning profile, where a 72-byte com.apple.macl value is present before signing. I also created a minimal Xcode reproducer that independently demonstrated the unexpected attribute behavior. I have not established which process creates or modifies the attribute, or whether its presence affects code-signing integrity. My questions are: Is this expected macOS behavior for app bundles and provisioning profiles? What is the recommended supported method to identify which system component creates or modifies this attribute? How should developers handle this situation when preparing and validating Developer ID signed applications? I would prefer to understand the cause rather than remove or suppress the attribute without knowing its security implications. Thank you.
2
0
192
1w
Apple TV as iPod in Apple Developer Center
I have a bizzare issue with my Apple TV that is shown as "iPod" in Apple developer portal. It's correctly visible in Xcode as Apple TV, but when I add it to developer portal it says "iPod". The problem is since it's there as an iPod I can't use it to my provisioning profile to build on the device Anyone has any idea how this can be solved? [Edited by Moderator]
5
1
1.8k
1w
Updating App - Validation Hell - 90286, 91130
Updating an App for the first time since 2011. Build, Analyze, Archive all successful. Automatically Manage Signing checked. Validation fails with 90286 - Invalid code signing entitlements, and 91130 - Invalid Provisioning Profile dozens of times after tweaks, clean builds, trying manual signing (thought I was done with that), etc. For 90286 it seems my Developer ID , e.g. 346JXXXXX (not Team ID, QZ99XXXXX) is the prefix for the bundle ID, com.company.app-name and that generates the error? For 91130 it's invalid "com.apple.application-identifier" which I assume is the same issue with a Developer ID instead of a Team ID. The original version of the app was QZ99XXXXX.com.company.app-name. I even changed the bundle identifier in Xcode to that, and got this: App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Yes, the original app name is being used for an app in my account. I was trying to update the app, checked all the boxes, added update text, but of course there was no build to upload. Would appreciate any help.
21
0
3.6k
1w
ITMS-90035: designated requirement uses NFD form of "İ" in team name; team name change pending
My first app cannot be uploaded: every IPA is rejected with ITMS-90035 "Invalid Signature". Setup: individual account, Team ID V7F74UFRBN, Xcode 27.0, macOS 26.6.2, Cloud Managed Apple Distribution certificate. My team name contains the Turkish letter "İ" (TELLİ). The certificate common name stores it as NFC (C4 B0), but the designated requirement written at signing time stores it as NFD (49 CC 87): certificate leaf[subject.CN] = 0x...54454c4c49cc87... so "codesign --verify --deep --strict" reports "does not satisfy its designated Requirement" for the app and every embedded framework. This looks like FB24633162 / thread 843700. I asked Developer Support to change my team name to the ASCII form "Mehmet Kaan TELLI" (case 103017162953) but have had no reply after several days, and the phone option shows as unavailable. Questions: Can DTS help escalate the team name change? Until then, is there a supported way to sign so the upload passes?
2
0
99
1w
Can I have my MAS and my "Indie" app share the same credentials for TCC (GateKeeper)?
I release my app both in the MAS and on my website. I use the same signing credentials, but necessarily different certs (Apple Development vs. Developer ID). When I run the MAS app and then run the other version, or vice versa, I need to re-authenticate the many privacy permissions each time (Finder AppleScript, Network browse, Full Disk Access), which is tedious and keeps causing trouble for other users because some of these require a tcc reset (which my app currently invokes manually, which I consider a hack, though). So, am I doing something wrong or is it really no possible to have both signed apps use the same identity with TCC?
3
0
166
2w
Paid team’s signing identity rejected on device (0xe8008018) since free-to-paid upgrade; same app installs under a free team
Since upgrading my free Apple Developer account to the paid Apple Developer Program (Individual) on September 21, 2026, every app signed with my paid team fails to install on my devices. TestFlight builds work. Error (Xcode Run, devicectl, Ad Hoc export): MIInstallerErrorDomain Code 13 / 0xe8008018 "The identity used to sign the executable is no longer valid." +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:] LibMISErrorNumber = -402620392 What I've established: A brand-new Hello World app with no capabilities fails the same way, so it is not my project, entitlements or widget. The same Hello World signed by a free Personal Team installs on the same iPad (after trusting the developer in Settings). So the device, OS, Xcode and Mac are fine. Fails on iPad Pro 13" M4 (iPadOS 27.0.1 and 27.2), iPhone Air (iOS 27.0.1) and iPhone 15 Pro Max (iOS 26.0.1), with Xcode 27.0, 27.1 and 27.2. Fails with Apple Development signing (Xcode Run) and with an Ad Hoc export signed with an Apple Distribution certificate. codesign verifies the app, the embedded profile contains the signing certificate and the device UDIDs, and the chain (WWDR G3 to Apple Root CA) is valid and not expired. Regenerated the Development and Distribution certificates, cleaned expired WWDR certificates from the keychain, removed profiles on the device, re-paired and toggled Developer Mode. No change. Only apps re-signed by Apple (TestFlight) install. This looks like stale signing state for the team on Apple's side after the free-to-paid conversion. I have an open request with Apple Developer Support (Case-ID 22506476) and Feedback Assistant report FB24912726, but have had no reply in two weeks. Has anyone seen 0xe8008018 on a team that was recently upgraded or converted, and is there anything I can do on my side beyond asking Apple to reset the team's signing identity?
1
0
749
2w
Which certificate for MAS submission? "Apple Distribution" vs "Mac App Distribution"
I am struggling with uploading my Mac-only app to TestFlight. I used to do this with Xcode 13.4.1 for a while without trouble, but now I have built the app with Xcode 27.1 and am getting issues such as ITMS-90885 and ITMS-90288 and I cannot figure out how to make it work. I have now at least realized that I seem to need to create a new provisioning profile because the one was using is missing some entitlement(s). To create a new profile, I need to create also a new certificate at https://developer.apple.com/account/resources/certificates/add But there's already my first hurdle: There are two types that allow upload the to MAS: "Apple Distribution" and "Mac App Distribution". Which one should I choose? I even googled for help but found nothing more than what the above website says. It's not clear what the difference is when I only want to submit to the MAS, and whether choosing the wrong one may already be part of the problem I'm having now with uploading my app. Can someone please explain in more detail if they're having exclusive behavior when using them to upload Mac apps to the MAS and TestFlight?
1
0
211
2w
Give Access to Team to Certs
Hello, New to Apple's system and structure for certs and signing. I've been working with their team to get access for developers on my team to access the correct Certs and sign what they need to so we can push our latest builds out, since this is needed by our CI/CD pipeline. How can I give access to members of my team so they can do the code saying they need to and access the certs they need to? the certs are for dmg and pkg installers on macos.
1
0
228
3w
Receiving message "Unable to find a team with the given Team ID to which you belong" when trying to access Certificates Identifiers & Profiles page
When attempting to access the (Certificates Identifiers & Profiles) page, I receive the message "Unable to find a team with the given Team ID to which you belong". Even while set as a developer or as an admin I still receive the same message above.
8
0
2.5k
3w
Apple Distribution signature fails its designated requirement — possible Unicode normalization issue
App Store Connect rejects my iOS Flutter app with error 90035: “Code failed to satisfy specified code requirement(s).” The error affects the main app executable, App.framework, and Flutter.framework. Environment: macOS 26.5.2 Xcode 26.6 Flutter 3.44.8 Individual Apple Developer Program membership The Release archive and App Store IPA build successfully. The exported IPA is signed with an Apple Distribution certificate and contains the correct TeamIdentifier. However, verification reports: Runner.app: valid on disk Runner.app: does not satisfy its designated Requirement The certificate Common Name contains a non-ASCII character: “Ç”. The generated designated requirement appears to represent this character using a decomposed Unicode form. I suspect a Unicode-normalization mismatch between the certificate Common Name and the embedded designated requirement. I am also unable to create a local Apple Distribution certificate: Xcode Manage Certificates reports: “The data couldn’t be read because it isn’t in the correct format.” The Apple Developer certificate portal reports “An unexpected error occurred” after I upload a valid CSR. Has anyone encountered this issue when an Apple Distribution certificate Common Name contains a non-ASCII character? Is there a supported way to regenerate the cloud-managed certificate or have Apple repair the team’s certificate state? I can provide sanitized codesign output if an Apple engineer needs additional diagnostic information.
17
0
2.2k
3w
After an A → B transfer with no update from B: does expiry of Team A's distribution certificate and provisioning profile affect sign-in or in-app purchases for the installed build?
Hello, We transferred an app from Team A to Team B. The app is live on the App Store, and every build currently in circulation was signed by Team A. Team B has not released any update — no App Store release and no TestFlight distribution — and the app may stay in that state for a considerable time. The distribution certificate and provisioning profile that Team A used to sign the build which is live right now will expire. We would like to confirm that this has no effect on sign-in and no effect on payments for the version that users already have installed from the App Store. Reasoning that applies to both The App Store re-signs the app as part of the distribution process, and the delivered build contains no embedded provisioning profile (TN3125), so neither Team A's certificate nor Team A's profile exists on the device. "Certificates overview" also states that an expired App Store distribution certificate does not affect existing App Store apps, and only prevents uploading new builds signed with it — which the transferor can no longer do in any case. Sign-in Login tokens live in the keychain under an access group whose name is prefixed with Team A's App ID Prefix. Our reading is that certificate and profile expiry has no bearing on keychain access at all, because the access check compares the group string in the binary's entitlements against the item's kSecAttrAccessGroup, and the signing certificate is not an input to that comparison. Is that correct? Payments Our reading is that payments are unaffected on both sides: StoreKit transactions — purchases, renewals, refunds — are handled by Apple's servers and do not depend on the app's signing certificate or provisioning profile; our server-side receipt validation relies on the app-specific shared secret, a 32-character hexadecimal string with no relationship to any certificate, so receipt validation keeps working. Is that correct, or does something break here? One consequence we would like confirmed If Team A ever needed to publish another build under its own account, we assume it would first have to issue a new, valid certificate and provisioning profile — that is, expiry does not affect the installed app, but it does affect Team A's ability to publish anything further. Is that right? Thanks!
1
0
305
3w
Internal enterprise iPadOS application - USB CDC entitlement
Dear Apple Developer Support Team, I am reaching out for assistance with two pending DriverKit entitlement requests. This is my first experience developing an application within Apple's ecosystem, and I recognize that my use case is somewhat unconventional. I may not have reached the appropriate support channel, so I would appreciate your guidance or assistance in directing this request to the correct team. We are currently evaluating the feasibility of adopting iPads for an internal enterprise application that communicates with our proprietary USB devices. These devices use the standard USB Communications Device Class (CDC), exposing a virtual serial port (UART). They work reliably on Windows, Linux, and macOS. To my surprise, I discovered that iPadOS does not provide general-purpose access to standard USB CDC serial devices. Based on my research, the recommended approach appears to be implementing a custom driver using DriverKit. We also use macOS as our primary development and debugging environment, so we would like to maintain a consistent DriverKit-based implementation across both platforms in macOS only for development. On September 30, 2026, I submitted the following entitlement requests: 1. Request GW966578ZB — DriverKit UserClient Access Requested entitlement: com.apple.developer.driverkit.userclient-access 2. Request 3HN2GMDFN5 — DriverKit / USB Transport Distribution Authorization Requested entitlements: com.apple.developer.driverkit com.apple.developer.driverkit.transport.usb Unfortunately, I have not received any response or status update on either request in the three weeks since submission. At this stage, our work is strictly a proof of concept (POC). We are not requesting public distribution or App Store publication. Our immediate objective is to validate the technical feasibility of communicating with our USB devices from iPadOS before committing to Apple's platform for our enterprise solution. The lack of progress on these requests has effectively blocked our evaluation for three weeks, making it difficult to assess whether iPadOS is a viable platform for our intended use case. Apple Developer Team ID: R4PSRJ28G7 We are genuinely interested in adopting Apple's technology for our enterprise operations, but we need to establish technical feasibility before proceeding. I would appreciate any guidance that could help us move forward. Best regards,Alon Bar-Lev
2
0
484
4w
Pending DriverKit USB Entitlment
Hi, Any idea about the timeline for approval? It's been sitting at submit for 8+ weeks. Email support will not help. Claiming no ETA and it's a separate team that reviews that. I've requested a few as initially had some mistake on submission. Here's one of it: Request ID: R7P34F4338 Team ID: H2SLQH5546 If this forum post can help escalate, that would be appreciated.
2
0
1k
Oct ’26
App Settings silently fails to select Team / generate Personal Team certificate
Hello, trying to create a simple utility for personal use using Swift Playgrounds. I want to install the app locally on my iPad, I don’t want to have Swift Playgrounds open to run. Have not been able to resolve. See below: Environment: iPadOS Version: iPadOS 26.6.2 (23G90) Hardware: iPad Pro M4 Swift Playgrounds Version: 4.5+ Steps to Reproduce: Create a new App project (+ App button). Open App Settings > Team & Bundle Identifier. Ensure a free Apple ID is signed in. Tap the user's name under the "Team" list. Expected Result: The UI should register the selection, generate a local provisioning profile, and reveal the "Install on this iPad" button. If the user needs to accept a web agreement, an alert should guide them. Actual Result: Nothing happens. The row registers the touch visually, but the state remains "No Team Selected, Unknown Bundle Identifier". No error message is thrown, blocking local installation entirely. Thanks
3
1
378
Oct ’26
iOS 26.5 can’t verify Xcode development app — PPQ returns “OK
I can’t launch an Xcode development build on my iPhone. The iPhone says “Unable to Verify App — An internet connection is required to verify trust of the developer,” and Xcode says the Developer App Certificate is not trusted. The app builds and installs successfully. I’ve tried Wi-Fi and cellular, and Developer Mode is enabled. A browser request to ppq.apple.com returned “OK,” but verification still fails. Could this be a PPQ verification issue?
2
0
399
Oct ’26
New Capabilities Request Tab in Certificates, Identifiers & Profiles
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.
Replies
0
Boosts
0
Views
3.7k
Activity
Jun ’25
productbuild and Keychain Access concern
productbuild cmd: productbuild --component /Applications/Very\ Large\ Number\ Calculator.app /Applications --sign "3rd Party Mac Developer Installer: Alain_B " /Applications/Very\ Large\ Number\ Calculator.pkg Give this error: Cannot write product to "/Applications/Very Large Number Calculator.pkg". (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Alain_B ”.) But Keychain Access show "3rd Party Mac Developer Installer" is in Certificates: 3rd Party Mac Developer Application: 10 digits (64......J5) certificate login Nov 10, 2027 at 8:02:04 AM Alain_B private key login 3rd Party Mac Developer Installer: Alain_B (64......J5) certificate login Apr 19, 2027 at 8:32:51AM Apple Development: Alain_B (35......P5) certificate login Oct 19, 2027 at 9:29:59 AM Apple Development: Alain_B (Alain_B ) private key login Apple Distribution: Alain_B (64MZBY64J5) certificate login Oct 26, 2027 at 9:36:16 AM Alain_B private key login Apple Root CA certificate login Feb 9, 2035 at 4:40:36 PM Apple Worldwide Developer Relations Certification Authority certificate login Feb 19, 2030 at 7:00:00 PM Apple Worldwide Developer Relations Certification Authority certificate login Mar 18, 2036 at 8:00:00 PM Developer ID Certification Authority certificate login Feb 1, 2027 at 5:12:15 PM Developer ID Certification Authority certificate login Sep 16, 2031 at 8:00:00 PM What can I do ? Thank you.
Replies
3
Boosts
0
Views
217
Activity
1d
Can't build blocked by agreement
I recently switched from a personal to organization account, but the organization name didn't update in apple store. Also, i'm getting this error in codemagic "GET https://api.appstoreconnect.apple.com/v1/certificates?limit=100&sort=displayName&filter%5BcertificateType%5D=IOS_DISTRIBUTION returned 403: A required agreement is missing or has expired. - This request requires an in-effect agreement that has not been signed or has expired." And I already signed all the agreements, no warning boxes in apple store connect. Any suggestions?
Replies
1
Boosts
0
Views
170
Activity
1d
Developer ID Installer installation
I am trying to renew my Developer ID installer certificate in order to sign our custom pkgs for MDM deployment. I have sent a certificate signing request to the owner of our Apple Developer account and they issued a new Developer ID installer certificate using that CSR and sent me the resulting certificate. I am now having issues signing pkgs. I have the cert, the private key and the intermediate certificate but any pkg I sign is treated as not signed and gatekeeper does not like it. Is it not possible to Developer ID Installer certificates to non account holders? or am I doing something wrong? Any assistance would be great.
Replies
1
Boosts
0
Views
55
Activity
3d
0xe8008018 after account reinstatement — online authorization still returns REJECT_PROFILE for a valid certificate and profile
Our developer account was suspended and later reinstated. Membership is active again, but every development-signed build from our team still fails to install on a registered device: Failed to verify code signature of …/testIPA.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) MIInstallerErrorDomain error 13, LibMISErrorNumber = -402620392 We have gone as far as we can locally. The device log shows the rejection comes from Apple's server, so this can only be resolved by the Apple team that owns that service. I'm posting here to reach that team. What the device log shows The certificate and profile pass local validation. The install fails at the online authorization step, where the server rejects the profile: installd: [com.apple.mis:mis] Performing online authorization. online-auth-agent: (CFNetwork) … received response, status 200 online-auth-agent: [com.apple.mis:mis] The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,…,"validity":33} online-auth-agent: [com.apple.mis:mis] Permanently rejected profile: … installd: [com.apple.mis:mis] validation failed because of failing online authorization (-402620392) Troubleshooting stepsCertificate is valid (2026-11-03 → 2027-11-03); Apple OCSP returns good. codesign --verify --deep --strict passes. The Xcode-managed profile contains the certificate and the device; the device lists it as valid. Device clock is correct, Developer Mode is on, and the authorization request reaches Apple (HTTP 200). Revoked and recreated the development certificate, regenerated the profile: same result. New empty project with a never-used bundle ID: same result. Control: same Mac, same iPhone, same project signed with a different team's development certificate installs fine. The only variable is the team. Nothing on the Mac, the device, or in the project changes the outcome. Our working hypothesis When the account was suspended, the team was blocked in the service that authorizes signed apps at install time. When the account was reinstated, membership was restored but that block was not lifted. So the account looks normal everywhere we can see it, while the authorization server still treats the team as blocked. This is a hypothesis, not something we can confirm from our side. Two things point to it: Developer Support says the account is in good standing, yet the server answers REJECT_PROFILE for a valid certificate and profile. I found a thread here from a developer whose account was suspended and reinstated and who then could not sign. Developer Support could not resolve it, and it started working again by itself about a year later. That matches the wording of the suspension notice, which says developer services cannot be used for one year. It looks as if the signing restriction runs on its own timer and does not follow the account's reinstatement. What we have already tried with Apple I went through several rounds by email with Developer Support under case 103007200283 and supplied the screen recording and IPA they asked for. The case was passed to engineering. The answer was that the account status is normal, that they could not help further, and that I should look for help on the Forums. I have read many threads here about 0xe8008018. Most have very few replies, and none has a solution that applies when the certificate is valid and the rejection comes from the server. The core problem: which team owns this? I think the reason this has not been resolved is that the case never reached the right team. There are two candidates: The team that manages account status and permissions. They see an active membership, so they answer that the account is normal. The engineering team that runs the signing and install authorization service. That service is what rejects us, and only they can see or clear the state on that server. Our evidence points to the second. Developer Support has so far answered from the first. Environment Xcode 27.2 (27B52), macOS 27.0.1 iPhone 14 Pro, iOS 26.5.2 (23F84) Automatic signing, Apple Development certificate, team provisioning profile
Replies
0
Boosts
0
Views
287
Activity
1w
Bundle identifier after moving from a Personal Team to a paid Apple Developer Program enrollment
Application Group identifier unavailable after moving from a Personal Team to a paid Apple Developer Program enrollment Hi everyone, I built an app in Xcode using a Personal Team (free, signed in with my Apple ID) with the bundle identifier com.jcsnp.Minutely. My paid Apple Developer Program enrollment has been active since 5 Nov 2026, and I'm now trying to build and run the app under the new team. Xcode is blocking me on the App Group and the provisioning profile. Environment macOS 27, Xcode 27.2, iOS target 26.6 Paid enrollment: individual account, active since 5 Nov 2026 Errors Communication with Apple failed. An Application Group with Identifier 'group.com.jcsnp.Minutely' is not available. Please enter a different string. No profiles for 'com.jcsnp.Minutely' were found Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jcsnp.Minutely'. What I've tried Cleaning the build folder. The errors remain. Questions The App Group group.com.jcsnp.Minutely is reported as unavailable. Is it still registered to my old Personal Team, or to another account? If so, how do I release it or move it to the new team? Does the Personal Team's registration of the bundle ID need to be removed before com.jcsnp.Minutely can be registered under the paid team? Is there a recommended order for setting this up: registering the App ID and App Group in the developer portal first, then letting Xcode generate the profile? Thanks in advance for any guidance.
Replies
5
Boosts
0
Views
356
Activity
1w
Unexpected com.apple.macl extended attribute on macOS app bundle and provisioning profile
Hello, I'm investigating an unexpected com.apple.macl extended attribute while preparing a macOS application for Developer ID signing. I have observed the attribute in two places: On the root of an application bundle, where the recorded 72-byte attribute value changed during testing. On a Developer ID provisioning profile, where a 72-byte com.apple.macl value is present before signing. I also created a minimal Xcode reproducer that independently demonstrated the unexpected attribute behavior. I have not established which process creates or modifies the attribute, or whether its presence affects code-signing integrity. My questions are: Is this expected macOS behavior for app bundles and provisioning profiles? What is the recommended supported method to identify which system component creates or modifies this attribute? How should developers handle this situation when preparing and validating Developer ID signed applications? I would prefer to understand the cause rather than remove or suppress the attribute without knowing its security implications. Thank you.
Replies
2
Boosts
0
Views
192
Activity
1w
Apple TV as iPod in Apple Developer Center
I have a bizzare issue with my Apple TV that is shown as "iPod" in Apple developer portal. It's correctly visible in Xcode as Apple TV, but when I add it to developer portal it says "iPod". The problem is since it's there as an iPod I can't use it to my provisioning profile to build on the device Anyone has any idea how this can be solved? [Edited by Moderator]
Replies
5
Boosts
1
Views
1.8k
Activity
1w
Updating App - Validation Hell - 90286, 91130
Updating an App for the first time since 2011. Build, Analyze, Archive all successful. Automatically Manage Signing checked. Validation fails with 90286 - Invalid code signing entitlements, and 91130 - Invalid Provisioning Profile dozens of times after tweaks, clean builds, trying manual signing (thought I was done with that), etc. For 90286 it seems my Developer ID , e.g. 346JXXXXX (not Team ID, QZ99XXXXX) is the prefix for the bundle ID, com.company.app-name and that generates the error? For 91130 it's invalid "com.apple.application-identifier" which I assume is the same issue with a Developer ID instead of a Team ID. The original version of the app was QZ99XXXXX.com.company.app-name. I even changed the bundle identifier in Xcode to that, and got this: App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Yes, the original app name is being used for an app in my account. I was trying to update the app, checked all the boxes, added update text, but of course there was no build to upload. Would appreciate any help.
Replies
21
Boosts
0
Views
3.6k
Activity
1w
ITMS-90035: designated requirement uses NFD form of "İ" in team name; team name change pending
My first app cannot be uploaded: every IPA is rejected with ITMS-90035 "Invalid Signature". Setup: individual account, Team ID V7F74UFRBN, Xcode 27.0, macOS 26.6.2, Cloud Managed Apple Distribution certificate. My team name contains the Turkish letter "İ" (TELLİ). The certificate common name stores it as NFC (C4 B0), but the designated requirement written at signing time stores it as NFD (49 CC 87): certificate leaf[subject.CN] = 0x...54454c4c49cc87... so "codesign --verify --deep --strict" reports "does not satisfy its designated Requirement" for the app and every embedded framework. This looks like FB24633162 / thread 843700. I asked Developer Support to change my team name to the ASCII form "Mehmet Kaan TELLI" (case 103017162953) but have had no reply after several days, and the phone option shows as unavailable. Questions: Can DTS help escalate the team name change? Until then, is there a supported way to sign so the upload passes?
Replies
2
Boosts
0
Views
99
Activity
1w
Can I have my MAS and my "Indie" app share the same credentials for TCC (GateKeeper)?
I release my app both in the MAS and on my website. I use the same signing credentials, but necessarily different certs (Apple Development vs. Developer ID). When I run the MAS app and then run the other version, or vice versa, I need to re-authenticate the many privacy permissions each time (Finder AppleScript, Network browse, Full Disk Access), which is tedious and keeps causing trouble for other users because some of these require a tcc reset (which my app currently invokes manually, which I consider a hack, though). So, am I doing something wrong or is it really no possible to have both signed apps use the same identity with TCC?
Replies
3
Boosts
0
Views
166
Activity
2w
Paid team’s signing identity rejected on device (0xe8008018) since free-to-paid upgrade; same app installs under a free team
Since upgrading my free Apple Developer account to the paid Apple Developer Program (Individual) on September 21, 2026, every app signed with my paid team fails to install on my devices. TestFlight builds work. Error (Xcode Run, devicectl, Ad Hoc export): MIInstallerErrorDomain Code 13 / 0xe8008018 "The identity used to sign the executable is no longer valid." +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:] LibMISErrorNumber = -402620392 What I've established: A brand-new Hello World app with no capabilities fails the same way, so it is not my project, entitlements or widget. The same Hello World signed by a free Personal Team installs on the same iPad (after trusting the developer in Settings). So the device, OS, Xcode and Mac are fine. Fails on iPad Pro 13" M4 (iPadOS 27.0.1 and 27.2), iPhone Air (iOS 27.0.1) and iPhone 15 Pro Max (iOS 26.0.1), with Xcode 27.0, 27.1 and 27.2. Fails with Apple Development signing (Xcode Run) and with an Ad Hoc export signed with an Apple Distribution certificate. codesign verifies the app, the embedded profile contains the signing certificate and the device UDIDs, and the chain (WWDR G3 to Apple Root CA) is valid and not expired. Regenerated the Development and Distribution certificates, cleaned expired WWDR certificates from the keychain, removed profiles on the device, re-paired and toggled Developer Mode. No change. Only apps re-signed by Apple (TestFlight) install. This looks like stale signing state for the team on Apple's side after the free-to-paid conversion. I have an open request with Apple Developer Support (Case-ID 22506476) and Feedback Assistant report FB24912726, but have had no reply in two weeks. Has anyone seen 0xe8008018 on a team that was recently upgraded or converted, and is there anything I can do on my side beyond asking Apple to reset the team's signing identity?
Replies
1
Boosts
0
Views
749
Activity
2w
Which certificate for MAS submission? "Apple Distribution" vs "Mac App Distribution"
I am struggling with uploading my Mac-only app to TestFlight. I used to do this with Xcode 13.4.1 for a while without trouble, but now I have built the app with Xcode 27.1 and am getting issues such as ITMS-90885 and ITMS-90288 and I cannot figure out how to make it work. I have now at least realized that I seem to need to create a new provisioning profile because the one was using is missing some entitlement(s). To create a new profile, I need to create also a new certificate at https://developer.apple.com/account/resources/certificates/add But there's already my first hurdle: There are two types that allow upload the to MAS: "Apple Distribution" and "Mac App Distribution". Which one should I choose? I even googled for help but found nothing more than what the above website says. It's not clear what the difference is when I only want to submit to the MAS, and whether choosing the wrong one may already be part of the problem I'm having now with uploading my app. Can someone please explain in more detail if they're having exclusive behavior when using them to upload Mac apps to the MAS and TestFlight?
Replies
1
Boosts
0
Views
211
Activity
2w
Give Access to Team to Certs
Hello, New to Apple's system and structure for certs and signing. I've been working with their team to get access for developers on my team to access the correct Certs and sign what they need to so we can push our latest builds out, since this is needed by our CI/CD pipeline. How can I give access to members of my team so they can do the code saying they need to and access the certs they need to? the certs are for dmg and pkg installers on macos.
Replies
1
Boosts
0
Views
228
Activity
3w
Receiving message "Unable to find a team with the given Team ID to which you belong" when trying to access Certificates Identifiers & Profiles page
When attempting to access the (Certificates Identifiers & Profiles) page, I receive the message "Unable to find a team with the given Team ID to which you belong". Even while set as a developer or as an admin I still receive the same message above.
Replies
8
Boosts
0
Views
2.5k
Activity
3w
Apple Distribution signature fails its designated requirement — possible Unicode normalization issue
App Store Connect rejects my iOS Flutter app with error 90035: “Code failed to satisfy specified code requirement(s).” The error affects the main app executable, App.framework, and Flutter.framework. Environment: macOS 26.5.2 Xcode 26.6 Flutter 3.44.8 Individual Apple Developer Program membership The Release archive and App Store IPA build successfully. The exported IPA is signed with an Apple Distribution certificate and contains the correct TeamIdentifier. However, verification reports: Runner.app: valid on disk Runner.app: does not satisfy its designated Requirement The certificate Common Name contains a non-ASCII character: “Ç”. The generated designated requirement appears to represent this character using a decomposed Unicode form. I suspect a Unicode-normalization mismatch between the certificate Common Name and the embedded designated requirement. I am also unable to create a local Apple Distribution certificate: Xcode Manage Certificates reports: “The data couldn’t be read because it isn’t in the correct format.” The Apple Developer certificate portal reports “An unexpected error occurred” after I upload a valid CSR. Has anyone encountered this issue when an Apple Distribution certificate Common Name contains a non-ASCII character? Is there a supported way to regenerate the cloud-managed certificate or have Apple repair the team’s certificate state? I can provide sanitized codesign output if an Apple engineer needs additional diagnostic information.
Replies
17
Boosts
0
Views
2.2k
Activity
3w
After an A → B transfer with no update from B: does expiry of Team A's distribution certificate and provisioning profile affect sign-in or in-app purchases for the installed build?
Hello, We transferred an app from Team A to Team B. The app is live on the App Store, and every build currently in circulation was signed by Team A. Team B has not released any update — no App Store release and no TestFlight distribution — and the app may stay in that state for a considerable time. The distribution certificate and provisioning profile that Team A used to sign the build which is live right now will expire. We would like to confirm that this has no effect on sign-in and no effect on payments for the version that users already have installed from the App Store. Reasoning that applies to both The App Store re-signs the app as part of the distribution process, and the delivered build contains no embedded provisioning profile (TN3125), so neither Team A's certificate nor Team A's profile exists on the device. "Certificates overview" also states that an expired App Store distribution certificate does not affect existing App Store apps, and only prevents uploading new builds signed with it — which the transferor can no longer do in any case. Sign-in Login tokens live in the keychain under an access group whose name is prefixed with Team A's App ID Prefix. Our reading is that certificate and profile expiry has no bearing on keychain access at all, because the access check compares the group string in the binary's entitlements against the item's kSecAttrAccessGroup, and the signing certificate is not an input to that comparison. Is that correct? Payments Our reading is that payments are unaffected on both sides: StoreKit transactions — purchases, renewals, refunds — are handled by Apple's servers and do not depend on the app's signing certificate or provisioning profile; our server-side receipt validation relies on the app-specific shared secret, a 32-character hexadecimal string with no relationship to any certificate, so receipt validation keeps working. Is that correct, or does something break here? One consequence we would like confirmed If Team A ever needed to publish another build under its own account, we assume it would first have to issue a new, valid certificate and provisioning profile — that is, expiry does not affect the installed app, but it does affect Team A's ability to publish anything further. Is that right? Thanks!
Replies
1
Boosts
0
Views
305
Activity
3w
Internal enterprise iPadOS application - USB CDC entitlement
Dear Apple Developer Support Team, I am reaching out for assistance with two pending DriverKit entitlement requests. This is my first experience developing an application within Apple's ecosystem, and I recognize that my use case is somewhat unconventional. I may not have reached the appropriate support channel, so I would appreciate your guidance or assistance in directing this request to the correct team. We are currently evaluating the feasibility of adopting iPads for an internal enterprise application that communicates with our proprietary USB devices. These devices use the standard USB Communications Device Class (CDC), exposing a virtual serial port (UART). They work reliably on Windows, Linux, and macOS. To my surprise, I discovered that iPadOS does not provide general-purpose access to standard USB CDC serial devices. Based on my research, the recommended approach appears to be implementing a custom driver using DriverKit. We also use macOS as our primary development and debugging environment, so we would like to maintain a consistent DriverKit-based implementation across both platforms in macOS only for development. On September 30, 2026, I submitted the following entitlement requests: 1. Request GW966578ZB — DriverKit UserClient Access Requested entitlement: com.apple.developer.driverkit.userclient-access 2. Request 3HN2GMDFN5 — DriverKit / USB Transport Distribution Authorization Requested entitlements: com.apple.developer.driverkit com.apple.developer.driverkit.transport.usb Unfortunately, I have not received any response or status update on either request in the three weeks since submission. At this stage, our work is strictly a proof of concept (POC). We are not requesting public distribution or App Store publication. Our immediate objective is to validate the technical feasibility of communicating with our USB devices from iPadOS before committing to Apple's platform for our enterprise solution. The lack of progress on these requests has effectively blocked our evaluation for three weeks, making it difficult to assess whether iPadOS is a viable platform for our intended use case. Apple Developer Team ID: R4PSRJ28G7 We are genuinely interested in adopting Apple's technology for our enterprise operations, but we need to establish technical feasibility before proceeding. I would appreciate any guidance that could help us move forward. Best regards,Alon Bar-Lev
Replies
2
Boosts
0
Views
484
Activity
4w
Pending DriverKit USB Entitlment
Hi, Any idea about the timeline for approval? It's been sitting at submit for 8+ weeks. Email support will not help. Claiming no ETA and it's a separate team that reviews that. I've requested a few as initially had some mistake on submission. Here's one of it: Request ID: R7P34F4338 Team ID: H2SLQH5546 If this forum post can help escalate, that would be appreciated.
Replies
2
Boosts
0
Views
1k
Activity
Oct ’26
App Settings silently fails to select Team / generate Personal Team certificate
Hello, trying to create a simple utility for personal use using Swift Playgrounds. I want to install the app locally on my iPad, I don’t want to have Swift Playgrounds open to run. Have not been able to resolve. See below: Environment: iPadOS Version: iPadOS 26.6.2 (23G90) Hardware: iPad Pro M4 Swift Playgrounds Version: 4.5+ Steps to Reproduce: Create a new App project (+ App button). Open App Settings > Team & Bundle Identifier. Ensure a free Apple ID is signed in. Tap the user's name under the "Team" list. Expected Result: The UI should register the selection, generate a local provisioning profile, and reveal the "Install on this iPad" button. If the user needs to accept a web agreement, an alert should guide them. Actual Result: Nothing happens. The row registers the touch visually, but the state remains "No Team Selected, Unknown Bundle Identifier". No error message is thrown, blocking local installation entirely. Thanks
Replies
3
Boosts
1
Views
378
Activity
Oct ’26
iOS 26.5 can’t verify Xcode development app — PPQ returns “OK
I can’t launch an Xcode development build on my iPhone. The iPhone says “Unable to Verify App — An internet connection is required to verify trust of the developer,” and Xcode says the Developer App Certificate is not trusted. The app builds and installs successfully. I’ve tried Wi-Fi and cellular, and Developer Mode is enabled. A browser request to ppq.apple.com returned “OK,” but verification still fails. Could this be a PPQ verification issue?
Replies
2
Boosts
0
Views
399
Activity
Oct ’26