Successfully received submission history.
history
......
--------------------------------------------------
createdDate: 2025-10-19T18:34:47.472Z
id: d3248896-7841-421e-9470-101df9d0da21
name: ...
status: In Progress
--------------------------------------------------
createdDate: 2025-10-19T18:12:45.325Z
id: e5822fa0-5bcf-4610-81fc-9f541e8ad189
name: ...
status: In Progress
Notarization
RSS for tagNotarization is the process of scanning Developer ID-signed software for malicious components before distribution outside of the Mac App Store.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello Colleagues,
We have been seeing a delay in our Apple notarization submission that hangs for hours "in progress" without completing:
This issue has been occurring since Friday, October 17th.
We have also checked the Apple System Status page and there is no indication of any outage for Apple notarization.
I've submitted my app, signed with a new Developer Id Certificate for a distribution outside of the App Store, 88 hours ago.
xcrun notarytool history ...
Shows the submission as "In Progress".
xcrun notarytool log ...
Tells me "Submission log is not yet available or submissionId does not exist".
I don't know if that's expected for an "In Progress" submission.
As far as I can tell the signing worked without problems. I'm using the Tauri toolchain, which under its hood is using notarytool.
How long can I expect this to take? If there is a problem with my submission does the status just stay on "In Progress" or do I get an error?
Thanks
Topic:
Code Signing
SubTopic:
Notarization
Hi Team,
i'm running into same issue with notarization time. I create new, small app for a customer but however the notarization is running since this morning, so almost a few hours.
This isn't normal or ?
Is there anything what i can do ?
Best regard,
Lars
Topic:
Code Signing
SubTopic:
Notarization
Can someone please explain why Mac app packaging is so farcically convoluted?
Windows app packaging can be picked up in an hour or so.
But I've spent longer trying to fathom how to package the Mac version than I did building the app.
And it's not done with me yet.
Every single line of code requires a deep dive into a new, unrelated skillset.
So, it’s sidebar after sidebar.
Kafka’s ‘The Trial’ comes to mind.
Why does it have to be like this?
Topic:
Code Signing
SubTopic:
Notarization
Hi, I'm currently at 19 hours waiting for notarization. My dev account is new and this is the first time I'm submitting anything to be notarized. I've gathered from my research that this is normal (unfortunately). I figure the only thing I can do is wait, but is there any way for me to know if I'm waiting for a human to manually review it? I was going to file a support request, but I saw that they won't be responding to any support requests until after their Thanksgiving break, and I assume nobody is manually reviewing notary submissions for the next week+. I attached the submission below, thanks!
createdDate: 2025-11-21T21:17:10.082Z
id: c9746d42-1dc7-4641-aec1-62c6cedff1a2
name: ***********.zip
status: In Progress
Topic:
Code Signing
SubTopic:
Notarization
App Notarization got stuck, showing In-Progress from last 24 hrs.
This is really frustrating. Can anyone plz update on this?
I am submitting .dmg notarization requests from Sequoia 15.7.3 using xcrun submit. My developer certificate was created in the last two weeks and is valid. I have had some successful notarizations already so I know that my configuration is correct. However, for the last 48 hours all of my submissions are stuck at 'in progress'. Is there an issue with the notarization service on Apple's side?
Topic:
Code Signing
SubTopic:
Notarization
I've submitted my app four times, each time waiting a few hours for something to happen, then reducing the file size of my *.dmg and trying again. The first two seemed to have completed after 36 hours, but I no longer have that specific signed binary (and its a much smaller binary now anyway). The latest two are still "In Progress" and its almost been 48 hours.
I know my process isn't wrong, and my app isn't somehow incorrectly built or being denied because two were accepted. The outage page shows green for the notary tool (https://developer.apple.com/system-status/) so I'm not sure what the hold up is.
I have recently enrolled in the Apple Developer to get my app notarized, and submitted an Archive for notarization, but it is taking forever. It has almost been a whole day, but the status is still in progress, whereas I have seen other developers say that the same takes 10-15 mins to an hour for them. Am I doing anything wrong? Please guide me through this.
Topic:
Code Signing
SubTopic:
Notarization
Multiple notarization submissions have been stuck at
"In Progress" status for over 2 days with no resolution
or error:
4996643b-4512-4025-9648-028fbafca82f - submitted Jan 18
b6db6cd0-dad7-4a8e-b1fc-379467c1086d - submitted Jan 17
88f269c1-56ea-4404-98ba-edbe9a05b3d2 - submitted Jan 19
No logs available (notarytool log returns "not yet available"). The submissions were uploaded successfully and received submission IDs.
Is there a known issue with the notarization service?
Topic:
Code Signing
SubTopic:
Notarization
I'm trying to notarize an application for the first time & it's stuck for more than 24 hours now. I ended up submitting the same app more than 5 times, but all are stuck in waiting state.
There is no visibility into what's happening & whenever i check the status it just shows as "In Progress".
How can i expedite this process ?
id: a6f37169-19a7-4abc-b086-3f298866f65d
id: 596e3ca4-e8a6-4ba9-9ac7-cf07a430eebb
In Progress from 2026-01-21T05:56:24.160Z、2026-01-21T05:55:45.032Z
for 30 hours
Topic:
Code Signing
SubTopic:
Notarization
So we are building a Tauri app and I have no been able to get our App to be Notarized using Developer ID.
We have a ticket open for 3 months now. Can anyone help me out here?
{
"logFormatVersion": 1,
"jobId": "e2ec4d13-bb83-41d4-a497-ba80cf830af1",
"status": "Rejected",
"statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.",
"statusCode": 7000,
"archiveFilename": "HIDDEN",
"uploadDate": "2026-01-23T16:13:37.589Z",
"sha256": "fd52815d5edf14b66b25529e89c207b2acff2c41642261e1049a479f19f2b72f",
"ticketContents": null,
"issues": null
}
How do we escalate to engineering team?
Sincerely,
Nash Gadre
https://camouflagenetworks.com
Topic:
Code Signing
SubTopic:
Notarization
Hi,
I read that notarization should be fairly quick. I thought that it was stuck, so I ended up sending a few submissions of the same app. I was wondering if you'd able to tell me the status of my latest submission (id: a094f93d-8bb2-47fe-a411-b6e357456ec7). It has been saying "In Progress" for over 3 hours now. If it is held for in-depth review, would you be able to tell me what's the wait period is like?
Thanks!
I'm submitting my first macOS app (a native
SwiftUI menu bar app, signed with Developer ID
Application certificate, Hardened Runtime
enabled) for notarization using xcrun
notarytool submit with keychain profile
authentication.
All 9 of my submissions have been stuck at "In
Progress" for up to 16 hours. None have
transitioned to "Accepted" or "Invalid." Logs
are unavailable for all of them (notarytool
log returns "Submission log is not yet
available").
Environment
macOS: 26.2 (25C56)
Xcode: 26.1.1 (17B100)
notarytool: 1.1.0 (39)
App: Native SwiftUI, universal binary
(x86_64 + arm64), ~2.2 MB DMG
Bundle ID: com.gro.ask
Team ID: 4KT56S2BX6
What I've verified
Code signing is valid:
$ codesign --verify --deep --strict GroAsk.app
passes with no errors
$ codesign -dvvv GroAsk.app
Authority=Developer ID Application: Jack Wu
(4KT56S2BX6)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
CodeDirectory flags=0x10000(runtime) #
Hardened Runtime enabled
Runtime Version=26.1.0
Format=app bundle with Mach-O universal
(x86_64 arm64)
Entitlements are minimal:
com.apple.security.app-sandbox
com.apple.security.network.client
Uploads succeed — each submission receives a
valid submission ID and the file uploads to
Apple's servers without error.
Submission history
Created (UTC): 04:40
ID: eeb12389-...
File: GroAsk-1.6.0.dmg
Status: Invalid (Hardened Runtime missing —
since fixed)
────────────────────────────────────────
Created (UTC): 04:42
ID: 6e537a32-...
File: GroAsk-1.6.0.dmg
Status: In Progress (16+ hrs)
────────────────────────────────────────
Created (UTC): 07:52
ID: 5ee41736-...
File: GroAsk-1.6.0.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 08:19
ID: f5c6b9a5-...
File: GroAsk-1.6.0.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 08:27
ID: 0f1c8333-...
File: GroAsk-1.6.0.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 08:29
ID: 77fd9cd4-...
File: GroAsk-1.6.0.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 08:51
ID: db9da93e-...
File: GroAsk-1.6.1.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 09:05
ID: 3c43c09f-...
File: GroAsk.zip
Status: In Progress
────────────────────────────────────────
Created (UTC): 12:01
ID: b2267a74-...
File: GroAsk-1.6.3.dmg
Status: In Progress
────────────────────────────────────────
Created (UTC): 12:15
ID: ae41e45c-...
File: GroAsk.zip
Status: In Progress
The very first submission (eeb12389) came back
as Invalid within minutes because Hardened
Runtime wasn't enabled on the binary. I fixed
the build configuration and confirmed
flags=0x10000(runtime) is present on all
subsequent builds. However, every submission
after that fix has been stuck at "In Progress"
with no state transition.
What I've tried
Submitting both .dmg and .zip formats — same
result
Verified notarytool log — returns
"Submission log is not yet available" for all
stuck submissions
Apple Developer System Status page shows the
Notary Service as "Available"
I've also emailed Apple Developer Support
but have not received a response yet
Questions
Is this the expected behavior for a
first-time notarization account? I've seen
other threads mentioning that new accounts may
be held for "in-depth analysis," but 16+
hours with zero feedback seems excessive.
2. Is there any manual configuration Apple
needs to do on their end to unblock my team
for notarization?
3. Should I stop submitting and wait, or is
there something else I can try?
Any guidance from DTS would be greatly
appreciated. This is blocking the release of
my app.
Notarization submission has been stuck in "In Progress" status for over 15 hours with no resolution.
Hi there, I am trying to roll out distribution to paid users who are unable to receive anything from me for quite some time now, and I've read that notarization is quick. But I've found myself to be under quite a delay. Wondering if I could please get some help.
Submission Details:
ID: e3dff14c-16ab-41a7-a81c-0d1774c66588
Submitted: 2026-02-08T16:42:07.377Z
File: Resonant-0.1.0-arm64.dmg (~200MB)
Status: In Progress (stuck)
Evidence:
Upload completed successfully within minutes
Delay is entirely server-side processing
Same app structure notarized successfully on Feb 5 (submission f5f4c241)
Multiple other submissions stuck since Feb 5 (see history below)
Stuck Submissions (all "In Progress" for days):
e3dff14c (Feb 8, 16:42 UTC) - 15+ hours
3e6bdcb5 (Feb 8, 16:11 UTC) - 16+ hours
37fd1b9f (Feb 8, 12:53 UTC) - 20+ hours
f21a1d9b (Feb 8, 12:31 UTC) - 20+ hours (different app, Clippa.zip)
417244e8 (Feb 8, 06:18 UTC) - 26+ hours
891f370f (Feb 7, 11:44 UTC) - 2+ days
1debba51 (Feb 7, 05:44 UTC) - 2+ days
6a06b87f (Feb 6, 14:16 UTC) - 3+ days
9867261c (Feb 6, 13:44 UTC) - 3+ days
1a7c3967 (Feb 6, 12:58 UTC) - 3+ days
Last Successful Notarization:
f5f4c241 (Feb 5, 18:24 UTC) - Accepted in normal timeframe
Impact:
Unable to distribute production release. This is blocking critical bug fixes from reaching users.
Expected Behavior:
Notarization should complete within 2-10 minutes as documented and as experienced prior to Feb 5.
Request:
Please investigate why submissions are not being processed and either:
Clear the backlog and process pending submissions
Provide guidance on how to proceed with distribution
Not accepted yet (all are still processing, none are rejected)
387af103-42d3-4d95-ae22-0289f90a8559 — In Progress
2d836594-9fb2-41a5-990c-7ea4e0870af0 — In Progress
e61ba9e3-5ff1-4856-8e9d-39c08445ff63 — In Progress
1defdeec-50b4-45c5-b32d-53ca6e4538bb — In Progress
34e60b80-20c3-4ea7-93a7-2bb9e7c6f05c — In Progress
09222b71-eae1-4c5c-aca4-368f697b2a39 — In Progress
eb5327e8-161e-4185-9920-3facf60b7b4b — In Progress
784fc210-d0bf-4924-b0a6-eb8bbac0f2c8 — In Progress
74bc8f31-b1b0-4bed-9142-0c03100a062a — In Progress
4739620c-894a-4283-a43b-df57b29a1771 — In Progress
have created new certificate as well same result.
waiting for apple support to give any answers.
Topic:
Code Signing
SubTopic:
Notarization
Hi! I am encountering an issue with the notarization process.
I'll leave here the outputs of a few command that I think might be useful.
user@AndreisMac % pkgutil --check-signature mypkg.pkg
Package "mypkg.pkg":
Status: signed by a developer certificate issued by Apple for distribution
Notarization: trusted by the Apple notary service
Signed with a trusted timestamp on: 2026-02-18 18:46:16 +0000
Certificate Chain:
...
user@AndreisMac % spctl -a -vv --type install mypkg.pkg
mypkg.pkg: rejected
origin=Developer ID Installer: MyComp LLC (ABCD)
user@AndreisMac % xcrun notarytool submit mypkg.pkg --keychain-profile "notary-profile" --wait
Conducting pre-submission checks for mypkg.pkg and initiating connection to the Apple notary service...
Submission ID received
id: e76f34b3-7c91-451c-a539-8fb39809a5bd
Upload progress: 100,00% (13,3 MB of 13,3 MB)
Successfully uploaded file
id: e76f34b3-7c91-451c-a539-8fb39809a5bd
path: /path/to/mypkg.pkg
Waiting for processing to complete.
Current status: Accepted...............
Processing complete
id: e76f34b3-7c91-451c-a539-8fb39809a5bd
status: Accepted
user@AndreisMac % spctl -a -vv --type install mypkg.pkg
mypkg.pkg: rejected
origin=Developer ID Installer: MyComp LLC (ABCD)
As you can see:
the installer is signed with a Developer ID Installer (the contents are signed and notarized as well)
the first spctl check is failing(even if the installer was already notarized on our build server)
trying to notarize again seems to work
checking again still shows the installer as rejected
I can run the installer locally by removing the quarantine flag, but this is not what I am expecting from a signed¬arized installer.
Interestingly enough, trying this installer on a different MacOS machine works as expected(no quarantine) and spctl shows it as notarized(Accepted).
Any idea what's wrong with my machine?
Made a notarization request a few hours ago and woke up to check the history and it's no longer available. Not rejected/accepted just not found. I have gone ahead to make another request but I have no confidence because I expect the same thing to happen again. Any guidance?
See logs below:
daramfon@MacBook-Pro-3 frontend % xcrun notarytool history --apple-id "$APPLE_ID" --password "$APPLE_APP_SPECIFIC_PASSWORD" --team-id "$APPLE_TEAM_ID"
Successfully received submission history.
history
--------------------------------------------------
createdDate: 2026-02-20T23:53:14.066Z
id: 6f2fadc0-2e8f-4331-a253-68f81334ebc6
name: Speakeasy AI-0.1.0-arm64.zip
status: In Progress
--------------------------------------------------
createdDate: 2026-02-20T23:47:12.897Z
id: 435aec4f-5356-49a5-898d-48aaafb7949f
name: Speakeasy AI.zip
status: In Progress
--------------------------------------------------
createdDate: 2026-02-20T22:35:23.947Z
id: 95896757-873a-4e54-a527-03dc767c9cb5
name: Speakeasy AI.zip
status: In Progress
daramfon@MacBook-Pro-3 frontend % xcrun notarytool history --apple-id "$APPLE_ID" --password "$APPLE_APP_SPECIFIC_PASSWORD" --team-id "$APPLE_TEAM_ID"
No submission history.
daramfon@MacBook-Pro-3 frontend % xcrun notarytool info 6f2fadc0-2e8f-4331-a253-68f81334ebc6 --apple-id "$APPLE_ID" --password "$APPLE_APP_SPECIFIC_PASSWORD" --team-id "$APPLE_TEAM_ID"
Submission does not exist or does not belong to your team.
id: 6f2fadc0-2e8f-4331-a253-68f81334ebc6