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

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
137
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
282
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
360
2w
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
100
2w
Title: Supported launch code requirement with direct posix_spawn and exclusive child reaping on macOS
Title: Supported launch code requirement with direct posix_spawn and exclusive child reaping on macOS I'm designing a security-sensitive process-lifecycle controller on Apple silicon macOS. The controller directly launches a signed foreground executable and must satisfy two requirements: Before any child executable code runs, macOS must enforce a launcher-supplied requirement binding the child to approved code, preferably using LaunchCodeRequirement and CodeDirectoryHash. The original parent must retain exclusive ownership of the child's terminal status through waitpid(), with signalling and reaping serialised by one designated execution context. I understand that Foundation Process.launchRequirement supports launch-time executable constraints, whereas the established lifecycle currently uses direct posix_spawn(). Could Apple DTS clarify: 1. Is there a supported public API for supplying an equivalent launcher-owned code requirement through direct posix_spawn() or its attributes? 2. If Foundation Process is the supported route, can its caller exclusively consume the direct child's terminal status with waitpid() without competing automatic reaping or status consumption by Foundation? Or must callers use Foundation's own termination reporting? 3. If those requirements cannot be combined through one supported interface, is there a recommended public API or launch topology providing both pre-execution code-requirement enforcement and an attributable terminal-status oracle? I'm seeking supported contractual behaviour, not private implementation details. This question concerns executable identity and child lifecycle ownership only. It does not assume that process termination establishes containment of descendants, delegated work or pending external operations. Thank you.
1
0
222
2w
Definitive Rules for Using Secure Enclave on MacOS
Can someone tell me the applications requirements for using the secure enclave on MacOS? Does the application need to be signed with the secure-enclave entitlement in order to use it? Since this is a restricted entitlement, does my App ID need approval to use it from Apple? Currently I'm building in XCode 16 on Sequoia (15.5) using developer signing. My application is a C/C++ daemon running as plist out of /Library/LaunchDaemons. I have also built it as an application using the instructions here but this has not lead to a solution: https://developer.apple.com/documentation/xcode/signing-a-daemon-with-a-restricted-entitlement/ When I run my application from the command line via sudo signed but without the secure-enclave entitlement enabled in my entitlements file it runs. The first call to: SecAccessControlRef access = SecAccessControlCreateWithFlags( kCFAllocatorDefault, kSecAttrAccessibleWhenUnlockedThisDeviceOnly, kSecAccessControlPrivateKeyUsage, &error); succeeds without error. The call to create the key using: SecKeyRef privateKey = SecKeyCreateRandomKey(attributes, &error); then fails with error: (OSStatus error -50 - Failed to generate keypair) Here are the setup attributes (keySize = 256): CFDictionarySetValue(attributes, kSecAttrKeyType, kSecAttrKeyTypeECSECPrimeRandom); CFDictionarySetValue(attributes, kSecAttrKeySizeInBits, keySize); CFDictionarySetValue(attributes, kSecAttrLabel, keyName); CFDictionarySetValue(attributes, kSecAttrApplicationTag, keyLabel); CFDictionarySetValue(attributes, kSecAttrTokenID, kSecAttrTokenIDSecureEnclave); // Store in the Secure Enclave CFDictionarySetValue(attributes, kSecAttrKeyClass, kSecAttrKeyClassPrivate); CFDictionarySetValue(attributes, kSecAttrAccessControl, access); CFDictionarySetValue(attributes, kSecAttrIsPermanent, kCFBooleanTrue); // persist key across app restarts and reboots CFDictionarySetValue(attributes, kSecAttrCanEncrypt, kCFBooleanTrue); CFDictionarySetValue(attributes, kSecAttrCanDecrypt, kCFBooleanTrue); CFDictionarySetValue(attributes, kSecAttrAccessible, kSecAttrAccessibleWhenUnlockedThisDeviceOnly); CFDictionarySetValue(attributes, kSecReturnPersistentRef, kCFBooleanTrue); When I run the application signed and include the "com.apple.developer.secure-enclave" in my entitlements file it crashes at startup. I believe this is to be expected based on above. How do I proceed such that my application can use the secure enclave correctly?
3
0
495
2w
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
168
2w
How to diagnose post-build CSSMERR_TP_NOT_TRUSTED (-26276) and a Runner-only entitlements warning?
An existing development-signed arm64 iPad Release build succeeds in Xcode, including its code-signing step. Post-build static verification from a restricted automation environment reports CSSMERR_TP_NOT_TRUSTED for Runner, App.framework, and Flutter.framework. The recorded commands were: codesign --verify --deep --strict --verbose=6 <app-path> codesign --display --entitlements - --xml <app-path> The entitlements command returns no XML and reports: binary contains an invalid entitlements blob; OS will ignore these entitlements This warning occurs only for Runner. The two frameworks have no entitlements slots. A public Security framework code-signing trust evaluation returned false, TrustResultValue 0, and an empty detailed result. The error and last underlying error were NSOSStatusErrorDomain / -26276, with description "OSStatus -26276". Existing observations: The Apple Development signing certificate matches the provisioning profile, which includes the target iPad. Keychain Access showed valid certificates using system-default trust. Offline code-page/resource hash and CMS signature checks matched. Offline parsing found matching XML/DER entitlement values within the profile's allowed values. These checks do not establish native trust or installation validity. The host is an Apple Silicon Mac and the target is a physical iPad. We have not isolated a focused Xcode sample that reproduces this issue. The original app contains Flutter and other integrations. We do not know whether the cause is in the artifact, trust evaluation, or the restricted execution environment. An OS log query was denied by that environment; it has not been retried or bypassed. We have not changed certificate trust, re-signed, rebuilt, or attempted installation to work around the verification failure. What supported, narrowly scoped diagnostic procedure would: distinguish a genuine trust-policy rejection from an evaluation that could not complete, diagnose the Runner-only entitlements warning, and establish whether the unchanged artifact is installable? Please advise the minimum redacted evidence or focused sample needed. We are seeking Apple's supported diagnostic route without exporting credentials or weakening trust settings. Attachments: none.
1
0
342
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
777
2w
notarytool crashes with SIGBUS mid-upload (EXC_BAD_ACCESS, stack guard fault) on nio.nioTransportServices.connectionchannel thread
xcrun notarytool submit crashes with a SIGBUS during upload, every time, for one specific build of our app. Filing this as its own post since it is a distinct, reproducible crash with a clear crash report, separate from general In Progress slowness. The exact exception, from the macOS crash reporter, is EXC_BAD_ACCESS (SIGBUS), subtype KERN_PROTECTION_FAILURE, with the message "Could not determine thread index for stack guard region." It happens on a background thread named nio.nioTransportServices.connectionchannel, which is the SwiftNIO Network.framework transport thread handling the upload connection. The faulting stack is inside notarytool's own code, going through String.init(format:), then Foundation's NSString formatting, then CoreFoundation's CFString formatting functions, almost certainly while it is trying to format a log or progress line during the upload. The same small set of return addresses repeats many times in a row right before the crash, which looks like unbounded or very deep recursion in that logging path. Reproduction: run xcrun notarytool submit yourbuild.zip --apple-id ... --password ... --team-id ... --wait against a roughly 180 MB zip of a signed .app. The tool prints Submission ID received, starts the S3 multipart upload, and crashes within about a second, before any upload progress is shown, with no error message. The submission is left behind on Apple's side, stuck at status In Progress, and disappears entirely about 11 to 12 hours later, at which point notarytool info for that id returns Submission does not exist or does not belong to your team. This is completely reproducible for us: it has now happened on five separate submissions of our x64 (Intel) build, and zero times submitting our arm64 (Apple Silicon) build of the exact same app, same machine, same credentials, same day. We also tried setting the upload timeout higher with defaults write com.apple.gke.notary.tool nt-upload-connection-timeout 300, which did not help, same crash. We have full macOS crash reports (.ips files) for two separate occurrences of this and are happy to attach or send them, along with the zip that triggers it.
4
0
666
2w
Notarization Stapling NSURLErrorDomain Code=-1005
Unfortunately Radar has been down for several hours tpday, so I figured I'd post here to see if anyone else is having the same issue. All of our Notarization and Stapling for our non-App Store apps is done via Terminal. It's generally worked pretty well for the past 12 months. But for the last 6 days, Notarization has been fine, but Stapling results in a NSURLErrorDomain Code=-1005 error ("The network connection was lost.") about 50% of the time. Needless to say this is getting to be pretty frustrating. I haven't noticed any hiccups with my Internet connection. Using Xcode 26.3 on Sequoia 15.8.2, and again doing everything on the command line. Anyone else seeing the same thing? Here's the most recent Stapling failure from a few minutes ago: error is Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={_kCFStreamErrorCodeKey=-4, NSUnderlyingError=0x6000007983f0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={NSErrorPeerAddressKey=<CFData 0x600002a84050 [0x20221bfa8]>{length = 16, capacity = 16, bytes = 0x100201bb11f8f13c0000000000000000}, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <E200F376-9A02-4636-944C-7DAA6BEECFEC>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <E200F376-9A02-4636-944C-7DAA6BEECFEC>.<1>" ), NSLocalizedDescription=The network connection was lost., NSErrorFailingURLStringKey=https://api.apple-cloudkit.com/database/1/com.apple.gk.ticket-delivery/production/public/records/lookup, NSErrorFailingURLKey=https://api.apple-cloudkit.com/database/1/com.apple.gk.ticket-delivery/production/public/records/lookup, _kCFStreamErrorDomainKey=4} CloudKit's response is inconsistent with expections: (null)
3
0
424
2w
How to request approval for the restricted com.apple.vm.networking entitlement?
Hello everyone, I'm currently developing a macOS application called macOSDocker, which uses Apple's Virtualization.framework to run a lightweight Linux virtual machine hosting Docker containers. One of the main features is bridged networking using VZBridgedNetworkDeviceAttachment, allowing the virtual machine to obtain its own IP address on the local network and making Docker containers directly accessible without additional NAT or port forwarding. However, this requires the restricted com.apple.vm.networking entitlement. Application details: App: macOSDocker Bundle ID: com.macOSDocker Team ID: RYPSKH8HG5 Apple Developer Support Case: 102997773774 I've already contacted Apple Developer Support to request access to this entitlement, but they directed me to the Apple Developer Forums instead. Currently, Xcode reports that the com.apple.vm.networking entitlement is missing from my provisioning profile. My questions are: What is the official process for requesting approval for the restricted com.apple.vm.networking entitlement? Is there a specific form or contact within Apple Developer Relations for submitting such a request? I would appreciate any guidance, particularly from Apple engineers, on how to proceed with the entitlement approval process. Thank you! Kevin
1
0
222
2w
macOS code signing: CSSMERR_TP_NOT_TRUSTED in different execution contexts
Hello Apple Developer Community, I'm running macOS 27.2 on Apple Silicon with Python 3.13.17 installed from the official python.org installer. I am investigating an inconsistency in macOS code-signing and trust verification. What I have observed: In the normal graphical Terminal, code-signature checks for /usr/bin/true and the installed Python 3.13 executable succeed. In an earlier, different execution context, trust verification reported CSSMERR_TP_NOT_TRUSTED. The Mac's date and time are configured automatically. The exact cause of the difference between execution contexts remains unknown. My questions: What could cause macOS trust evaluation to differ between execution contexts? Which read-only diagnostics could identify the cause? How can I investigate this without modifying Keychain trust settings, disabling system security or purchasing a paid developer membership? I can provide sanitized diagnostic logs if needed. Thank you for your help!
Topic: Code Signing SubTopic: General
7
0
816
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
Developer ID notarization submissions stuck "In Progress" for 13+ hours — Team 7MK3979GD2
Hello, All of our notarization submissions except one are stuck in "In Progress" with no terminal state. I would appreciate it if someone could confirm whether they are still queued, or whether something on our side is blocking them. Team ID: 7MK3979GD2 Account: individual, newly enrolled; Developer ID Application certificate issued 2026-10-29 Tool: xcrun notarytool submit with an App Store Connect API key (Team Key, Admin role) Auth/upload work fine: notarytool info returns "In Progress"; notarytool log says the log is not yet available. Submissions (all times UTC): created submission id file status 1 2026-10-29T23:59:53Z 10b84260-955d-4ed5-a7ad-aa7484228427 GsGPT.zip In Progress 2 2026-10-30T01:24:44Z 2fa44ce1-345e-467b-8ea9-97362be6f45f GsGPT.app.zip Accepted (~2.5 min) 3 2026-10-30T01:28:09Z 097fee47-6fec-4645-b4af-f8250820dc8f GsGPT-mac-arm64-8.31.0.dmg In Progress 4 2026-10-30T09:21:25Z 9f4ec58b-d116-4e84-b859-9281ec0e5b92 GsGPT.app.zip In Progress 5 2026-10-30T11:05:58Z d0b9cebb-7795-4699-94b7-2c040fd06028 GsGPT.app.zip In Progress Notes: Submission #2 was accepted in about two and a half minutes, and its log reports "status": "Accepted", "issues": null. All submissions come from the same account, the same certificate and the same build job, so I believe the signed content is compliant. I have not resubmitted the same content. Later attempts are different artifacts from the same pipeline (app zip and DMG). App: GsGPT, an Electron-based macOS desktop app (bundle id cc.ekoaku.gsgpt, version 8.31.0, arm64), signed with Developer ID Application with hardened runtime, to be distributed outside the App Store as a notarized, stapled DMG. I understand that first notarizations from a new account may undergo additional screening. The oldest stuck submission has now been waiting over 13 hours, so I would just like to know whether these are still being processed or have been held. Could you please confirm the current state of Team 7MK3979GD2's submissions and let me know if anything on our side needs action? I am happy to provide any logs or additional details. Thank you very much for your time.
2
0
706
2w
Notary Request Stuck In Pending
Hi Apple team, I have a recently created dev account and submitted two different 20-30 mb .apps for notary through the notary tool. I have read that this should only take minutes at this size of an app but both have been stuck in progress for almost 24+ hours. Below are the UUIDs of the notary submissions. Also I tried re-submitting but these are also stuck in progress. Successfully received submission history. history -------------------------------------------------- createdDate: 2025-09-26T11:46:32.643Z id: 9714758e-e216-496d-80f8-422f77011ebe name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T21:48:46.161Z id: c2a81300-c903-4277-8ef3-70205a690c76 name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T18:24:36.205Z id: 42742be1-c7e5-4483-a2c5-95e89086d070 name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T16:35:09.059Z id: a404256e-40c2-4dca-97fc-983e70ea4b7b name: <>.zip status: In Progress
11
2
1.9k
2w
DriverKit Networking request stalled
We have developed a driver for our WiFi HaLow chipset, but are unable to progress beyond development because our entitlement request has stalled. We have received development entitlements, but these "require provisioning support" The original request was: Entitlement name: DriverKit, DriverKit USB Transport, and DriverKit Networking Business need: Distributing drivers for Morse Micro Wi-Fi HaLow Network Adapters Request date: 7 August 2026 Request ID: C7HYK62R73 When I followed up by email, I was asked to have the Account Holder (rather than a mere admin) reiterate the request to devprograms@apple.com, which I did. That was Follow-up number: 102965131843 The request from the Account Holder was on 21 September. When I followed up on 14 October, I was told to have the Account Holder follow up. None of the responses have asked for any additional information, nor have they offered any insight as to what may be blocking the request beyond the fact that I'm not the Account Holder. No responses have been sent to the Account Holder at all. What's blocking this? We're seeing increasing pressure from major accounts to support macOS, and are powerless to do so.
0
0
260
2w
New Developer ID team: clean, previously accepted app held for hours on every notarization
My macOS app notarized in 22-24 seconds on every release for months under my previous Developer ID team. I often shipped several releases a day, even with minor changes. Since moving to a new Developer ID team (FPRW433858) on Oct 25, every submission of the same app is held for hours: 85da38d3-1874-458a-9bb5-e4656c770037 (Oct 25 19:09 UTC): still In Progress when my CI job hit its 6-hour limit; accepted later. e4bf6e71-58dc-4710-abc0-ba0b459b099f (Oct 29 17:02 UTC): Accepted after 1h56m. Log: "issues": null, "Ready for distribution". Useless because GitHub CI crashed on it. 0c21d8be-cd60-45c0-b990-f7ebb616201a (Oct 29 19:02 UTC): In Progress, 1.5+ hours and counting. Same source, same build pipeline, same Sparkle framework, hardened runtime, inside-out signing. The only change is the team. The build is clean, and you have accepted it twice. I've read the "some uploads are held for in-depth analysis" answers. That is not an answer I can work with. A bugfix release now takes hours or fails outright on CI time limits (6h on github), for an app you have already accepted twice under the new Dev ID and countless times under the old Dev ID. I need concrete answers: Is team FPRW433858 flagged for in-depth analysis, and why? When does that end? After how many accepted submissions, or on what date? Is there anything I must do on my side? If so, what exactly? If nothing on my side causes this, please clear the team or escalate it to someone who can. I cannot accept to wait hours/days on app releases that are straightforward otherwise.
1
1
258
3w
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
230
3w
iPadOS DriverKit USB approval pending -- blocking TestFlight pilot
Could someone help expedite our pending DriverKit USB distribution review request? Our driver works under development signing, but approval is blocking a TestFlight pilot for our accessibility product. Request: 8AR5R3NKZD Submitted October 18, 2026 (still "Submitted") Team: 7U9T57JPF7 Capability: DriverKit USB Transport – VendorID USB: VID 6790 (0x1A86), PID 29987 (0x7523) Support case: 103013236358 Thank you!
0
0
209
3w
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
137
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
282
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
360
Activity
2w
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
100
Activity
2w
Title: Supported launch code requirement with direct posix_spawn and exclusive child reaping on macOS
Title: Supported launch code requirement with direct posix_spawn and exclusive child reaping on macOS I'm designing a security-sensitive process-lifecycle controller on Apple silicon macOS. The controller directly launches a signed foreground executable and must satisfy two requirements: Before any child executable code runs, macOS must enforce a launcher-supplied requirement binding the child to approved code, preferably using LaunchCodeRequirement and CodeDirectoryHash. The original parent must retain exclusive ownership of the child's terminal status through waitpid(), with signalling and reaping serialised by one designated execution context. I understand that Foundation Process.launchRequirement supports launch-time executable constraints, whereas the established lifecycle currently uses direct posix_spawn(). Could Apple DTS clarify: 1. Is there a supported public API for supplying an equivalent launcher-owned code requirement through direct posix_spawn() or its attributes? 2. If Foundation Process is the supported route, can its caller exclusively consume the direct child's terminal status with waitpid() without competing automatic reaping or status consumption by Foundation? Or must callers use Foundation's own termination reporting? 3. If those requirements cannot be combined through one supported interface, is there a recommended public API or launch topology providing both pre-execution code-requirement enforcement and an attributable terminal-status oracle? I'm seeking supported contractual behaviour, not private implementation details. This question concerns executable identity and child lifecycle ownership only. It does not assume that process termination establishes containment of descendants, delegated work or pending external operations. Thank you.
Replies
1
Boosts
0
Views
222
Activity
2w
Definitive Rules for Using Secure Enclave on MacOS
Can someone tell me the applications requirements for using the secure enclave on MacOS? Does the application need to be signed with the secure-enclave entitlement in order to use it? Since this is a restricted entitlement, does my App ID need approval to use it from Apple? Currently I'm building in XCode 16 on Sequoia (15.5) using developer signing. My application is a C/C++ daemon running as plist out of /Library/LaunchDaemons. I have also built it as an application using the instructions here but this has not lead to a solution: https://developer.apple.com/documentation/xcode/signing-a-daemon-with-a-restricted-entitlement/ When I run my application from the command line via sudo signed but without the secure-enclave entitlement enabled in my entitlements file it runs. The first call to: SecAccessControlRef access = SecAccessControlCreateWithFlags( kCFAllocatorDefault, kSecAttrAccessibleWhenUnlockedThisDeviceOnly, kSecAccessControlPrivateKeyUsage, &error); succeeds without error. The call to create the key using: SecKeyRef privateKey = SecKeyCreateRandomKey(attributes, &error); then fails with error: (OSStatus error -50 - Failed to generate keypair) Here are the setup attributes (keySize = 256): CFDictionarySetValue(attributes, kSecAttrKeyType, kSecAttrKeyTypeECSECPrimeRandom); CFDictionarySetValue(attributes, kSecAttrKeySizeInBits, keySize); CFDictionarySetValue(attributes, kSecAttrLabel, keyName); CFDictionarySetValue(attributes, kSecAttrApplicationTag, keyLabel); CFDictionarySetValue(attributes, kSecAttrTokenID, kSecAttrTokenIDSecureEnclave); // Store in the Secure Enclave CFDictionarySetValue(attributes, kSecAttrKeyClass, kSecAttrKeyClassPrivate); CFDictionarySetValue(attributes, kSecAttrAccessControl, access); CFDictionarySetValue(attributes, kSecAttrIsPermanent, kCFBooleanTrue); // persist key across app restarts and reboots CFDictionarySetValue(attributes, kSecAttrCanEncrypt, kCFBooleanTrue); CFDictionarySetValue(attributes, kSecAttrCanDecrypt, kCFBooleanTrue); CFDictionarySetValue(attributes, kSecAttrAccessible, kSecAttrAccessibleWhenUnlockedThisDeviceOnly); CFDictionarySetValue(attributes, kSecReturnPersistentRef, kCFBooleanTrue); When I run the application signed and include the "com.apple.developer.secure-enclave" in my entitlements file it crashes at startup. I believe this is to be expected based on above. How do I proceed such that my application can use the secure enclave correctly?
Replies
3
Boosts
0
Views
495
Activity
2w
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
168
Activity
2w
How to diagnose post-build CSSMERR_TP_NOT_TRUSTED (-26276) and a Runner-only entitlements warning?
An existing development-signed arm64 iPad Release build succeeds in Xcode, including its code-signing step. Post-build static verification from a restricted automation environment reports CSSMERR_TP_NOT_TRUSTED for Runner, App.framework, and Flutter.framework. The recorded commands were: codesign --verify --deep --strict --verbose=6 <app-path> codesign --display --entitlements - --xml <app-path> The entitlements command returns no XML and reports: binary contains an invalid entitlements blob; OS will ignore these entitlements This warning occurs only for Runner. The two frameworks have no entitlements slots. A public Security framework code-signing trust evaluation returned false, TrustResultValue 0, and an empty detailed result. The error and last underlying error were NSOSStatusErrorDomain / -26276, with description "OSStatus -26276". Existing observations: The Apple Development signing certificate matches the provisioning profile, which includes the target iPad. Keychain Access showed valid certificates using system-default trust. Offline code-page/resource hash and CMS signature checks matched. Offline parsing found matching XML/DER entitlement values within the profile's allowed values. These checks do not establish native trust or installation validity. The host is an Apple Silicon Mac and the target is a physical iPad. We have not isolated a focused Xcode sample that reproduces this issue. The original app contains Flutter and other integrations. We do not know whether the cause is in the artifact, trust evaluation, or the restricted execution environment. An OS log query was denied by that environment; it has not been retried or bypassed. We have not changed certificate trust, re-signed, rebuilt, or attempted installation to work around the verification failure. What supported, narrowly scoped diagnostic procedure would: distinguish a genuine trust-policy rejection from an evaluation that could not complete, diagnose the Runner-only entitlements warning, and establish whether the unchanged artifact is installable? Please advise the minimum redacted evidence or focused sample needed. We are seeking Apple's supported diagnostic route without exporting credentials or weakening trust settings. Attachments: none.
Replies
1
Boosts
0
Views
342
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
777
Activity
2w
notarytool crashes with SIGBUS mid-upload (EXC_BAD_ACCESS, stack guard fault) on nio.nioTransportServices.connectionchannel thread
xcrun notarytool submit crashes with a SIGBUS during upload, every time, for one specific build of our app. Filing this as its own post since it is a distinct, reproducible crash with a clear crash report, separate from general In Progress slowness. The exact exception, from the macOS crash reporter, is EXC_BAD_ACCESS (SIGBUS), subtype KERN_PROTECTION_FAILURE, with the message "Could not determine thread index for stack guard region." It happens on a background thread named nio.nioTransportServices.connectionchannel, which is the SwiftNIO Network.framework transport thread handling the upload connection. The faulting stack is inside notarytool's own code, going through String.init(format:), then Foundation's NSString formatting, then CoreFoundation's CFString formatting functions, almost certainly while it is trying to format a log or progress line during the upload. The same small set of return addresses repeats many times in a row right before the crash, which looks like unbounded or very deep recursion in that logging path. Reproduction: run xcrun notarytool submit yourbuild.zip --apple-id ... --password ... --team-id ... --wait against a roughly 180 MB zip of a signed .app. The tool prints Submission ID received, starts the S3 multipart upload, and crashes within about a second, before any upload progress is shown, with no error message. The submission is left behind on Apple's side, stuck at status In Progress, and disappears entirely about 11 to 12 hours later, at which point notarytool info for that id returns Submission does not exist or does not belong to your team. This is completely reproducible for us: it has now happened on five separate submissions of our x64 (Intel) build, and zero times submitting our arm64 (Apple Silicon) build of the exact same app, same machine, same credentials, same day. We also tried setting the upload timeout higher with defaults write com.apple.gke.notary.tool nt-upload-connection-timeout 300, which did not help, same crash. We have full macOS crash reports (.ips files) for two separate occurrences of this and are happy to attach or send them, along with the zip that triggers it.
Replies
4
Boosts
0
Views
666
Activity
2w
Notarization Stapling NSURLErrorDomain Code=-1005
Unfortunately Radar has been down for several hours tpday, so I figured I'd post here to see if anyone else is having the same issue. All of our Notarization and Stapling for our non-App Store apps is done via Terminal. It's generally worked pretty well for the past 12 months. But for the last 6 days, Notarization has been fine, but Stapling results in a NSURLErrorDomain Code=-1005 error ("The network connection was lost.") about 50% of the time. Needless to say this is getting to be pretty frustrating. I haven't noticed any hiccups with my Internet connection. Using Xcode 26.3 on Sequoia 15.8.2, and again doing everything on the command line. Anyone else seeing the same thing? Here's the most recent Stapling failure from a few minutes ago: error is Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={_kCFStreamErrorCodeKey=-4, NSUnderlyingError=0x6000007983f0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={NSErrorPeerAddressKey=<CFData 0x600002a84050 [0x20221bfa8]>{length = 16, capacity = 16, bytes = 0x100201bb11f8f13c0000000000000000}, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <E200F376-9A02-4636-944C-7DAA6BEECFEC>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <E200F376-9A02-4636-944C-7DAA6BEECFEC>.<1>" ), NSLocalizedDescription=The network connection was lost., NSErrorFailingURLStringKey=https://api.apple-cloudkit.com/database/1/com.apple.gk.ticket-delivery/production/public/records/lookup, NSErrorFailingURLKey=https://api.apple-cloudkit.com/database/1/com.apple.gk.ticket-delivery/production/public/records/lookup, _kCFStreamErrorDomainKey=4} CloudKit's response is inconsistent with expections: (null)
Replies
3
Boosts
0
Views
424
Activity
2w
How to request approval for the restricted com.apple.vm.networking entitlement?
Hello everyone, I'm currently developing a macOS application called macOSDocker, which uses Apple's Virtualization.framework to run a lightweight Linux virtual machine hosting Docker containers. One of the main features is bridged networking using VZBridgedNetworkDeviceAttachment, allowing the virtual machine to obtain its own IP address on the local network and making Docker containers directly accessible without additional NAT or port forwarding. However, this requires the restricted com.apple.vm.networking entitlement. Application details: App: macOSDocker Bundle ID: com.macOSDocker Team ID: RYPSKH8HG5 Apple Developer Support Case: 102997773774 I've already contacted Apple Developer Support to request access to this entitlement, but they directed me to the Apple Developer Forums instead. Currently, Xcode reports that the com.apple.vm.networking entitlement is missing from my provisioning profile. My questions are: What is the official process for requesting approval for the restricted com.apple.vm.networking entitlement? Is there a specific form or contact within Apple Developer Relations for submitting such a request? I would appreciate any guidance, particularly from Apple engineers, on how to proceed with the entitlement approval process. Thank you! Kevin
Replies
1
Boosts
0
Views
222
Activity
2w
macOS code signing: CSSMERR_TP_NOT_TRUSTED in different execution contexts
Hello Apple Developer Community, I'm running macOS 27.2 on Apple Silicon with Python 3.13.17 installed from the official python.org installer. I am investigating an inconsistency in macOS code-signing and trust verification. What I have observed: In the normal graphical Terminal, code-signature checks for /usr/bin/true and the installed Python 3.13 executable succeed. In an earlier, different execution context, trust verification reported CSSMERR_TP_NOT_TRUSTED. The Mac's date and time are configured automatically. The exact cause of the difference between execution contexts remains unknown. My questions: What could cause macOS trust evaluation to differ between execution contexts? Which read-only diagnostics could identify the cause? How can I investigate this without modifying Keychain trust settings, disabling system security or purchasing a paid developer membership? I can provide sanitized diagnostic logs if needed. Thank you for your help!
Topic: Code Signing SubTopic: General
Replies
7
Boosts
0
Views
816
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
Developer ID notarization submissions stuck "In Progress" for 13+ hours — Team 7MK3979GD2
Hello, All of our notarization submissions except one are stuck in "In Progress" with no terminal state. I would appreciate it if someone could confirm whether they are still queued, or whether something on our side is blocking them. Team ID: 7MK3979GD2 Account: individual, newly enrolled; Developer ID Application certificate issued 2026-10-29 Tool: xcrun notarytool submit with an App Store Connect API key (Team Key, Admin role) Auth/upload work fine: notarytool info returns "In Progress"; notarytool log says the log is not yet available. Submissions (all times UTC): created submission id file status 1 2026-10-29T23:59:53Z 10b84260-955d-4ed5-a7ad-aa7484228427 GsGPT.zip In Progress 2 2026-10-30T01:24:44Z 2fa44ce1-345e-467b-8ea9-97362be6f45f GsGPT.app.zip Accepted (~2.5 min) 3 2026-10-30T01:28:09Z 097fee47-6fec-4645-b4af-f8250820dc8f GsGPT-mac-arm64-8.31.0.dmg In Progress 4 2026-10-30T09:21:25Z 9f4ec58b-d116-4e84-b859-9281ec0e5b92 GsGPT.app.zip In Progress 5 2026-10-30T11:05:58Z d0b9cebb-7795-4699-94b7-2c040fd06028 GsGPT.app.zip In Progress Notes: Submission #2 was accepted in about two and a half minutes, and its log reports "status": "Accepted", "issues": null. All submissions come from the same account, the same certificate and the same build job, so I believe the signed content is compliant. I have not resubmitted the same content. Later attempts are different artifacts from the same pipeline (app zip and DMG). App: GsGPT, an Electron-based macOS desktop app (bundle id cc.ekoaku.gsgpt, version 8.31.0, arm64), signed with Developer ID Application with hardened runtime, to be distributed outside the App Store as a notarized, stapled DMG. I understand that first notarizations from a new account may undergo additional screening. The oldest stuck submission has now been waiting over 13 hours, so I would just like to know whether these are still being processed or have been held. Could you please confirm the current state of Team 7MK3979GD2's submissions and let me know if anything on our side needs action? I am happy to provide any logs or additional details. Thank you very much for your time.
Replies
2
Boosts
0
Views
706
Activity
2w
Notary Request Stuck In Pending
Hi Apple team, I have a recently created dev account and submitted two different 20-30 mb .apps for notary through the notary tool. I have read that this should only take minutes at this size of an app but both have been stuck in progress for almost 24+ hours. Below are the UUIDs of the notary submissions. Also I tried re-submitting but these are also stuck in progress. Successfully received submission history. history -------------------------------------------------- createdDate: 2025-09-26T11:46:32.643Z id: 9714758e-e216-496d-80f8-422f77011ebe name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T21:48:46.161Z id: c2a81300-c903-4277-8ef3-70205a690c76 name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T18:24:36.205Z id: 42742be1-c7e5-4483-a2c5-95e89086d070 name: <>.zip status: In Progress -------------------------------------------------- createdDate: 2025-09-25T16:35:09.059Z id: a404256e-40c2-4dca-97fc-983e70ea4b7b name: <>.zip status: In Progress
Replies
11
Boosts
2
Views
1.9k
Activity
2w
DriverKit Networking request stalled
We have developed a driver for our WiFi HaLow chipset, but are unable to progress beyond development because our entitlement request has stalled. We have received development entitlements, but these "require provisioning support" The original request was: Entitlement name: DriverKit, DriverKit USB Transport, and DriverKit Networking Business need: Distributing drivers for Morse Micro Wi-Fi HaLow Network Adapters Request date: 7 August 2026 Request ID: C7HYK62R73 When I followed up by email, I was asked to have the Account Holder (rather than a mere admin) reiterate the request to devprograms@apple.com, which I did. That was Follow-up number: 102965131843 The request from the Account Holder was on 21 September. When I followed up on 14 October, I was told to have the Account Holder follow up. None of the responses have asked for any additional information, nor have they offered any insight as to what may be blocking the request beyond the fact that I'm not the Account Holder. No responses have been sent to the Account Holder at all. What's blocking this? We're seeing increasing pressure from major accounts to support macOS, and are powerless to do so.
Replies
0
Boosts
0
Views
260
Activity
2w
New Developer ID team: clean, previously accepted app held for hours on every notarization
My macOS app notarized in 22-24 seconds on every release for months under my previous Developer ID team. I often shipped several releases a day, even with minor changes. Since moving to a new Developer ID team (FPRW433858) on Oct 25, every submission of the same app is held for hours: 85da38d3-1874-458a-9bb5-e4656c770037 (Oct 25 19:09 UTC): still In Progress when my CI job hit its 6-hour limit; accepted later. e4bf6e71-58dc-4710-abc0-ba0b459b099f (Oct 29 17:02 UTC): Accepted after 1h56m. Log: "issues": null, "Ready for distribution". Useless because GitHub CI crashed on it. 0c21d8be-cd60-45c0-b990-f7ebb616201a (Oct 29 19:02 UTC): In Progress, 1.5+ hours and counting. Same source, same build pipeline, same Sparkle framework, hardened runtime, inside-out signing. The only change is the team. The build is clean, and you have accepted it twice. I've read the "some uploads are held for in-depth analysis" answers. That is not an answer I can work with. A bugfix release now takes hours or fails outright on CI time limits (6h on github), for an app you have already accepted twice under the new Dev ID and countless times under the old Dev ID. I need concrete answers: Is team FPRW433858 flagged for in-depth analysis, and why? When does that end? After how many accepted submissions, or on what date? Is there anything I must do on my side? If so, what exactly? If nothing on my side causes this, please clear the team or escalate it to someone who can. I cannot accept to wait hours/days on app releases that are straightforward otherwise.
Replies
1
Boosts
1
Views
258
Activity
3w
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
230
Activity
3w
iPadOS DriverKit USB approval pending -- blocking TestFlight pilot
Could someone help expedite our pending DriverKit USB distribution review request? Our driver works under development signing, but approval is blocking a TestFlight pilot for our accessibility product. Request: 8AR5R3NKZD Submitted October 18, 2026 (still "Submitted") Team: 7U9T57JPF7 Capability: DriverKit USB Transport – VendorID USB: VID 6790 (0x1A86), PID 29987 (0x7523) Support case: 103013236358 Thank you!
Replies
0
Boosts
0
Views
209
Activity
3w