I am trying to notarize my first macOS app for direct distribution outside the Mac App Store using Developer ID Application signing.
Team ID: 32S6XVAQPY
Environment:
- macOS app distributed via Developer ID
- notarytool with a saved keychain profile
- archive exported locally, app zipped with ditto
What I already verified locally:
- The archived app is signed with: Developer ID Application: (32S6XVAQPY)
- codesign --verify --deep --strict passes
- spctl shows: source=Unnotarized Developer ID
- syspolicy_check distribution only reports the expected missing notary ticket
- Hardened runtime is enabled
- The app bundle and nested Sparkle executables were re-signed and now have valid Developer ID signatures with secure timestamps
Important note: I previously had a real signing issue in nested Sparkle binaries, and Apple rejected that submission quickly as Invalid. I fixed those signatures, and now new submissions no longer fail quickly but remain stuck In Progress.
Submission IDs currently stuck:
- bea6c4b3-b107-4c81-8042-6c58b1cf5087
- 5489e29c-d583-4779-a125-ca0fbd9cad0b
Earlier invalid submission with a concrete Sparkle signing error:
- 10df648b-eca8-428f-98d6-4cb4096153ad
Apple reported invalid Developer ID / missing secure timestamp on:
- Sparkle.framework/Versions/B/Updater.app/Contents/MacOS/Updater
- Sparkle.framework/Versions/B/Autoupdate
- Sparkle.framework/Versions/B/XPCServices/Downloader.xpc/Contents/MacOS/Downloader
- Sparkle.framework/Versions/B/XPCServices/Installer.xpc/Contents/MacOS/Installer
That Sparkle issue has since been fixed locally and re-verified.
Question: Is there currently a notarization backlog or any known issue affecting first-time macOS notarizations or Developer ID submissions? At this point the remaining submissions appear valid locally but sit In Progress for a very long time.