General: Forums topic: Code Signing Forums subtopic: Code Signing > Notarization Forums tag: Notarization WWDC 2018 Session 702 Your Apps and the Future of macOS Security WWDC 2019 Session 703 All About Notarization WWDC 2021 Session 10261 Faster and simpler notarization for Mac apps WWDC 2022 Session 10109 What’s new in notarization for Mac apps — Amongst other things, this introduced the Notary REST API Notarizing macOS Software Before Distribution documentation Customizing the Notarization Workflow documentation Resolving Common Notarization Issues documentation Notary REST API documentation TN3147 Migrating to the latest notarization tool technote Fetching the Notary Log forums post Q&A with the Mac notary service team Developer > News post Apple notary service update Developer > News post Notarisation and the macOS 10.9 SDK forums post Testing a Notarised Product forums post Notarisation Fundamentals forums post The Pros and Cons of Stapling forums post Resolving Error 65 When Stapling forums post Many notarisation issues are actually code signing or trusted execution issue. For more on those topics, see Code Signing Resources and Trusted Execution Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi all — looking for diagnosis help, posting publicly in case other devs hit the same issue. Symptom Every notarytool submission for the past 32 days returns: statusCode: 7000 statusSummary: "Team is not yet configured for notarization. Please contact Developer Programs Support..." Account state (all healthy as far as I can tell) Team ID: P6V2783F8M Membership: Active, Individual, paid Free Apps Agreement: Active Paid Apps Agreement: Active (signed Jan 4, 2026) W-8BEN tax form: Active Bank account: Active Developer ID Application certificate: valid, used for signing Bundle ID: dev.tinyclaw.desktop (registered) App is correctly signed codesign -dvvv shows: Authority=Developer ID Application: Yang Yang (P6V2783F8M) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=Apr 11, 2026 Hardened runtime + secure timestamp both enabled. spctl --assess passes locally. Submissions (all rejected with 7000) 5a903f08-bd17-4d59-ac63-12e191e2bb5a 49b670da-0f79-4814-809a-f675791f15c3 febfb37a-b445-4d03-b7c4-bf573304f219 9013e185-10e2-42d4-91c1-3378083266eb bfc64627-5eb6-402c-ac25-e79648d2c251 (latest, 2026-05-02) Different builds, different versions (0.5.22-beta.7 → 0.5.27), different DMGs. Same 7000 every time. Credentials revalidated with a fresh app-specific password — same result. DTS Case 102855668616 open since Apr 2 — 4+ weeks of template responses, no engineering progress. Question Has anyone seen 7000 persist this long after a clean Individual enrollment? Is there a specific team-side flag that has to be flipped server-side, that DTS L1 can't see or escalate? Any suggestion on which DTS topic forces escalation to the notarization service team specifically? Happy to share more diagnostic output. Thanks.

I have a macOS app (a background daemon) that I distribute outside the App Store as a .pkg installer. My build process is: Build the app (xcodebuild archive) Sign the app with Developer ID Application Package it with pkgbuild, signed with Developer ID Installer Notarize with notarytool Staple with stapler This works perfectly on my local machine using custom build_pkg.sh. I'm trying to automate this in Xcode Cloud using a ci_post_xcodebuild.sh script so a new build is triggered whenever I push to git repository. The problem is: • security find​-identity shows 0 valid identities in the post-build script environment • The archived app has Signature​=adhoc (no Developer ID signing) • pkgbuild can't sign the .pkg without a Developer ID Installer certificate • Notarization rejects everything because nothing is signed with Developer ID My question: Is there any way to make Developer ID certificates available in Xcode Cloud's post-build scripts? Or is Xcode Cloud only designed for App Store distribution, and I need to use a different CI (like GitHub Actions) for Developer ID / notarized .pkg workflows? Are there other ways to trigger creation of notarized pkg files whenever I push to GitHub?

