Post

Replies

Boosts

Views

Activity

All notarization submissions stuck "In Progress" — including a 210-byte test payload (Team SSHD524FKZ)
Every notarization submission from our team has been stuck in "In Progress" since our first attempt about 18 hours ago. None of them has ever produced a log. This includes a deliberately trivial test payload, which is why I believe this is an account-level hold rather than a problem with our app. Team ID: SSHD524FKZ Submissions (all still "In Progress", none has a log), as of 2026-08-06 14:44 UTC: 7aa0f57f-3ada-4867-8951-db832a9ac605 — created 2026-08-05 20:48:16 UTC — app archive, ~125 MB — 18h eea0e40b-d343-4818-b57b-d8bc821adf00 — created 2026-08-05 21:18:47 UTC — app archive, ~125 MB — 17h 6ffa47f1-4420-4fa3-b8a2-ef31451dfbea — created 2026-08-06 10:34:15 UTC — app archive, ~125 MB — 4h 0d05113d-4772-46df-bc1f-2daaf996165c — created 2026-08-06 11:24:49 UTC — test payload, 210 bytes — 3h The key data point: submission 0d05113d is a 210-byte zip containing a single plain text file. It is not signed and contains no executable code at all, so I expected it to be rejected as Invalid within a minute or two. Instead it has in-depth analysis, the delay does not appear to be related to the content, size or signature of our actual app. notarytool log for every submission above returns: Submission log is not yet available or submissionId does not exist which suggests the backend never began processing any of them. What I have already verified locally — the app is correctly signed with a Developer ID Application certificate, with hardened runtime enabled and a secure timestamp: $ codesign -dv --verbose=2 e-muavin.app Identifier=com.e-muavin.app CodeDirectory v=20500 ... flags=0x10000(runtime) Authority=Developer ID Application: E MUAVIN EGITIM TEKNOLOJILERI ... (SSHD524FKZ) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=6 Aug 2026 at 13:34:02 TeamIdentifier=SSHD524FKZ $ codesign -vvv --deep --strict e-muavin.app e-muavin.app: valid on disk e-muavin.app: satisfies its Designated Requirement $ spctl -a -vvv -t install e-muavin.app e-muavin.app: rejected source=Unnotarized Developer ID So the only thing missing is notarization itself. Other checks: the Apple Developer System Status page lists the Developer ID Notary Service as Operational. We are not re-submitting repeatedly — the four submissions listed above are every submission this team has ever made. These are in fact our team's first notarization attempts; our Developer ID certificates were issued yesterday. Environment: macOS 26.6 (25G72), Xcode 26.6 (17F113), notarytool 1.1.2 (41), submitting with an App Store Connect API key via electron-builder 26.15.3. Could someone from the notary service team please look at why submissions from this team are not being processed? Happy to provide any further detail. Thank you.
Topic: Code Signing SubTopic: Notarization
2
0
79
13h
All notarization submissions stuck "In Progress" — including a 210-byte test payload (Team SSHD524FKZ)
Every notarization submission from our team has been stuck in "In Progress" since our first attempt about 18 hours ago. None of them has ever produced a log. This includes a deliberately trivial test payload, which is why I believe this is an account-level hold rather than a problem with our app. Team ID: SSHD524FKZ Submissions (all still "In Progress", none has a log), as of 2026-08-06 14:44 UTC: 7aa0f57f-3ada-4867-8951-db832a9ac605 — created 2026-08-05 20:48:16 UTC — app archive, ~125 MB — 18h eea0e40b-d343-4818-b57b-d8bc821adf00 — created 2026-08-05 21:18:47 UTC — app archive, ~125 MB — 17h 6ffa47f1-4420-4fa3-b8a2-ef31451dfbea — created 2026-08-06 10:34:15 UTC — app archive, ~125 MB — 4h 0d05113d-4772-46df-bc1f-2daaf996165c — created 2026-08-06 11:24:49 UTC — test payload, 210 bytes — 3h The key data point: submission 0d05113d is a 210-byte zip containing a single plain text file. It is not signed and contains no executable code at all, so I expected it to be rejected as Invalid within a minute or two. Instead it has in-depth analysis, the delay does not appear to be related to the content, size or signature of our actual app. notarytool log for every submission above returns: Submission log is not yet available or submissionId does not exist which suggests the backend never began processing any of them. What I have already verified locally — the app is correctly signed with a Developer ID Application certificate, with hardened runtime enabled and a secure timestamp: $ codesign -dv --verbose=2 e-muavin.app Identifier=com.e-muavin.app CodeDirectory v=20500 ... flags=0x10000(runtime) Authority=Developer ID Application: E MUAVIN EGITIM TEKNOLOJILERI ... (SSHD524FKZ) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=6 Aug 2026 at 13:34:02 TeamIdentifier=SSHD524FKZ $ codesign -vvv --deep --strict e-muavin.app e-muavin.app: valid on disk e-muavin.app: satisfies its Designated Requirement $ spctl -a -vvv -t install e-muavin.app e-muavin.app: rejected source=Unnotarized Developer ID So the only thing missing is notarization itself. Other checks: the Apple Developer System Status page lists the Developer ID Notary Service as Operational. We are not re-submitting repeatedly — the four submissions listed above are every submission this team has ever made. These are in fact our team's first notarization attempts; our Developer ID certificates were issued yesterday. Environment: macOS 26.6 (25G72), Xcode 26.6 (17F113), notarytool 1.1.2 (41), submitting with an App Store Connect API key via electron-builder 26.15.3. Could someone from the notary service team please look at why submissions from this team are not being processed? Happy to provide any further detail. Thank you.
Topic: Code Signing SubTopic: Notarization
Replies
2
Boosts
0
Views
79
Activity
13h