Hi, I have an app built in Unity that I am trying to sign an notarize for distribution. I can successfully codesign the app and it runs properly. But after successfully notarizing the app, the app stops opening.
My process is as follows:
# codesign the app. omitting "--deep" "--option runtime" or both will result in notarization failing
codesign --force --deep --verify --verbose --option runtime --sign "Developer ID Application: ORG NAME (ZZZZZZZZZ)" path/to/app.app
# create notarization submission zip
/usr/bin/ditto -c -k --keepParent path/to/app.app path/to/app.zip
# submit for notarization
xcrun notarytool submit --wait path/to/app.zip -v --apple-id apple@id.com --password "aaaa-aaaa-aaaa-aaaa" --team-id "ZZZZZZZZZ"
Notarization seems to succeed. Running:
spctl -a -vvv -t install path/to/app.app
-returns:
path/to/app.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: JOHN DOE (ZZZZZZZZZ)
The Problem:
Before code signature, the app runs normally
After code signature, the app runs normally
After notarization, the app hangs indefinitely on opening. It stays in the Dock until force quit. The app does not create its main window. There are no Gatekeeper warnings or pop-up windows.
Additional Information:
The second time I attempt to open the application I get a pop-up warning me that the app was force-quit while opening windows.
This happens whether or not I have used xcrun stapler to staple the notarization to the app
This happens whether I run the app from the terminal, by double clicking on the .app package, or by running the Unix Executable within Contents/MacOS/
Any idea how I can debug this and figure out what's going wrong? Any help would be greatly appreciated.
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
We are trying to notarize a MacOS app on our paid developer business account for the past 3 weeks. After many hours of processing, we received the following error:
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,
Has anyone else experienced this issue and if so, how was it resolved?
We have reached out to support to ask them to enable this configuration and received no reply.
Any advice or guidance would be appreciated.
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 trying to notarize an Electron app for distribution outside the Mac App Store, but every submission is rejected with error 7000.
Team Details:
Team ID: P3HATASMP9
Organization: Rose Ai Labs, Inc.
Role: Account Holder
Apple Developer Program: Active membership
Certificate:
Type: Developer ID Application
Identity: “Developer ID Application: Rose Ai Labs, Inc. (P3HATASMP9)”
Status: Valid in Keychain Access with full certificate chain
App Details:
Platform: macOS (Electron)
Hardened runtime: Enabled
Code signing: Successful (codesign -v passes)
Submission History (all rejected with same error):
Jan 20, 2026: d2f5e812-d443-4858-895e-ca9828f65d6b
Jan 20, 2026: 4864e851-99d4-49df-87b8-22a6b280f4fc
Jan 21, 2026: 69b177bd-5f08-4363-a2bb-1d286dd9f047
Jan 21, 2026: a181071b-e874-4794-90f3-c172b112900e
Jan 21, 2026: ae3ec87f-60da-4826-91df-a247cd4fd46f
Jan 21, 2026: b7165e2f-19a8-4d4a-9e00-21e85550ec8b
Jan 24, 2026: 2b83d46d-6606-450f-9ffe-cbfa0f0bf179
Jan 27, 2026: ed8ba49c-b24f-422b-9271-44dff805fb61
Error from notarytool log:
status: Rejected
statusCode: 7000
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.
What I’ve verified:
Developer ID certificate is valid and trusted
Apple Worldwide Developer Relations Certification Authority chain is complete
App is properly code-signed with hardened runtime
Using notarytool with valid credentials (submission uploads successfully)
Account Holder role with full permissions
Existing support case: 102808512705
I’ve had this issue for over a week with no resolution. The error message says “Team is not yet configured for notarization” which suggests something needs to be enabled on Apple’s side. Has anyone encountered this and found a resolution?
Hi,
we are sending MacOS apps packaged in a ZIP archive or DMG disk image to the Notary Service.
Before we send the app for notarization, we check the code signature via command
codesign -vvv --deep --strict /path/to/app_or_bundle
The result is positive and it does not provide any gaps.
(And yes, we are following the inside out code signing approach, mentioned at Using the codesign Tool's --deep Option Correctly)
Unfortunately, the result of the Notary service provided that one file has no signature, which was not detected by the signature verification command.
The path of the binary was in
<app_name>.app.zip/<app_name>.app/Contents/Resources/inst/<binary>
How I can be verify like a the Notary service does it on our side?
Best regards,
Stefan
Hi Apple Developer Relations / Notary Service Team,
CRITICAL: All notarization submissions stuck "In Progress" since Feb 1, 2026 (5+ days). Blocking product release.
Latest (PRIORITY):
9bf1e3ca-33ed-4185-816c-2e06ff539f25
Stuck submissions:
a9f1abf6-04a1-462c-b7d1-91e834b44c1a
94a172f8-4aa6-475c-a7ec-fd83c8cfc49a
e2c033da-a1d0-480c-a3b5-5401a8dd3d03
eecefd87-8bf9-496c-86c8-c6f0d6a550e0
b1d27d30-7111-4cc7-9f0e-3f44aac43a97
Details: Team ID: JA8C8B5W34 App: 323MB DMG (codesign verified) notarytool log: "not available" (In Progress) Status page: Green
Requests:
Process 9bf1e3ca-33ed-4185-816c-2e06ff539f25
Queue status / ETA?
@Quinn or Notary team - production blocker!
Topic:
Code Signing
SubTopic:
Notarization
Okay, I just pushed a release and notarized. Works great on my test laptop (macOS 26.2) and my test desktop (macOS 14.x)
But it seems to fail for a friend who's running macOS 15.
I've been using the same GitHub actions successfully for months.
How can notarization work for macOS 14 and 26, but not for macOS 15?
I think everything looks okay as far as the signing?
I've checked codesign -dvv
Executable=/Applications/Avogadro2.app/Contents/MacOS/Avogadro2
Identifier=cc.avogadro
Format=app bundle with Mach-O thin (arm64)
CodeDirectory v=20500 size=11607 flags=0x10000(runtime) hashes=352+7 location=embedded
Signature size=8986
Authority=Developer ID Application: Geoffrey Hutchison (…..)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=Feb 5, 2026 at 8:47:21 PM
Info.plist entries=24
TeamIdentifier=…..
Runtime Version=15.5.0
Sealed Resources version=2 rules=13 files=3306
Internal requirements count=1 size=172
And from spctl -a -vv
/Applications/Avogadro2.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Geoffrey Hutchison (….)
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
I am trying to notarize my app but it rejected with this error after 5 days of being in progress.
{
"logFormatVersion": 1,
"jobId": "8291ad9e-4c8e-4974-8753-af1a78e5a4a2",
"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": "SkanVirtualAssistant-1.0.0.dmg",
"uploadDate": "2026-02-05T03:13:41.280Z",
"sha256": "eb95cc25a382e5ce36fc2b7e195c20a1a09cfbfb71a057e754306ad400300d38",
"ticketContents": null,
"issues": null
}
Can anyone help with this? I have an urgent product launch deadline in a week! I have contacted developer program support but have received no response.
Seeing my notarizations getting stuck. This is becoming a blocker for releasing. What's strange is that earlier versions of the same app (very similar) passed notarization very quickly. Any advice or recourse?
Hi everyone,
For the past three days I've been unable to notarize my app — every attempt fails with an HTTP 500 error from Apple's notarization service. What's unusual is that the error occurs not only during submission, but also when simply validating credentials via store-credentials.
Example:
$ xcrun notarytool store-credentials "notarytool-password" \
--apple-id <id> --team-id <team> --password <app-specific-password>
Validating your credentials...
Error: HTTP status code: 500. Internal Server Error
Request ID: K6NYCMIFNM66OI2WRG3ORZEDUE.0.0
Please try again at a later time.
Since the failure happens at credential validation — before any package is even uploaded — I'm fairly confident this is a server-side issue, not something wrong with my setup or the binary. I've tried across different network connections, same result.
Has anyone else been hitting this? Is there a known outage or incident on Apple's notarization infrastructure? Any way to escalate or get a status update beyond checking developer.apple.com/system-status/?
Thanks
I've submitted a few first notarizations for my electron app - I've verified with all the QA and resources that I am doing the correct thing - but its silently just holding all my notarization requests on apples side with no logs. I'm trying to launch my app this week - how should I proceed?
Topic:
Code Signing
SubTopic:
Notarization
Hello everyone,
I’m currently developing an Electron application, and I’m trying to properly sign and notarize it for macOS. The notarization process itself seems to complete successfully—the file is accepted without issues. However, when I attempt to staple the notarization ticket to the executable, I consistently get Error 65 with TheStableAndValidateActionFailed.
The issue is puzzling because the executable does not change at any point during the process. After facing this issue multiple times in my own project, I decided to test it on a more controlled setup. I followed the steps from this https://www.youtube.com/watch?v=hYBLfjT57hU and the instructions from this macos-code-signing-example which have previously worked for others. Yet, even with this setup, I still get the same Error 65.
Below, I have attached the verbose logs for reference. I’m trying to understand what could be causing this issue—whether it’s related to certificates, the signing process, or something else entirely.
Has anyone encountered a similar problem, and if so, how did you resolve it? Any insights would be greatly appreciated!
Hi,
I have an account that is only a few days old. My first notary went smooth and was done within minutes. Every subsequent notary has been stuck pending. The oldest one being a day or so.
Hey everyone,
I've been trying to notarize my Electron macOS app for the past two days without any success. My longest attempt took nearly 4 hours, and my current attempt has already been running for 2 hours and 26 minutes.
From what I can see in the logs, the signing step has completed successfully, and the app is currently in the notarization stage. But it's been stuck there with no real updates or progress indicators.
Is this kind of delay normal?
Has anyone else experienced such long notarization times?
Any help or insight would be greatly appreciated!
Thanks in advance.
Topic:
Code Signing
SubTopic:
Notarization