Hi all, I enrolled in the Apple Developer Program on April 29 and immediately started notarizing my Electron-based macOS app. All submissions are stuck "In Progress" for 24–67 hours, with no Accepted or Invalid verdict. Team ID: VKFQG6Q29S Account: Individual, newly enrolled 2026-04-29 Submissions stuck (all "In Progress"): 2142f524-4c36-4452-a25d-2260d3b7010d (created 2026-04-30, ~50h) 6237312a-ae36-4a98-8ffe-37193c150a69 (created 2026-04-30, ~54h) 5184f493-f574-4f34-a536-8184bf4ce4eb (created 2026-04-29, ~64h) c108ed9f-1908-4c47-9b32-c55d34da99c7 (created 2026-04-29, ~67h) e1502fcd-dad6-402d-a0aa-550a1907ee46 (created 2026-05-01, fresh — submitted via App Store Connect API key as a control) What I have verified: Developer ID Application certificate is valid and trusted (security find-identity -v -p codesigning shows it) Inside-out signing: every Mach-O binary signed individually with hardened runtime, secure timestamp, entitlements; Helper apps and frameworks sealed top-level AFTER inner binaries; parent .app sealed last; DMG container codesigned codesign --verify --deep --strict --verbose=2 /path/to/app → "valid on disk" and "satisfies its Designated Requirement" I tried both auth methods: App-Specific Password (notarytool keychain profile A) and App Store Connect API Key (Team Key, Developer role, validated successfully). Both produce the same "In Progress" stall. Three earlier submissions returned "Invalid" within minutes with concrete errors (missing entitlements on shm-bridge .dylib, broken parent seal etc.), which I fixed. After the fixes, every submission gets stuck "In Progress" with no terminal status. I opened a Code Signing support case (102882655678) on April 30, no response yet. Has anyone else experienced extended "In Progress" hold on a freshly enrolled Developer ID? Is there a known first-submission review queue, and what's the typical SLA? Any way to escalate or is waiting the only path? Thank you.

I have 2 Notarisation stuck for nearly 24 hours oth submission UUIDs: b78aa323-9993-40fd-a510-4fff5e989e8f and 952714cb-3a59-4caa-9343-674ca7dd86d4 Team ID 6A754AWMJB This is a Developer ID distribution (not App Store)

My app's notarization progress is stuck. ID: aa61b008-a329-4e31-bb23-648029510e36 Forum mod DTS Engineer gives "copy-paste" answers to every user who has this problem.

Dear Apple Support, sometimes we observe exit code 68 in stapling via xcrun stapler staple <pkg_file.pkg> The notarization went fine but then stapling does not work. The output for the last ast failed launch looks like Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x60000363c7b0 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <4F2E1620-9251-4525-91E7-C5F3E3681CD0>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <4F2E1620-9251-4525-91E7-C5F3E3681CD0>.<1>" NSLocalizedDescription=The request timed out., 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) As per manual of stapler and sysexit(3) the exit code means EX_NOHOST (68) The host specified did not exist. This is used in mail addresses or network requests. Make a retry sense or is there any other things which is not set correctly at that time? What is your suggestion to avoid this failure and stabilizing our automation of notarization? Best ergards, Stefan

