Demystify code signing and its importance in app development. Get help troubleshooting code signing issues and ensure your app is properly signed for distribution.

All subtopics
Posts under Code Signing topic

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
Code Signing Resources
General: Forums topic: Code Signing Forums subtopics: Code Signing > General, Code Signing > Certificates, Identifiers & Profiles, Code Signing > Notarization, Code Signing > Entitlements Forums tags: Code Signing, Signing Certificates, Provisioning Profiles, Entitlements Developer Account Help — This document is good in general but, in particular, the Reference section is chock-full of useful information, including the names and purposes of all certificate types issued by Apple Developer web site, tables of which capabilities are supported by which distribution models on iOS and macOS, and information on how to use managed capabilities. Developer > Support > Certificates covers some important policy issues Bundle Resources > Entitlements documentation TN3125 Inside Code Signing: Provisioning Profiles — This includes links to the other technotes in the Inside Code Signing series. WWDC 2021 Session 10204 Distribute apps in Xcode with cloud signing Certificate Signing Requests Explained forums post --deep Considered Harmful forums post Don’t Run App Store Distribution-Signed Code forums post Resolving errSecInternalComponent errors during code signing forums post Finding a Capability’s Distribution Restrictions forums post Signing code with a hardware-based code-signing identity forums post New Capabilities Request Tab in Certificates, Identifiers & Profiles forums post Isolating Code Signing Problems from Build Problems forums post Investigating Third-Party IDE Code-Signing Problems forums post Determining if an entitlement is real forums post Code Signing Identifiers Explained forums post Mac code signing: Forums tag: Developer ID Creating distribution-signed code for macOS documentation Packaging Mac software for distribution documentation Placing Content in a Bundle documentation Embedding nonstandard code structures in a bundle documentation Embedding a command-line tool in a sandboxed app documentation Signing a daemon with a restricted entitlement documentation Defining launch environment and library constraints documentation WWDC 2023 Session 10266 Protect your Mac app with environment constraints TN2206 macOS Code Signing In Depth archived technote — This doc has mostly been replaced by the other resources linked to here but it still contains a few unique tidbits and it’s a great historical reference. Manual Code Signing Example forums post The Care and Feeding of Developer ID forums post TestFlight, Provisioning Profiles, and the Mac App Store forums post For problems with notarisation, see Notarisation Resources. For problems with the trusted execution system, including Gatekeeper, see Trusted Execution Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
0
0
43k
Jan ’26
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?
0
0
94
6h
Can't notarize after agreements are signed
Hi all, For the second time, when our account owner goes into the developer portal and signs any pending agreements, notarization stops working. But stays not working. This happened a few months ago, and it's now day 4 of it happening again. I've filed a support case and followed up 2x now, but it's crickets. We have a real application thaht's used by many people and can not release it. It's myself and other on a small team's livelihood. It's materially affecting us as a company, but I have no recourse to do... anything but pray at this point. Is this typical of anyone else's experience?
0
0
91
14h
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.
2
0
138
18h
Clarification on Installation of Existing Notarized Installer Packages After February 1, 2027
Hello Apple Developer Support, We are seeking clarification regarding the impact of the upcoming certificate changes taking effect on February 1, 2027. Our organization has previously distributed macOS installer packages (.pkg) that were: • Signed using a Developer ID Installer certificate that chains to the Developer ID Certification Authority intermediate certificate expiring on February 1, 2027. • Successfully notarized by Apple. • Signed with a secure timestamp. We are specifically seeking clarification on the impact of the Developer ID Certification Authority intermediate CA expiration on packages that were signed, securely timestamped, and successfully notarized prior to the expiration date. We would like to understand how these existing packages will be treated after February 1, 2027. Questions Will installer packages (.pkg) that were already signed, timestamped, and notarized before February 1, 2027 continue to install successfully after that date? Does notarization combined with a secure timestamp allow these previously distributed packages to remain trusted and installable after the certificate changes take effect? Are software vendors required to re-sign and re-notarize installer packages that have already been distributed if they were signed using certificates affected by this change? If re-signing is required, does this apply to: • Only new packages created after February 1, 2027, or • Existing packages that were previously notarized and distributed? Are there any recommended validation steps to determine whether an existing notarized package will continue to install successfully after February 1, 2027? Business Impact We are evaluating whether previously released installer packages signed with Developer ID Installer certificates that chain to the expiring Developer ID Certification Authority intermediate CA will remain deployable for customers after February 1, 2027, and whether any re-signing or re-notarization effort is required for our existing catalog of notarized installers. Without clarification, we cannot determine whether archived installers will continue to function as expected or whether remediation work is required to preserve the installability of previously released software versions. Thank you for your guidance. We would appreciate any relevant documentation or recommendations regarding best practices for existing notarized installer packages.
4
1
946
1d
spctl reports internal error for an ad-hoc signed macOS command-line tool
On an Apple Silicon Mac running macOS 27.0.1 (26A434), I am assessing the arm64 command-line tool age v1.3.2. The downloaded file retains its quarantine attribute. The command spctl --assess --type execute --verbose=2 returned exit code 1 with: “internal error in Code Signing subsystem”. A later codesign --verify --strict --verbose=4 check returned exit code 0. The file hash and recorded attributes did not change around the strict verification. The tool is ad-hoc/linker-signed, with no TeamIdentifier. I have not executed the tool or removed quarantine. The exact environment and independent raw output file for the first spctl assessment were not recorded; the error above is a transcription of the observed output. What is the supported way to assess a standalone command-line tool in this situation? How can I distinguish a policy rejection from an assessment failure, and what further diagnostics would you recommend without running the tool or reducing system security?
Topic: Code Signing SubTopic: General
4
0
255
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
41
1d
First notarization stuck In Progress for 68+ hours (Team ID: QDUMUTR8V4)
Hello, I am a new Apple Developer Program member (Team ID: QDUMUTR8V4) submitting my macOS Electron application for notarization. My first submission (79b105e6-951f-4be2-8e89-4dc2a1c9bc7b) returned Invalid quickly due to an unsigned nested .tar.gz archive inside node_modules. I immediately fixed the issue, removed the unsigned archive, re-signed the app, and submitted a second build: Team ID: QDUMUTR8V4 Submission ID: 1ec8ce36-b7d3-4fe9-bb25-fdb5f5de3b06 Submitted At: 2026-11-14T05:16:27.933Z Current Status: In Progress (stuck for over 68 hours) Could someone from the Apple team please check if this submission is stuck in the backend queue? Thank you very much for your help.
1
0
183
1d
First notarization submissions from a new team stuck "In Progress" for 4 days (Team ID PSM2TYR5TX)
Hi, We are a newly enrolled individual team (Team ID PSM2TYR5TX). None of our valid notarization submissions has ever finished: all four have been "In Progress" since upload, and notarytool log says the log is not yet available. Submissions, oldest first (all still In Progress as of 2026-11-16 08:00 UTC): e73bcb6e-dc26-46df-801d-0ae26fa6a037 (submitted 2026-11-12 08:18 UTC, about 4 days ago) 07a4e338-575d-4936-a9a7-fd26059cbbb2 (2026-11-13 09:02 UTC) 7d67283c-8d4e-447a-81d4-2ce0a478747a (2026-11-13 10:16 UTC) fd8c30bf-853e-40d3-8d77-449d480e1853 (2026-11-13 18:04 UTC) One other submission, ade47a2f-5f6b-4d6a-a9f7-d7002eb22ea0, came back Invalid quickly because that build was signed without a secure timestamp (the app and its nested Sparkle binaries). We fixed that, so uploads and credentials work. The app is a small Mac utility written in Swift that embeds the Sparkle framework. It is signed with our Developer ID Application certificate, with hardened runtime and a secure timestamp and no get-task-allow entitlement; codesign --verify --deep --strict passes. Each submission is a signed DMG uploaded with xcrun notarytool submit (notarytool 1.1.4, Xcode 27.2). We have read the note about in-depth analysis and are happy to wait, but the oldest submission is now past four days and we hope to ship this week. Could someone check whether these are still being processed, or whether something on our team's side needs attention? Thank you!
2
0
38
1d
BlockStorageDeviceDriverKit grant confirmed by support but shows "No Requests" in the portal. How to resolve?
Hello! I am hoping a DTS engineer or someone who knows the Capability Requests portal can help, because I am stuck between a written support confirmation and what the portal actually shows. Background. We are building a native macOS iSCSI initiator for SOHO and home NAS use, developed over close to two years. A userspace daemon runs the iSCSI protocol and a DriverKit system extension presents the remote LUN as a block device. The code is essentially complete. Only the DriverKit extension cannot be signed, loaded and validated without the entitlement. We submitted request 32PC8MGU57 for two entitlements: com.apple.developer.driverkit.family.block-storage-device for the extension com.aviontex.iscsi.AviontexISCSI.AviontexInitiator com.apple.developer.driverkit.userclient-access for the app com.aviontex.iscsi.AviontexISCSI, scoped to the extension bundle id The problem. On June 25 Developer Support confirmed in writing that both entitlements were granted. The portal does not match that: Block Storage Device: No Requests: on both App IDs UserClient Access: Assigned: on the app SCSI Controller: Submitted: on the app So the one entitlement we actually need, Block Storage Device, shows as never requested, even though request 32PC8MGU57 covered it and support confirmed the grant. The case was escalated to the senior team on July 2 (case 102922935570). Follow-up emails since then have not received a response. Why Block Storage Device specifically Our initiator has no PCI or Thunderbolt bus and no DMA path, so SCSIControllerDriverKit does not fit. This is confirmed by DTS in thread 776020, where Kevin Elliott explains that SCSIControllerDriverKit passes data through fBufferIOVMAddr as a physical address with no mechanism to convert it into a VM address the dext can access. He also notes it cannot be used with any bus other than PCI or Thunderbolt. Block Storage Device is therefore the family we need. My questions: Am I reading the portal correctly: Block Storage Device not requested, UserClient Access assigned, SCSI Controller submitted? From here, what is the correct way to get Block Storage Device onto these two App IDs, with both the Development and the Distribution grant, since our public beta depends on Distribution? Should I submit a new request through the Capability Requests tab or does the escalated case handle it? Is there any way to get visibility on the escalated case, since email follow-ups are not being answered? A full technical justification is prepared and we are happy to share the source code. Any guidance would be appreciated. Thank you.
74
4
18k
1d
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
268
5d
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
343
5d
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
184
6d
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.7k
1w
is com.apple.developer.usb.host-controller-interface managed?
I'm posting this here after reading Quinn's post here: https://developer.apple.com/forums/thread/799000 The above entitlement is mentioned in IOUSBHostControllerInterface.h. It isn't an entitlement one can add using the + button on the Capabilities panel in Xcode. If I try to add it by hand, Xcode complains that it isn't in my profile. Is this a managed entitlement? We'd like to create a local USB "device" to represent a real device reachable over a network.
22
1
4.3k
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
iOS App Store upload fails with "Invalid Signature" on main executable (Godot 4.7.2, Xcode 27.1)
Hi everyone, I'm trying to publish my first iOS app (a game built with the Godot engine), but every upload to App Store Connect fails with this error: "Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path "sevenatseven.app/sevenatseven" is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate." Setup: Xcode 27.1 (27A9275), macOS 27.0.1 The Xcode project is exported from Godot 4.7.2 (stable) Automatic signing with my paid team; no signing errors shown in Xcode Release configuration, Code Sign Identity: Apple Development (Xcode re-signs for distribution on upload) My account has a valid Distribution Managed certificate What I tried: Archive with "Any iOS Device (arm64)", then Distribute App > App Store Connect > Upload Clean Build Folder, fresh project export, new archive The archive always succeeds and the app runs fine on a real iPhone, but the upload is rejected every time with the same error on the main executable. What can cause this error on the main executable when the archive and signing look correct in Xcode? Is there a way to see which code requirement is failing, or a codesign command I should run on the archive to check it? Thanks!
3
0
446
1w
ScreenCaptureKit on iOS 27: How can developers provision com.apple.developer.screen-recording?
I'm testing Apple's official "Capturing screen content on iOS" sample architecture using Xcode 27.2 and a physical iPhone running iOS 27.2. My application builds, signs and launches successfully using a Personal Team without the screen-recording entitlement. However, when I add the entitlement required by Apple's sample, automatic provisioning fails with: "Entitlement com.apple.developer.screen-recording not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file." The generated provisioning profile does not contain the entitlement. Could Apple clarify: Is this entitlement available to Personal Teams for development? Does it require Apple Developer Program membership or separate capability approval? What is the supported procedure for obtaining a provisioning profile that includes it? Is there a known issue with entitlement availability or the iOS 27 sample? Our intended use is explicitly authorised full-display capture using the system picker, with on-device processing and no attempt to bypass user consent. I would appreciate guidance on the correct supported provisioning procedure.
1
0
108
1w
Supported independent whole-file reference for df and codesign in macOS build 26A434
We are looking for a supported way to establish an independent byte-level reference for two Apple-supplied executables: /bin/df and /usr/bin/codesign. This is a provenance inquiry, not an allegation of tampering or a known Apple defect. The Apple Developer OS download catalog lists macOS 27.0.1, build 26A434, released September 28, 2026, and links to this Apple silicon restore image: https://updates.cdn-apple.com/2026FallFCS/59241290-5d51-4ca8-9df4-31624b9a4eac/UniversalMac_27.0.1_26A434_Restore.ipsw We have saved whole-file lengths and SHA-256 observations from earlier local reads. Different observations had different whole-file digests. A separate historical OS version record identifies 26A434, but it is not contemporaneous with every file observation, so we use this build only as a candidate reference, not as an established build for every sample. The historical device context is Apple silicon / Mac18,5. No new machine inspection is requested or implied here. Questions: Does Apple publish, or have a supported way to obtain, authenticated whole-file byte lengths and SHA-256 values for these exact two paths in the 26A434 Apple silicon distribution? Please specify the applicable architecture and file representation. If not, is there a supported read-only procedure to authenticate the exact restore asset and extract these two complete files as a comparable reference, without installing or restoring macOS? What checks establish the build, model applicability and integrity of the extracted content? Are there documented transformations during installation, personalization or architecture selection that could make a valid installed file differ byte-for-byte from the corresponding restore-image file? If so, what comparison is supported without silently changing a whole-file-equality requirement? We understand from TN2206 and TN3126 that architectures in universal binaries are signed independently and that removing an architecture can preserve signature validity. A valid signature or CDHash is therefore not being treated as a substitute for our whole-file SHA-256 observations. Likewise, a checksum for the complete IPSW would not itself be the checksum of either executable. The intended comparison must not rely solely on the previously observed local codesign executable whose own whole-file binding changed. We are seeking a supported independent reference or verification method; we are not asking to disable Gatekeeper, SIP, authenticated-root protection, modify trust settings, re-sign system executables, or infer the cause of the historical differences. No system image has been downloaded or mounted for this inquiry. No passwords, account identifiers, keychain contents, private keys, logs, or attachments are included. References: https://developer.apple.com/download/os/ https://developer.apple.com/library/archive/technotes/tn2206/ https://developer.apple.com/documentation/technotes/tn3126-inside-code-signing-hashes https://support.apple.com/guide/security/signed-system-volume-security-secd698747c9/web
Topic: Code Signing SubTopic: General
1
0
277
1w
Developer ID notarization stuck "In Progress" for 1h+ — previous submissions took minutes
Two notarization submissions for a Developer ID–signed macOS app have been "In Progress" for over an hour. Earlier submissions from this same team, credentials and workflow were all Accepted within minutes. Submissions Created (UTC)IDFileStatus2026-11-05 15:54:4802956de4-0ec7-4009-8f8e-1635f93a10d1ProxyPal.zipIn Progress2026-11-05 16:37:25e38d47a1-6709-4008-9682-18f9b96af217ProxyPal.zipIn ProgressThe second one is a resubmission of the identical zip, sent after the first had been stuck for about 40 minutes. What I've checked xcrun notarytool info <id> returns In Progress. xcrun notarytool log <id> returns "Submission log is not yet available". Authentication and upload work, and notarytool history lists both submissions. codesign --verify --deep --strict passes on the app. Every executable in the bundle has the hardened runtime and a secure timestamp. The zip is made with ditto -c -k --keepParent, the same command as the earlier accepted releases. The bundle contents are essentially unchanged since the last accepted release. The differences are a small generated static HTML help folder and version-number changes. Environment Submitted with xcrun notarytool submit ... --keychain-profile ... --wait from a script. macOS 26 (Darwin 25.6), Xcode toolchain notarytool. Zip is 89 MB, 193 files, and includes two nested .apk files that were also in earlier accepted releases. Questions Are these two submissions held for additional analysis, or stuck in the queue? Is there anything on my side I should change?
4
0
493
1w
Notarization Failure Linked to /Library/Developer
I've been unable to notarize an installer for an app (https://fxfactory.com/info/fxcore/) ever since adding a plug-in SDK that I was hoping to distribute as follows: /Library/Developer/SDKs/FxCore.sdk /Library/Developer/Xcode/Templates/FxCore/FxCore.xctemplate This creates the smoothest possible UX for someone who starts using the SDK, mimicking official SDKs. This is causing notarization failure, without a useful explanation, but a search suggests that Apple is preventing installers from touching the /Library/Developer directory as this might otherwise compromise the developer toolchain. What is the correct strategy for third-party SDKs? I'm assuming that ADDITIONAL_SDKS doesnt' care if the SDK isn't located at that specific location, but is there any other place where I can put the xctemplate and have it appear when creating a new project in Xcode? (I haven't tried using a post-install script to copy files after the fact but I’d assume that would fail... otherwise what would be the point of this extra safety check.) Thank you!
1
0
357
1w
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
Code Signing Resources
General: Forums topic: Code Signing Forums subtopics: Code Signing > General, Code Signing > Certificates, Identifiers & Profiles, Code Signing > Notarization, Code Signing > Entitlements Forums tags: Code Signing, Signing Certificates, Provisioning Profiles, Entitlements Developer Account Help — This document is good in general but, in particular, the Reference section is chock-full of useful information, including the names and purposes of all certificate types issued by Apple Developer web site, tables of which capabilities are supported by which distribution models on iOS and macOS, and information on how to use managed capabilities. Developer > Support > Certificates covers some important policy issues Bundle Resources > Entitlements documentation TN3125 Inside Code Signing: Provisioning Profiles — This includes links to the other technotes in the Inside Code Signing series. WWDC 2021 Session 10204 Distribute apps in Xcode with cloud signing Certificate Signing Requests Explained forums post --deep Considered Harmful forums post Don’t Run App Store Distribution-Signed Code forums post Resolving errSecInternalComponent errors during code signing forums post Finding a Capability’s Distribution Restrictions forums post Signing code with a hardware-based code-signing identity forums post New Capabilities Request Tab in Certificates, Identifiers & Profiles forums post Isolating Code Signing Problems from Build Problems forums post Investigating Third-Party IDE Code-Signing Problems forums post Determining if an entitlement is real forums post Code Signing Identifiers Explained forums post Mac code signing: Forums tag: Developer ID Creating distribution-signed code for macOS documentation Packaging Mac software for distribution documentation Placing Content in a Bundle documentation Embedding nonstandard code structures in a bundle documentation Embedding a command-line tool in a sandboxed app documentation Signing a daemon with a restricted entitlement documentation Defining launch environment and library constraints documentation WWDC 2023 Session 10266 Protect your Mac app with environment constraints TN2206 macOS Code Signing In Depth archived technote — This doc has mostly been replaced by the other resources linked to here but it still contains a few unique tidbits and it’s a great historical reference. Manual Code Signing Example forums post The Care and Feeding of Developer ID forums post TestFlight, Provisioning Profiles, and the Mac App Store forums post For problems with notarisation, see Notarisation Resources. For problems with the trusted execution system, including Gatekeeper, see Trusted Execution Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
Replies
0
Boosts
0
Views
43k
Activity
Jan ’26
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
0
Boosts
0
Views
94
Activity
6h
Can't notarize after agreements are signed
Hi all, For the second time, when our account owner goes into the developer portal and signs any pending agreements, notarization stops working. But stays not working. This happened a few months ago, and it's now day 4 of it happening again. I've filed a support case and followed up 2x now, but it's crickets. We have a real application thaht's used by many people and can not release it. It's myself and other on a small team's livelihood. It's materially affecting us as a company, but I have no recourse to do... anything but pray at this point. Is this typical of anyone else's experience?
Replies
0
Boosts
0
Views
91
Activity
14h
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
2
Boosts
0
Views
138
Activity
18h
Clarification on Installation of Existing Notarized Installer Packages After February 1, 2027
Hello Apple Developer Support, We are seeking clarification regarding the impact of the upcoming certificate changes taking effect on February 1, 2027. Our organization has previously distributed macOS installer packages (.pkg) that were: • Signed using a Developer ID Installer certificate that chains to the Developer ID Certification Authority intermediate certificate expiring on February 1, 2027. • Successfully notarized by Apple. • Signed with a secure timestamp. We are specifically seeking clarification on the impact of the Developer ID Certification Authority intermediate CA expiration on packages that were signed, securely timestamped, and successfully notarized prior to the expiration date. We would like to understand how these existing packages will be treated after February 1, 2027. Questions Will installer packages (.pkg) that were already signed, timestamped, and notarized before February 1, 2027 continue to install successfully after that date? Does notarization combined with a secure timestamp allow these previously distributed packages to remain trusted and installable after the certificate changes take effect? Are software vendors required to re-sign and re-notarize installer packages that have already been distributed if they were signed using certificates affected by this change? If re-signing is required, does this apply to: • Only new packages created after February 1, 2027, or • Existing packages that were previously notarized and distributed? Are there any recommended validation steps to determine whether an existing notarized package will continue to install successfully after February 1, 2027? Business Impact We are evaluating whether previously released installer packages signed with Developer ID Installer certificates that chain to the expiring Developer ID Certification Authority intermediate CA will remain deployable for customers after February 1, 2027, and whether any re-signing or re-notarization effort is required for our existing catalog of notarized installers. Without clarification, we cannot determine whether archived installers will continue to function as expected or whether remediation work is required to preserve the installability of previously released software versions. Thank you for your guidance. We would appreciate any relevant documentation or recommendations regarding best practices for existing notarized installer packages.
Replies
4
Boosts
1
Views
946
Activity
1d
spctl reports internal error for an ad-hoc signed macOS command-line tool
On an Apple Silicon Mac running macOS 27.0.1 (26A434), I am assessing the arm64 command-line tool age v1.3.2. The downloaded file retains its quarantine attribute. The command spctl --assess --type execute --verbose=2 returned exit code 1 with: “internal error in Code Signing subsystem”. A later codesign --verify --strict --verbose=4 check returned exit code 0. The file hash and recorded attributes did not change around the strict verification. The tool is ad-hoc/linker-signed, with no TeamIdentifier. I have not executed the tool or removed quarantine. The exact environment and independent raw output file for the first spctl assessment were not recorded; the error above is a transcription of the observed output. What is the supported way to assess a standalone command-line tool in this situation? How can I distinguish a policy rejection from an assessment failure, and what further diagnostics would you recommend without running the tool or reducing system security?
Topic: Code Signing SubTopic: General
Replies
4
Boosts
0
Views
255
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
41
Activity
1d
First notarization stuck In Progress for 68+ hours (Team ID: QDUMUTR8V4)
Hello, I am a new Apple Developer Program member (Team ID: QDUMUTR8V4) submitting my macOS Electron application for notarization. My first submission (79b105e6-951f-4be2-8e89-4dc2a1c9bc7b) returned Invalid quickly due to an unsigned nested .tar.gz archive inside node_modules. I immediately fixed the issue, removed the unsigned archive, re-signed the app, and submitted a second build: Team ID: QDUMUTR8V4 Submission ID: 1ec8ce36-b7d3-4fe9-bb25-fdb5f5de3b06 Submitted At: 2026-11-14T05:16:27.933Z Current Status: In Progress (stuck for over 68 hours) Could someone from the Apple team please check if this submission is stuck in the backend queue? Thank you very much for your help.
Replies
1
Boosts
0
Views
183
Activity
1d
First notarization submissions from a new team stuck "In Progress" for 4 days (Team ID PSM2TYR5TX)
Hi, We are a newly enrolled individual team (Team ID PSM2TYR5TX). None of our valid notarization submissions has ever finished: all four have been "In Progress" since upload, and notarytool log says the log is not yet available. Submissions, oldest first (all still In Progress as of 2026-11-16 08:00 UTC): e73bcb6e-dc26-46df-801d-0ae26fa6a037 (submitted 2026-11-12 08:18 UTC, about 4 days ago) 07a4e338-575d-4936-a9a7-fd26059cbbb2 (2026-11-13 09:02 UTC) 7d67283c-8d4e-447a-81d4-2ce0a478747a (2026-11-13 10:16 UTC) fd8c30bf-853e-40d3-8d77-449d480e1853 (2026-11-13 18:04 UTC) One other submission, ade47a2f-5f6b-4d6a-a9f7-d7002eb22ea0, came back Invalid quickly because that build was signed without a secure timestamp (the app and its nested Sparkle binaries). We fixed that, so uploads and credentials work. The app is a small Mac utility written in Swift that embeds the Sparkle framework. It is signed with our Developer ID Application certificate, with hardened runtime and a secure timestamp and no get-task-allow entitlement; codesign --verify --deep --strict passes. Each submission is a signed DMG uploaded with xcrun notarytool submit (notarytool 1.1.4, Xcode 27.2). We have read the note about in-depth analysis and are happy to wait, but the oldest submission is now past four days and we hope to ship this week. Could someone check whether these are still being processed, or whether something on our team's side needs attention? Thank you!
Replies
2
Boosts
0
Views
38
Activity
1d
BlockStorageDeviceDriverKit grant confirmed by support but shows "No Requests" in the portal. How to resolve?
Hello! I am hoping a DTS engineer or someone who knows the Capability Requests portal can help, because I am stuck between a written support confirmation and what the portal actually shows. Background. We are building a native macOS iSCSI initiator for SOHO and home NAS use, developed over close to two years. A userspace daemon runs the iSCSI protocol and a DriverKit system extension presents the remote LUN as a block device. The code is essentially complete. Only the DriverKit extension cannot be signed, loaded and validated without the entitlement. We submitted request 32PC8MGU57 for two entitlements: com.apple.developer.driverkit.family.block-storage-device for the extension com.aviontex.iscsi.AviontexISCSI.AviontexInitiator com.apple.developer.driverkit.userclient-access for the app com.aviontex.iscsi.AviontexISCSI, scoped to the extension bundle id The problem. On June 25 Developer Support confirmed in writing that both entitlements were granted. The portal does not match that: Block Storage Device: No Requests: on both App IDs UserClient Access: Assigned: on the app SCSI Controller: Submitted: on the app So the one entitlement we actually need, Block Storage Device, shows as never requested, even though request 32PC8MGU57 covered it and support confirmed the grant. The case was escalated to the senior team on July 2 (case 102922935570). Follow-up emails since then have not received a response. Why Block Storage Device specifically Our initiator has no PCI or Thunderbolt bus and no DMA path, so SCSIControllerDriverKit does not fit. This is confirmed by DTS in thread 776020, where Kevin Elliott explains that SCSIControllerDriverKit passes data through fBufferIOVMAddr as a physical address with no mechanism to convert it into a VM address the dext can access. He also notes it cannot be used with any bus other than PCI or Thunderbolt. Block Storage Device is therefore the family we need. My questions: Am I reading the portal correctly: Block Storage Device not requested, UserClient Access assigned, SCSI Controller submitted? From here, what is the correct way to get Block Storage Device onto these two App IDs, with both the Development and the Distribution grant, since our public beta depends on Distribution? Should I submit a new request through the Capability Requests tab or does the escalated case handle it? Is there any way to get visibility on the escalated case, since email follow-ups are not being answered? A full technical justification is prepared and we are happy to share the source code. Any guidance would be appreciated. Thank you.
Replies
74
Boosts
4
Views
18k
Activity
1d
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
268
Activity
5d
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
343
Activity
5d
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
184
Activity
6d
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.7k
Activity
1w
is com.apple.developer.usb.host-controller-interface managed?
I'm posting this here after reading Quinn's post here: https://developer.apple.com/forums/thread/799000 The above entitlement is mentioned in IOUSBHostControllerInterface.h. It isn't an entitlement one can add using the + button on the Capabilities panel in Xcode. If I try to add it by hand, Xcode complains that it isn't in my profile. Is this a managed entitlement? We'd like to create a local USB "device" to represent a real device reachable over a network.
Replies
22
Boosts
1
Views
4.3k
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
iOS App Store upload fails with "Invalid Signature" on main executable (Godot 4.7.2, Xcode 27.1)
Hi everyone, I'm trying to publish my first iOS app (a game built with the Godot engine), but every upload to App Store Connect fails with this error: "Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path "sevenatseven.app/sevenatseven" is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate." Setup: Xcode 27.1 (27A9275), macOS 27.0.1 The Xcode project is exported from Godot 4.7.2 (stable) Automatic signing with my paid team; no signing errors shown in Xcode Release configuration, Code Sign Identity: Apple Development (Xcode re-signs for distribution on upload) My account has a valid Distribution Managed certificate What I tried: Archive with "Any iOS Device (arm64)", then Distribute App > App Store Connect > Upload Clean Build Folder, fresh project export, new archive The archive always succeeds and the app runs fine on a real iPhone, but the upload is rejected every time with the same error on the main executable. What can cause this error on the main executable when the archive and signing look correct in Xcode? Is there a way to see which code requirement is failing, or a codesign command I should run on the archive to check it? Thanks!
Replies
3
Boosts
0
Views
446
Activity
1w
ScreenCaptureKit on iOS 27: How can developers provision com.apple.developer.screen-recording?
I'm testing Apple's official "Capturing screen content on iOS" sample architecture using Xcode 27.2 and a physical iPhone running iOS 27.2. My application builds, signs and launches successfully using a Personal Team without the screen-recording entitlement. However, when I add the entitlement required by Apple's sample, automatic provisioning fails with: "Entitlement com.apple.developer.screen-recording not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file." The generated provisioning profile does not contain the entitlement. Could Apple clarify: Is this entitlement available to Personal Teams for development? Does it require Apple Developer Program membership or separate capability approval? What is the supported procedure for obtaining a provisioning profile that includes it? Is there a known issue with entitlement availability or the iOS 27 sample? Our intended use is explicitly authorised full-display capture using the system picker, with on-device processing and no attempt to bypass user consent. I would appreciate guidance on the correct supported provisioning procedure.
Replies
1
Boosts
0
Views
108
Activity
1w
Supported independent whole-file reference for df and codesign in macOS build 26A434
We are looking for a supported way to establish an independent byte-level reference for two Apple-supplied executables: /bin/df and /usr/bin/codesign. This is a provenance inquiry, not an allegation of tampering or a known Apple defect. The Apple Developer OS download catalog lists macOS 27.0.1, build 26A434, released September 28, 2026, and links to this Apple silicon restore image: https://updates.cdn-apple.com/2026FallFCS/59241290-5d51-4ca8-9df4-31624b9a4eac/UniversalMac_27.0.1_26A434_Restore.ipsw We have saved whole-file lengths and SHA-256 observations from earlier local reads. Different observations had different whole-file digests. A separate historical OS version record identifies 26A434, but it is not contemporaneous with every file observation, so we use this build only as a candidate reference, not as an established build for every sample. The historical device context is Apple silicon / Mac18,5. No new machine inspection is requested or implied here. Questions: Does Apple publish, or have a supported way to obtain, authenticated whole-file byte lengths and SHA-256 values for these exact two paths in the 26A434 Apple silicon distribution? Please specify the applicable architecture and file representation. If not, is there a supported read-only procedure to authenticate the exact restore asset and extract these two complete files as a comparable reference, without installing or restoring macOS? What checks establish the build, model applicability and integrity of the extracted content? Are there documented transformations during installation, personalization or architecture selection that could make a valid installed file differ byte-for-byte from the corresponding restore-image file? If so, what comparison is supported without silently changing a whole-file-equality requirement? We understand from TN2206 and TN3126 that architectures in universal binaries are signed independently and that removing an architecture can preserve signature validity. A valid signature or CDHash is therefore not being treated as a substitute for our whole-file SHA-256 observations. Likewise, a checksum for the complete IPSW would not itself be the checksum of either executable. The intended comparison must not rely solely on the previously observed local codesign executable whose own whole-file binding changed. We are seeking a supported independent reference or verification method; we are not asking to disable Gatekeeper, SIP, authenticated-root protection, modify trust settings, re-sign system executables, or infer the cause of the historical differences. No system image has been downloaded or mounted for this inquiry. No passwords, account identifiers, keychain contents, private keys, logs, or attachments are included. References: https://developer.apple.com/download/os/ https://developer.apple.com/library/archive/technotes/tn2206/ https://developer.apple.com/documentation/technotes/tn3126-inside-code-signing-hashes https://support.apple.com/guide/security/signed-system-volume-security-secd698747c9/web
Topic: Code Signing SubTopic: General
Replies
1
Boosts
0
Views
277
Activity
1w
Developer ID notarization stuck "In Progress" for 1h+ — previous submissions took minutes
Two notarization submissions for a Developer ID–signed macOS app have been "In Progress" for over an hour. Earlier submissions from this same team, credentials and workflow were all Accepted within minutes. Submissions Created (UTC)IDFileStatus2026-11-05 15:54:4802956de4-0ec7-4009-8f8e-1635f93a10d1ProxyPal.zipIn Progress2026-11-05 16:37:25e38d47a1-6709-4008-9682-18f9b96af217ProxyPal.zipIn ProgressThe second one is a resubmission of the identical zip, sent after the first had been stuck for about 40 minutes. What I've checked xcrun notarytool info <id> returns In Progress. xcrun notarytool log <id> returns "Submission log is not yet available". Authentication and upload work, and notarytool history lists both submissions. codesign --verify --deep --strict passes on the app. Every executable in the bundle has the hardened runtime and a secure timestamp. The zip is made with ditto -c -k --keepParent, the same command as the earlier accepted releases. The bundle contents are essentially unchanged since the last accepted release. The differences are a small generated static HTML help folder and version-number changes. Environment Submitted with xcrun notarytool submit ... --keychain-profile ... --wait from a script. macOS 26 (Darwin 25.6), Xcode toolchain notarytool. Zip is 89 MB, 193 files, and includes two nested .apk files that were also in earlier accepted releases. Questions Are these two submissions held for additional analysis, or stuck in the queue? Is there anything on my side I should change?
Replies
4
Boosts
0
Views
493
Activity
1w
Notarization Failure Linked to /Library/Developer
I've been unable to notarize an installer for an app (https://fxfactory.com/info/fxcore/) ever since adding a plug-in SDK that I was hoping to distribute as follows: /Library/Developer/SDKs/FxCore.sdk /Library/Developer/Xcode/Templates/FxCore/FxCore.xctemplate This creates the smoothest possible UX for someone who starts using the SDK, mimicking official SDKs. This is causing notarization failure, without a useful explanation, but a search suggests that Apple is preventing installers from touching the /Library/Developer directory as this might otherwise compromise the developer toolchain. What is the correct strategy for third-party SDKs? I'm assuming that ADDITIONAL_SDKS doesnt' care if the SDK isn't located at that specific location, but is there any other place where I can put the xctemplate and have it appear when creating a new project in Xcode? (I haven't tried using a post-install script to copy files after the fact but I’d assume that would fail... otherwise what would be the point of this extra safety check.) Thank you!
Replies
1
Boosts
0
Views
357
Activity
1w