Following up with a full diagnostic summary since my last post, in case it helps narrow this down. Certificates: Developer ID Installer and Developer ID Application (Team ID 6VCLSHAN7R), both freshly created Aug 19, 2026. Both show as valid/trusted in Keychain Access and match the developer portal (expiration 2031/08/20). What I've verified/tried, all pointing to the same conclusion: Local signature is valid. pkgutil --check-signature shows a full chain (Developer ID Installer → Developer ID Certification Authority → Apple Root CA) with a trusted timestamp. codesign -dvv on the embedded binaries (VST3, AU component, standalone app) all show Authority=Developer ID Application: ..., hardened runtime enabled, valid secure timestamp. No account/cert issues found. No duplicate certificates (security find-identity -v -p basic returns exactly 2 valid identities). No pending Program License Agreement. developer.apple.com/system-status shows Notary Service operational. Signed with productsign directly, not just via the packaging GUI (Packages/Whitebox) — same result. Isolated from product content: a minimal pkgbuild test package (single text file, signed only with productsign, no relation to my actual product) fails with the exact same error. Waited 3+ days in case of certificate propagation delay — no change. Tried both authentication methods — Apple ID + app-specific password, and a Team-scoped App Store Connect API key — both fail identically. Every single attempt returns: "message": "The binary is not signed with a valid Developer ID certificate." Latest Submission IDs (all Invalid, same error): 5b495af5-1a31-41cd-b8a3-d1e33ab2a12a (product pkg, API key auth) 91eee4f0-778a-4edb-9515-eabfc6711f3f (minimal test pkg, Apple ID auth) At this point I've ruled out everything on my end I can think of — package contents, signing tool, authentication method, certificate freshness/propagation, account status. This looks like something wrong with how these specific certificates are provisioned on Apple's side for notarization. Could someone from DTS take a look at the account/certificates directly? Happy to provide any further diagnostics needed. Thanks for your patience.

Hi all, I've hit a wall trying to notarize a macOS installer pkg (built with Packages/Whitebox, signed with productsign). Every submission fails with: "message": "The binary is not signed with a valid Developer ID certificate." What's strange: this happens even on a minimal test pkg built with pkgbuild containing a single text file, signed only with productsign — no relation to my actual product. So it's not a content/nested-binary issue. Local verification passes fine: pkgutil --check-signature shows a full valid chain (Developer ID Installer → Developer ID Certification Authority → Apple Root CA) with a trusted timestamp. Both my Developer ID Installer and Developer ID Application certificates were freshly created on Aug 19, 2026, show as valid/trusted in Keychain Access, and match on developer.apple.com (Team ID 6VCLSHAN7R). What I've already tried: Re-created both certificates from scratch Waited 2 days in case of propagation delay Checked for pending program agreements (none) Checked developer.apple.com/system-status (Notary Service shows operational) Verified no duplicate/conflicting certificates in keychain Submitted a DTS support ticket 2 days ago, still waiting on a response. Has anyone run into this exact "valid everywhere except the notary service" situation? Any pointers appreciated. Example submission ID: 91eee4f0-778a-4edb-9515-eabfc6711f3f