Hello, I have been hitting status code 7000 on every notarization submission since April 21, 2026. The notable detail: earlier submissions on April 18 and April 20 from the same team were Accepted normally. Whatever flag flipped between April 20 and April 21 is on the notary side, because nothing changed on my end. Team details Team ID: ZS76A62WJ4 Organization: KENOPA LTD (UK private limited company) Role: Account Holder Apple Developer Program: Active until April 17, 2027 Apple Developer Program License Agreement: accepted April 16, 2026 Paid Apps Agreement, Free Apps Agreement: both Active in App Store Connect W-8BEN-E and banking: Active Certificate Type: Developer ID Application Identity: "Developer ID Application: KENOPA LTD (ZS76A62WJ4)" Valid through 2027-02-01, full chain trusted App details Platform: macOS (native AppKit, Objective-C, no Electron) Hardened runtime: enabled Code signing passes verify and strict checks Sandbox: not used (Developer ID distribution outside the App Store) Submission history (Team ID ZS76A62WJ4) Accepted submissions: 2026-04-18 10:00 UTC 39856e43-... 2026-04-18 10:03 UTC 3edf2f4f-... 2026-04-18 10:25 UTC 858c52e7-... 2026-04-20 17:17 UTC 4766f3ce-... 2026-04-21 03:58 UTC 9eed3336-... 2026-04-21 05:44 UTC b759941f-... Then everything since flips to Rejected with code 7000: 2026-04-21 19:10 UTC bedc99ad-... 2026-04-21 20:24 UTC 4dbb55f0-... 2026-04-22 07:36 UTC 50e1420e-... 2026-04-24 04:11 UTC 7e4adf81-... 2026-04-25 04:31 UTC 4c0367ea-... 2026-04-25 08:02 UTC a3ce5f56-... (still In Progress at the time of posting) I can paste the full submission IDs in a follow-up if helpful. Sample notary log The body of every Rejected log is the same: status: Rejected statusCode: 7000 statusSummary: "Team is not yet configured for notarization. Please contact Developer Programs Support..." Submissions all upload successfully, sit "In Progress" for hours-to-days, then flip to Rejected with this code. What I have verified All four agreements (Apple Developer Program License, Apple Developer Agreement, Paid Apps, Free Apps) are accepted and Active. Re-checked under the Account Holder login on both portals. Banking and W-8BEN-E are Active. Developer ID Application, Apple Distribution, and Apple Development certificates are all valid and the private keys import cleanly. App Store Connect API key works (notarytool history returns the full list with no auth errors). Same codesign invocation, same notarytool submit flags, same hardened runtime entitlements that worked on April 18-20 still produce the rejection on April 21+. Existing support channels Opened a support ticket via the developer contact form under "Development and Technical / Other Development or Technical Questions" (the exact path the error message specifies). Also emailed Developer Programs separately. Question Has anyone with the same "was working, then suddenly 7000 with no other change" pattern had it resolved? I am aware that DTS engineers have stated on this forum that they cannot escalate this. I am trying to get a sense of: Typical resolution time once a Developer Programs case is open (reports range from days to two-plus months). Whether anyone has found a particular wording of the support request that gets routed faster. Whether the Account Holder doing anything specific in the portal (re-accepting an agreement, toggling something in Membership, etc.) ever cleared this for someone. Thanks.

Hi all, I'm submitting a Developer ID-signed, hardened-runtime app for notarization. Every submission returns: "statusCode: 7000 statusSummary: Team is not yet configured for notarization. Please contact Developer Programs Support..." Team ID: V67NRZ84A2. Apple Developer membership is active, Developer ID Application certificate is valid, signing/verification all clean. Already opened a support case last week via the recommended path. The "contact page" on the developer site said Apple usually responds within 2 business days.... Has anyone hit this and gotten it resolved? How long did it take, and was there a more effective channel than the standard support form? I've seen people on Reddit claim they've actually been able to call a Developer phone line, but I haven't seen a valid phone number anywhere. I appreciate your response!

Hi, I have two notarization submissions stuck "In Progress" for over 18 hours. This is my first time notarizing on this Developer ID account. Submission 1: c1ae7112-79d9-4ada-92a8-bcf87930b5a3 (submitted ~24 hours ago) Submission 2: e201629a-35ef-48a9-b6c4-efbdeecee839 (submitted ~12 hours ago) Team ID: PH4PLAN782 Bundle ID: com.SoundHawkStudio.ComboDyn Type: macOS Audio Unit plugin (.component), universal binary (x86_64 + arm64), Developer ID Application signed, hardened runtime enabled. I have also filed support case 102876329587. Both submissions remain In Progress with no transition to Accepted or Invalid. Any assistance would be greatly appreciated.

Posting another data point in case it helps the team see the pattern. First-time notariser, Apple Developer Team ID Q9LV8L6XZ9. Four submissions (all Ping.zip, Electron app, arm64, hardened runtime, signed with Developer ID Application) submitted yesterday between 19:13 and 20:27 UTC. All still In Progress 19 hours later with no state change whatsoever. Submission IDs: 3861f4af-ec5e-47f9-93c7-d1583ba98863 c5b200a0-5c13-41cf-8376-83eab8d9afe4 cda1991e-1779-4d1d-9448-d464e64e930a 4f374650-4343-4aa8-8afe-03b150dd52b9 xcrun notarytool log <id> returns "Submission log is not yet available" for every one of them — so Apple hasn't produced any analysis output, successful or not. I appreciate that "in-depth analysis" can take longer for first-time uploads, but 19+ hours on four identical submissions with zero progress looks less like deep analysis and more like the jobs are stuck. Is there anything on the account/team-ID side that might be blocking them from entering the analysis pipeline? Happy to provide anything else that would help.

Hey everyone, Just enrolled in the Apple Developer Program yesterday and tried to notarize my first macOS app. I submitted via notarytool and the submission has been sitting at "In Progress" for over 22 hours now. I've submitted twice and both are stuck. The app is a macOS utility built with PyInstaller. I signed it with my Developer ID Application cert, enabled hardened runtime, added a secure timestamp, and included the appropriate entitlements. Everything looked fine on my end. When I query with notarytool info it just says status: In Progress. No rejection email, no acceptance email, nothing. Is this a known issue for first-time submissions? Or is there something specific about PyInstaller apps that causes this? Submission IDs if anyone from Apple is reading this: b512bd92-7eca-4975-823e-9561d5c2ad63 f90cd69f-cf36-4762-bcda-0d0b047d5f49 Already filed a support ticket but wanted to check here too.

Hi, I have a notarization submission that has been stuck in "In Progress" for over 26 hours with no resolution. Apple's system status page shows no incident for the Developer ID Notary Service. Submission details: Submission ID: 23dc147c-6355-49a8-8ebf-78ae40ba19a3 Team ID: 5DX9FFYJHV App: Chakra Browser (Chromium-based, arm64, macOS) Bundle ID: com.chakra.Browser.development Submitted: 2026-04-22 at 19:09 UTC Current status: In Progress I also have two earlier submissions for the same app that are stuck in the same state: 23fe6ea2-325b-4ae8-84a4-4f913e7d3aea (submitted ~17:58 UTC, same day) 943e737a-1c45-468d-ae6b-1ef7358fc1a5 (submitted ~18:32 UTC, same day) The app is signed with a valid Developer ID Application certificate. The zip is ~243 MB (738 MB app bundle). Entitlements used: com.apple.security.cs.allow-jit, com.apple.security.cs.allow-unsigned-executable-memory, com.apple.security.cs.disable-library-validation. These are standard for Chromium-based browsers. xcrun notarytool log returns "Submission log is not yet available" for all three submissions, so there is no error output to share. Has anyone seen notarization stuck this long without a reported service incident? Is there anything I can do to get these unblocked, or do I need to file a TSI? Thanks

Firstly - I didn't want to post here but my attempts at support call service and support submit issue service BOTH returned errors to me upon 'send'/'submit'. Maybe this is linked to my post below. So, here's another one to add to the list of recent (stuck/fail) posts: I'm unable to get any notarization submissions processed. Over the past 24 hours I've submitted 10+ builds of my macOS app and every submission remains at "In Progress" indefinitely — none have completed. To isolate the issue, I submitted a minimal test app (a single "Hello World" binary, ~50KB zip) using the same Developer ID certificate and API key credentials. That submission is also stuck at "In Progress," which suggests the issue is account-level rather than app-specific. What I've ruled out: Network issues (tested on multiple networks, all VPN/network extensions disabled) Authentication method (tested both app-specific password and App Store Connect API key) Code signing (signatures verify locally; one earlier submission did return "Invalid" with actionable errors, confirming the service can process my submissions) The Apple Developer System Status page shows all services as available. Could you please look into whether there's a processing issue or hold on my account's notarization queue? Submission IDs (all stuck at "In Progress"): 20e4c082-b682-4135-a85e-3f17280b0085 (minimal test app, 2026-04-23T07:03 UTC) 81835570-8a2c-462c-8d5a-bd25733a17c3 (2026-04-23T06:55 UTC) 5b7f337e-3e3f-4502-9fde-0a625a2061e7 (2026-04-23T03:38 UTC) bebe35f3-2944-40de-9caf-1c43b68986bb (2026-04-23 ~04:00 UTC) 3c010292-10d7-4cfc-80e3-8bdb4cdae669 (2026-04-23 ~04:30 UTC) a5ca8b1c-91c1-48db-a78a-9e4fd83fe27f (2026-04-23T03:38 UTC) 937f7a3c-435a-4b00-b5b5-7330b80855d4 (2026-04-23T01:59 UTC) 61af2ba4-f136-4993-a8fc-9cd18021fbb5 (2026-04-23T03:10 UTC) b1b7769a-9f1c-4d2b-b1f0-3224808cc901 (2026-04-23T00:12 UTC) 74653d5c-2edf-47b4-9cf3-1e8d33630f6b (2026-04-22T13:27 UTC) 961af655-30e3-44d3-a01b-1c69f5bccfa6 (2026-04-22T12:54 UTC) Thank you!

Hi, I’m requesting investigation of two CtxVault notarization submissions that have remained "In Progress" well past 24 hours. Team ID: DCY4ZS6CS6 App / archive: CtxVault.zip Platform: macOS direct distribution Pending submissions: e2f25e8c-8bf6-44e6-8e60-24b22467b7e6 — created 2026-04-22T12:50:04.988Z — still In Progress 1f41ff2d-cf61-4509-beba-3389f4496ba7 — created 2026-04-22T12:40:23.167Z — still In Progress Context: This is a new Developer ID release path for a personal team. Earlier submissions were Invalid due to unsigned nested Mach-O files inside a bundled Python runtime. That issue was corrected before the two pending submissions above. The current app is signed with Developer ID Application, hardened runtime, and secure timestamps. Local validation passes: codesign --verify --deep --strict spctl assessment on the signed app notarytool accepts the upload and returns submission IDs, but the submissions do not complete and no log is yet available. Earlier invalid submission for context: b4e665a0-98eb-4b92-b44c-58a0a2c6122e Could someone from Apple please confirm whether this team is stuck in queue or under extended review, and whether any team-side provisioning or backend action is needed? I am intentionally not creating more duplicate submissions while these corrected jobs remain pending. Thanks.

Hi, I have two xcrun notarytool submissions stuck in status: In Progress for over 60 hours. Hoping an Apple engineer can take a look, or confirm whether there is an ongoing notarization service incident. Submissions Submission A: 55c155c2-0df9-4157-b2c1-b3510c453b22 Submission B: 06926b24-3e76-4d14-b5f1-2083f0d9dae9 Team ID: 4CXZ4H3C2R Both submitted: 2026-04-21 Both still return status: In Progress at 60+ hours No result email received from Apple xcrun notarytool log <UUID> returns "The log is not yet available" Environment macOS 15 Sequoia Xcode 16.x command-line tools (notarytool 1.x) Developer ID Application certificate, SHA-1 70:86:EB:14:E4:C5:AA:71:2F:C5:3D:A4:3F:E8:79:DE:32:CE:B3:42, valid through 2031-04-20 Hardened Runtime enabled Standard notarization workflow from the same dev environment that has processed previous releases successfully Notarized artifact: single DMG, ~120 MB What I have already tried Apple Developer Support case #102874171230 — opened 2026-04-21. Rep replied 3x suggesting Forums + Feedback Assistant (hence this post). Feedback Assistant FB22576862 — filed 2026-04-22 under Developer Tools > App Notarization > Incorrect/Unexpected Behavior, with attached notarytool poll log showing sustained In Progress. Code-level support request (DTS) — form routes this class of issue out to these Forums (no submit path for notarization service queue issues). Reviewed other Forums threads on similar symptoms from March-April 2026 — multiple teams reporting the same pattern. Asking Can any Apple engineer cross-reference UUIDs A and B against the notarization backend queue state? Is there an ongoing service incident affecting these submissions? Is it safe to resubmit, or will that create duplicate queue entries? Thank you.

I've tried to notarize my app recently and got the error:{ "logFormatVersion": 1, "jobId": "...", "status": "Rejected", "statusSummary": "Team is not yet configured for notarization", "statusCode": 7000, "archiveFilename": "myapp.dmg", "uploadDate": "2019-06-20T06:24:53Z", "sha256": "...", "ticketContents": null, "issues": null }I've never heard about "team configuration for notarization" previously. What are the steps to resolve that issue?Thanks in advance.

I’m looking for guidance on a notarization submission that has been stuck in In Progress for over 24 hours. Details: Team ID: 94B7AVM73F Certificate: Developer ID Application: Bilal Ahmed Qureshi (94B7AVM73F) Tool: xcrun notarytool File: FlashcardGeneratorTrial-AppleSilicon.dmg Submission ID: 7817f9d0-32da-452f-9e2d-fff43478ccf6 Submission created: 2026-04-17T22:10:01.402Z Current status: xcrun notarytool info still reports In Progress This has now been ongoing for more than 24 hours The submission uploaded successfully and received a valid submission ID The Developer ID certificate is valid and correctly paired with the private key in Keychain security find-identity -v -p codesigning returns 1 valid identity Environment: First-time notarization on this developer account macOS direct distribution outside the Mac App Store DMG signed with Developer ID Application certificate Hardened runtime and timestamp enabled during signing I’ve seen some other recent reports of long notarization delays, especially for first-time submissions, so I’m trying to understand whether this is expected queueing / in-depth analysis, or whether there may be an issue with this specific submission. Questions: Is this normal for a first notarization on a new Developer ID account? Is there anything I should do besides wait? Can Apple check whether this submission is stuck in the queue? Thanks.

Hello, I'm submitting my first macOS app for notarization from a new Developer ID team. All three submissions have been stuck at "In Progress" for several hours now. notarytool log returns "Submission log is not yet available" for all of them. Submission IDs: 39856e43-46ee-45ed-b1c7-771fb6603258 (submitted 2026-04-18T10:00 UTC) 3edf2f4f-cbaf-4e14-ba3b-c1b4e111827e (submitted 2026-04-18T10:03 UTC) 858c52e7-3386-41a8-8fee-a31c49980319 (submitted 2026-04-18T10:25 UTC) Details: This is the first notarization attempt for this Developer ID team App is signed with Developer ID Application certificate, hardened runtime enabled codesign --verify --deep --strict passes All nested code (including Sparkle framework helpers) is properly signed Only public system frameworks are linked (IOKit, AppKit, Foundation, etc.) Entitlements: app-sandbox + Sparkle mach-lookup exceptions only No private API usage Is this expected for first-time submissions, or could someone check the backend queue status for these submissions? Any guidance appreciated.

This is my first time submitting an app for notarization. Both submissions have been stuck "In Progress" with no logs available. Body: This is my first time submitting an app for notarization. Both submissions have been stuck "In Progress" with no logs available. Submission 1: ID: 43ea68c1-5291-42c6-b0e1-3cacab4ca01a Submitted: 2026-04-09T02:05:34Z Status: In Progress (15+ hours) Submission 2: ID: 12ea49a0-64cf-495e-af7e-9aad5aabe30f Submitted: 2026-04-09T17:06:51Z Status: In Progress (1+ hour) Details: Team ID: PWTWN9N25D App: Native macOS SwiftUI app (arm64), ~84 MB zipped Signed with Developer ID Application certificate, Hardened Runtime enabled All embedded helper binaries individually codesigned with Hardened Runtime codesign --verify --deep --strict passes Submitted via xcrun notarytool submit with --keychain-profile notarytool log returns "not yet available" for both Apple System Status shows all services available